@dlukes: I think I'm going to put this aside, as once I make progress in one area, I end up breaking other things.

Any suggestions on easiest/best to support #775 @roshanshariff?

Basically, we need to refactor the file code so it doesn't assume only ever standard file paths, with the initial case zotero links.

I haven't been following this development very much, but I wonder if it's better to just bypass the citar-file functionality completely. In other words, make a separate citar-zotero module that handles everything to do with Zotero attachments, including showing the indicators and handling the "open" action. That way citar-file can stay focused on actual files, since most of its functionality is not relevant to Zotero attachments anyway.

I wonder if it's better to just bypass the citar-file functionality completely. In other words, make a separate citar-zotero module that handles everything to do with Zotero attachments, including showing the indicators and handling the "open" action.

So zotero resources then would be a separate type of related resource, in a separate group from "files"?

And therefore also a separate command from citar-open-files?

They are still files, though, they just use a different mechanism to find them, and are opened in a different viewer, effectively.

I did a few weeks ago merge a change that allow one to set citar-open-entry to open in Zotero, rather than a bib or json file. That felt right to me.

But this has gotten more complicated, as I mentioned.

And a separate module opens up other questions, which I'm loathe to tackle, at least anytime soon.

I think I'm going to close this for now.

Apologies, the whole family's been ill on and off for the past week or so, and I just can't afford to invest much time into this right now, especially as the Citar codebase is mostly unfamiliar to me. Again, sorry!