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

Reverse Synctex opens new file #220

Closed
jancurse opened this issue Sep 13, 2019 · 4 comments
Closed

Reverse Synctex opens new file #220

jancurse opened this issue Sep 13, 2019 · 4 comments

Comments

@jancurse
Copy link

jancurse commented Sep 13, 2019

System: Ubuntu 18.04
Latex: 2017.20180305-1
Atom: 1.29.0

Steps to reproduce: I compiled a .tex file within atom using atom-latex:build and view it as a tab within atom. I then try to reverse-sync using Ctrl-left click in the pdf

Result: Atom opens a new tab of the (correct) tex-file and points to the correct location in that file.
(If I make changes in that new tab and compile using atom-latex:build, the pdf is unchanged (it seems to compile the old file which is still open in the original tab).)

Expected result: The cursor points to the correct location in the already opened tab.

Thank you.

@Aerijo
Copy link

Aerijo commented Sep 13, 2019

I'm not sure what you mean by "current tex-file"? Is this the correct file that corresponds to that position in the PDF? And you are saying the correct file opens, but it does not place the cursor in the right position?

Also your Atom version is out of date; the current is 1.40.1

@jancurse
Copy link
Author

I'm not sure what you mean by "current tex-file"? Is this the correct file that corresponds to that position in the PDF? And you are saying the correct file opens, but it does not place the cursor in the right position?

Also your Atom version is out of date; the current is 1.40.1

I changed the question to make this more clear.

@ashthespy
Copy link
Owner

@jancurse Is there a MWE of your issue? In the normal case,

  1. If the file is already open, Atom should just focus the tab, and not open a new editor tab.
  2. Unless you have "Save before build" it could just be that the file is not saved, and hence you don't see the changes?

@ashthespy
Copy link
Owner

Closing for now, feel free to respond with new info to reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants