Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow relative paths for LaTeX aux file (group definition by cited entries) #8344

Open
jorgman1 opened this issue Dec 20, 2021 · 11 comments
Open

Comments

@jorgman1
Copy link

Is your suggestion for improvement related to a problem? Please describe.
I have some groups defined by the citations in a LaTeX auxiliary file. However, the path to the auxiliary file needs to be an absolute path. Thus, it only works in one computer. (I synchronise my library in several computers via ownCloud).

Describe the solution you'd like
Allow relative paths when defining groups from aux files

@Siedlerchr Siedlerchr added good first issue An issue intended for project-newcomers. Varies in difficulty. groups type: enhancement labels Dec 20, 2021
@Siedlerchr Siedlerchr removed the good first issue An issue intended for project-newcomers. Varies in difficulty. label Dec 20, 2021
@Siedlerchr
Copy link
Member

The following should already work:

  • Library Properties -> LaTeX File directory. Here you can use a relative directory to your aux directory
  • In the group dialog, if you then select the aux file, it will be stored as relative to the above directory

But I just see that there is a paramter which takes the username into account

@k3KAW8Pnf7mkmdSMPHz27
Copy link
Sponsor Member

While it is a bit unclear, I believe the LaTeX File directory is also user-specific.

refs. JabRef's documentation and #4736.

@jorgman1
Copy link
Author

Ahh, I did not know those Path definitions in the Library Properties. They seem to take user and computer name into account. At least they are stored as follows in my bib-file:

@comment{jabref-meta: fileDirectoryLatex-USER-COMPUTER:PATH;}

I will check it in January with the computer at the university. But that should solve my problem. Thanks a lot!

(I was a bit confused, because in the JabRef preferences the following option can be checked: "Search and store files relative to library file location". I could not find the equivalent for the LaTeX files)

@ilippert
Copy link
Contributor

Just to check, is this issue solved?

@jorgman1
Copy link
Author

Sorry for my delay answering. I completely forgot about it. I tried the suggestion from Siedlerchr, but it does not work (JabRef 5.7--2022-06-15--cb5fe60).
If I use an absolute path for the LaTeX File directory, then I can use a relative Path in the group dialog. That makes sense. Unfortunately, the group remains empty. However, if I remove the LaTeX File directory and use an absolute path in the group dialog, the group is populated correctly. But this solution only works on one computer.

@lcnittl
Copy link

lcnittl commented Jun 8, 2023

I think this is due to a bug -- cf. #9990

@jorgman1 If these files still exist and it is still relevant, can you please check whether the username set correctly for your second host in the bib file:

@Comment{jabref-meta: fileDirectoryLatex-UserA-HostA:C:\\Path\\A;}

and that it is not

@Comment{jabref-meta: fileDirectoryLatex-UserA-HostA:C:\\Path\\A;}
@Comment{jabref-meta: fileDirectoryLatex-UserA-HostB:C:\\Path\\B;}

@jorgman1
Copy link
Author

Using the latest version (JabRef 5.10--2023-06-15--710e1f2) I still have an error. The username is set correctly only for one host, the second host does not save a username:

@comment{jabref-meta: fileDirectoryLatex--HostB:PathB;}
@comment{jabref-meta: fileDirectoryLatex-UserA-HostA:PathA;}

Moreover, when I try to edit the group and select an Aux file, I get an error (on both hosts, even if the LaTeX file directory is not set). This error is new. Error_log.txt

@Siedlerchr
Copy link
Member

I think we need to get all entries and check which belongs to the username
@calixtus @koppor Did you recently refactored anything regarding the file listener?

@calixtus
Copy link
Member

calixtus commented Jun 16, 2023

No, I remember looking at it, when I discovered that we have a DummyFileMonitor, but I don't think anyone refactored it for quite some time.

@calixtus
Copy link
Member

calixtus commented Jun 16, 2023

Maybe related to the change of getUser to getUserAndHost?

@koppor
Copy link
Member

koppor commented Jun 19, 2023

Maybe related to the change of getUser to getUserAndHost?

The issue occurred before. Need to investigate.

@koppor koppor self-assigned this Jun 19, 2023
@koppor koppor added this to the 6.0-beta milestone Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Normal priority
Development

No branches or pull requests

7 participants