search

sawhney17 / logseq-citation-manager

73 stars 12 forks source link

New file location requirement poses difficulties for macOS users #34

Open kerim opened 1 year ago

kerim commented 1 year ago

"You will have to reconfigure the .bib export. It now has to be located in .logseq/storage/logseq-citation-manager and in settings, you just give the filename with extension(like starred-items.bib), no need for the file path."

This is difficult for two reasons.

  1. The path is wrong on the Mac. It should be "/Users/[home directory name]/.logseq/storages/logseq-citation-manager" (note that it is "storages" not "storage."

  2. It is a hidden folder and can't easily be navigated to in the Zotero export menu. The only way to do it is to copy the correct entire path name and then use cmd-shift-G to open the dialog box to navigate directly to a folder.

I worry that these issues will make it difficult for most users to figure this out. It would be much easier if one could just save the file in one's logseq assets folder or something like that?

sawhney17 commented 1 year ago

There isn’t an API unfortunately for this function of accessing assets. This is the official logseq provided way(the workaround I was using was proving problematic for some people) On 30 Aug 2022 at 4:10 AM +0400, P. Kerim Friedman @.***>, wrote:

"You will have to reconfigure the .bib export. It now has to be located in .logseq/storage/logseq-citation-manager and in settings, you just give the filename with extension(like starred-items.bib), no need for the file path." This is difficult for two reasons.

  1. The path is wrong on the Mac. It should be "/Users/[home directory name]/.logseq/storages/logseq-citation-manager" (note that it is "storages" not "storage."

  2. It is a hidden folder and can't easily be navigated to in the Zotero export menu. The only way to do it is to copy the correct entire path name and then use cmd-shift-G to open the dialog box to navigate directly to a folder.

I worry that these issues will make it difficult for most users to figure this out. It would be much easier if one could just save the file in one's logseq assets folder or something like that? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

sawhney17 commented 1 year ago

Also, "command shift ." will make it so that hidden folders are visible within the popup menu. On 30 Aug 2022 at 4:10 AM +0400, P. Kerim Friedman @.***>, wrote:

I worry that these issues will make it difficult for most users to figure this out. It would be much easier if one could just save the file in one's logseq assets folder or something like that?

kerim commented 1 year ago

I understand that you are limited by the official API, but it would be good to make a feature request to the team to offer an easier way. I don't want to do it myself because I'm not a programmer, but I think you could write one in a way that would be more persuasive regarding the workflow for both plugin developers and users.

sawhney17 commented 1 year ago

I actually believe it is in development right now. It’s a request that’s already been made and there’s an open PR as well I believe. On 30 Aug 2022 at 8:04 AM +0400, P. Kerim Friedman @.***>, wrote:

I understand that you are limited by the official API, but it would be good to make a feature request to the team to offer an easier way. I don't want to do it myself because I'm not a programmer, but I think you could write one in a way that would be more persuasive regarding the workflow for both plugin developers and users. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

MatthijsKeep commented 1 year ago

This fixed #49 , thanks!