Thanks for your PR. Can you please explain what the problem is/was and why your fix works? It looks like you only have a relative file in your tex group and want to resolve this path relative to the latex folder, is this correct?

If the problem is that it is a relative path, perhaps this would be another location where the code could be added?

Basically, the path for the aux-file is created for the wrong base directory.

creates a Path object path="main.aux". When converting it to its absolute path (path.toAbsolutePath()), it uses the working directory of JabRef and not for the directory of the opened library, which results in a non-existing file-path.

Later, the "file-monitor" detects the modified file main.aux with its correct absolute path, but when it tries to inform the registered listeners at

no proper entry for this file is found in the keys of the map, thus no listener gets informed.

If TexGroup.java would be used, then there would still exist some wrong paths in the code. Thus, I would drop the changes in TexGroup.java and choose GroupsParser.java instead.

@k3KAW8Pnf7mkmdSMPHz27 You are right. In this case, when the library is simply opened from within JabRef, your mentioned code line is not executed, but if one would convert an existing group to a tex-group, this should be a problem as well.

Changing

to

fileMonitor.addListenerForFile(group.filePath, group);

and ignoring the other fixes, should fix both cases (I. simply opening the library and II. changing a group to a TexGroup)

I am not up-to-date on how changing the group type works in practice, but it seems like a good solution to the relativized path issue.

Thanks for the explanation! #7412 (comment) looks like the right approach to me. In addition, I would suggest to add a method getFilePathResolved() to TexGroup that simply returns the filepath object.

Basically, I agree with @tobiasdiez, same regarding #7173 (comment).

I have tested this fix for loading a library, for changing a group to a TexGroup and with different editors each. It works great for Ubuntu.

@k3KAW8Pnf7mkmdSMPHz27 Could you check for safety reasons, that your library on macOS is still getting updated with this version?

@k3KAW8Pnf7mkmdSMPHz27 Could you check for safety reasons, that your library on macOS is still getting updated with this version?

The library is still getting updated 👍 😃

Would be nice if someone can test this under Windows as well, because Windows and Linux behave differently regarding file watching events/file system operations

Just a general thing: Please try to shorten your PR titles and commit messages and keep them meaningful, so after months you still understand, what you did. See https://www.freecodecamp.org/news/writing-good-commit-messages-a-practical-guide/