The SumatraPDF Inverse-Search for any arbitrary Editor
I wanna use texmaker+sumatra, winEdt8+sumatra and texnic Center+sumatra together.
I set the SumatraPDF Inverse-Search option on all editors.
But the SumatraPDF Inverse-Search does not work on WinEdt and TexMaker While working on Texnic Center.
TexMaker setting:
winEdt setting:
TexnicCenter setting:
miktex texmaker texniccenter winedt sumatrapdf
|
show 1 more comment
I wanna use texmaker+sumatra, winEdt8+sumatra and texnic Center+sumatra together.
I set the SumatraPDF Inverse-Search option on all editors.
But the SumatraPDF Inverse-Search does not work on WinEdt and TexMaker While working on Texnic Center.
TexMaker setting:
winEdt setting:
TexnicCenter setting:
miktex texmaker texniccenter winedt sumatrapdf
3
Here is a detailed manual on how to usesynctex
with Sumatra PDF: william.famille-blum.org/blog/…
– Henri Menke
Jul 27 '13 at 11:34
WinEdt and TC already recognizes SumatraPDF. But you need to choose what to do for inverse search.
– percusse
Jul 27 '13 at 11:35
I edited my question.
– Angel
Jul 27 '13 at 13:13
2
@Angel SumatraPDF doesn't know which editor compiled the document. It only knows which editor it should send the inverse-search request as given in the SumatraPDF configuration. Even if you compile with WinEdt it will call TeXnicCenter if it is setup like that. In other words, they don't know each other, they are connected via SyncTeX
– percusse
Jul 27 '13 at 13:46
anybody help me
– Angel
Jul 28 '13 at 21:31
|
show 1 more comment
I wanna use texmaker+sumatra, winEdt8+sumatra and texnic Center+sumatra together.
I set the SumatraPDF Inverse-Search option on all editors.
But the SumatraPDF Inverse-Search does not work on WinEdt and TexMaker While working on Texnic Center.
TexMaker setting:
winEdt setting:
TexnicCenter setting:
miktex texmaker texniccenter winedt sumatrapdf
I wanna use texmaker+sumatra, winEdt8+sumatra and texnic Center+sumatra together.
I set the SumatraPDF Inverse-Search option on all editors.
But the SumatraPDF Inverse-Search does not work on WinEdt and TexMaker While working on Texnic Center.
TexMaker setting:
winEdt setting:
TexnicCenter setting:
miktex texmaker texniccenter winedt sumatrapdf
miktex texmaker texniccenter winedt sumatrapdf
edited Jul 27 '13 at 13:12
Angel
asked Jul 26 '13 at 12:50
AngelAngel
2621210
2621210
3
Here is a detailed manual on how to usesynctex
with Sumatra PDF: william.famille-blum.org/blog/…
– Henri Menke
Jul 27 '13 at 11:34
WinEdt and TC already recognizes SumatraPDF. But you need to choose what to do for inverse search.
– percusse
Jul 27 '13 at 11:35
I edited my question.
– Angel
Jul 27 '13 at 13:13
2
@Angel SumatraPDF doesn't know which editor compiled the document. It only knows which editor it should send the inverse-search request as given in the SumatraPDF configuration. Even if you compile with WinEdt it will call TeXnicCenter if it is setup like that. In other words, they don't know each other, they are connected via SyncTeX
– percusse
Jul 27 '13 at 13:46
anybody help me
– Angel
Jul 28 '13 at 21:31
|
show 1 more comment
3
Here is a detailed manual on how to usesynctex
with Sumatra PDF: william.famille-blum.org/blog/…
– Henri Menke
Jul 27 '13 at 11:34
WinEdt and TC already recognizes SumatraPDF. But you need to choose what to do for inverse search.
– percusse
Jul 27 '13 at 11:35
I edited my question.
– Angel
Jul 27 '13 at 13:13
2
@Angel SumatraPDF doesn't know which editor compiled the document. It only knows which editor it should send the inverse-search request as given in the SumatraPDF configuration. Even if you compile with WinEdt it will call TeXnicCenter if it is setup like that. In other words, they don't know each other, they are connected via SyncTeX
– percusse
Jul 27 '13 at 13:46
anybody help me
– Angel
Jul 28 '13 at 21:31
3
3
Here is a detailed manual on how to use
synctex
with Sumatra PDF: william.famille-blum.org/blog/…– Henri Menke
Jul 27 '13 at 11:34
Here is a detailed manual on how to use
synctex
with Sumatra PDF: william.famille-blum.org/blog/…– Henri Menke
Jul 27 '13 at 11:34
WinEdt and TC already recognizes SumatraPDF. But you need to choose what to do for inverse search.
– percusse
Jul 27 '13 at 11:35
WinEdt and TC already recognizes SumatraPDF. But you need to choose what to do for inverse search.
– percusse
Jul 27 '13 at 11:35
I edited my question.
– Angel
Jul 27 '13 at 13:13
I edited my question.
– Angel
Jul 27 '13 at 13:13
2
2
@Angel SumatraPDF doesn't know which editor compiled the document. It only knows which editor it should send the inverse-search request as given in the SumatraPDF configuration. Even if you compile with WinEdt it will call TeXnicCenter if it is setup like that. In other words, they don't know each other, they are connected via SyncTeX
– percusse
Jul 27 '13 at 13:46
@Angel SumatraPDF doesn't know which editor compiled the document. It only knows which editor it should send the inverse-search request as given in the SumatraPDF configuration. Even if you compile with WinEdt it will call TeXnicCenter if it is setup like that. In other words, they don't know each other, they are connected via SyncTeX
– percusse
Jul 27 '13 at 13:46
anybody help me
– Angel
Jul 28 '13 at 21:31
anybody help me
– Angel
Jul 28 '13 at 21:31
|
show 1 more comment
4 Answers
4
active
oldest
votes
The Problem is, mentioned in the questions comment, that SumatraPDF is linked to the Latex-Compiler through synctex and doesnt know, which created the resulting PDF.
You can use the inverse-search command through the a commandlineswitch of SumatraPDF:-inverse-search
. The commands are:
TeXnicCenter:
-inverse-search ""C:Program FilesTeXnicCenterTEXCNTR.EXE" /ddecmd "[goto('%f', '%l')]""
Note the escapecharacters for doublequotes.
WinEdt:
-inverse-search ""C:Program FilesWinEdt TeamWinEdtwinedt.exe" "[Open(|%f|);SelPar(%l,8)]""
Note the escapecharacters for doublequotes.
TexMaker:
-inverse-search ""C:Program FilesTexmakertexmaker.exe" "%f" -line %l"
Note the escapecharacters for doublequotes.
Explanations
Most applications use DDE-commands to interact. So does TeXnicCenter and WinEdt. For inverse-search SumatraPDF has to comunicate with the PDF-producing application. In that case you have to say SumatraPDF which application is the PDF-producer to communicate with. This works with the commandlineswitch I mentioned above. By clicking the view button in the LatexIDE you should start SumatraPDF with the correct parameters.
"C:Program FilesSumatraPDFSumatraPDF.exe" "PathToPDF" -inverse-search "PathToEditor InverseSearchCommand"
Additional you can use -reuse-instance
to not open a new PDF-window each time. Also its possible to use only the Latexide applications filename instead of the full path, if the Path of the LatexIDE application is in the systems PATH variable.
Inverse search works for TeXnicCenter, because you added the "TeXnicCenter inverse Search DDE command" correct in SumatraPDFs commandline.
In WinEdt you inserted the correct commandlineswitch but no executable to use for the inverse-search. So use the parameter I mentioned above.
In TexMaker you used no comandlineswitch after all. Add the parameter I mentioned above.
All the informations found in the net: TeXnicCenter and WinEdt, TexMaker
Nice explanation, but this doesn't answer the question... How to let SumatraPDF know which editor has been called by? BTW it is WinEdt, not WinEdit.
– karlkoeller
Sep 18 '13 at 17:53
1
@karlkoeller I edited the misspelling of WinEdt. The answer of the question is that you call the pdfviewer with an additional commandlineswitch which includes the path to the caller. In this case the pdfviewer knows who called and is able to call back. On the other hand its not possible that you open the pdfviewer manually with an pdf and then want to invoke a inverse-search. Theoretically the pdfviewer uses the last used (the last calling) application. Additionally its only possible to use inverse-search if you compile the Tex-document for at least one time with the correct parameters.
– RoKi0815
Sep 19 '13 at 6:46
add a comment |
This is a kludge I would try (I didn't): just install SumatraPDF on several locations, each one configured against a different program. If the configuration is stored by directory (and not in the registry or similar) I see no reason why this won't work. Is quite inelegant, but if you don't mind...
SumatraPDF can support multiple configurations via -appdata command thus you can call one per editor
– KJO
28 mins ago
add a comment |
I do not have enough reputation to comment and my is just a small update of what @RoKi0815 wrote:
At least for WinEdt 9, the correct inverse search command is
-inverse-search ""%Bwinedt.exe" "[Open(|%%f|);SelPar(%%l,8)]""
Note the %B
for WinEdt installation directory, and %%f
and %%l
that will become %f
and %l
in SumatraPDF to denote the file name that will be opened and source code line that will be highlighted by inverse search (WinEdt would expand the original %f
to current WinEdt file and %l
would expand to the current WinEdt line, instead of the line that has been double-clicked in SumatraPDF).
This has changed in WinEdt 10 and the auto configurator adds the corrected syntax
– KJO
Dec 14 '18 at 22:53
add a comment |
SumatraPDF has an undocumented setting that allows you to select different advanced settings files for multiple inverse searches. This is most useful for portable configurations but can also be beneficial for normal installed. Simply add -appdata "path to desired settings file" from each editor this replaces the need to -inverse-search ….
Avoid using DDE (its no longer recommended) ONLY use -inverse-search ONCE to set it up (OR switch ONCE between editors, do not call it repeatedly for every compilation) -reuse-instance is not needed (basically its now ignored in tabbed mode)
Most of the answers on this forum for configuring SumatraPDF are now well out of date. Avoid using DDE to SumatraPDF though it is still needed when starting TeXnicCenter from SumatraPDF see the following.
For TeXnicCenter see Adobe Reader makes TexNicCenter crash - Alternative Sumatra
For WinEdt 10 see How to configure Inverse Search with WinEdt + Okular configuration?
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f125546%2fthe-sumatrapdf-inverse-search-for-any-arbitrary-editor%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
The Problem is, mentioned in the questions comment, that SumatraPDF is linked to the Latex-Compiler through synctex and doesnt know, which created the resulting PDF.
You can use the inverse-search command through the a commandlineswitch of SumatraPDF:-inverse-search
. The commands are:
TeXnicCenter:
-inverse-search ""C:Program FilesTeXnicCenterTEXCNTR.EXE" /ddecmd "[goto('%f', '%l')]""
Note the escapecharacters for doublequotes.
WinEdt:
-inverse-search ""C:Program FilesWinEdt TeamWinEdtwinedt.exe" "[Open(|%f|);SelPar(%l,8)]""
Note the escapecharacters for doublequotes.
TexMaker:
-inverse-search ""C:Program FilesTexmakertexmaker.exe" "%f" -line %l"
Note the escapecharacters for doublequotes.
Explanations
Most applications use DDE-commands to interact. So does TeXnicCenter and WinEdt. For inverse-search SumatraPDF has to comunicate with the PDF-producing application. In that case you have to say SumatraPDF which application is the PDF-producer to communicate with. This works with the commandlineswitch I mentioned above. By clicking the view button in the LatexIDE you should start SumatraPDF with the correct parameters.
"C:Program FilesSumatraPDFSumatraPDF.exe" "PathToPDF" -inverse-search "PathToEditor InverseSearchCommand"
Additional you can use -reuse-instance
to not open a new PDF-window each time. Also its possible to use only the Latexide applications filename instead of the full path, if the Path of the LatexIDE application is in the systems PATH variable.
Inverse search works for TeXnicCenter, because you added the "TeXnicCenter inverse Search DDE command" correct in SumatraPDFs commandline.
In WinEdt you inserted the correct commandlineswitch but no executable to use for the inverse-search. So use the parameter I mentioned above.
In TexMaker you used no comandlineswitch after all. Add the parameter I mentioned above.
All the informations found in the net: TeXnicCenter and WinEdt, TexMaker
Nice explanation, but this doesn't answer the question... How to let SumatraPDF know which editor has been called by? BTW it is WinEdt, not WinEdit.
– karlkoeller
Sep 18 '13 at 17:53
1
@karlkoeller I edited the misspelling of WinEdt. The answer of the question is that you call the pdfviewer with an additional commandlineswitch which includes the path to the caller. In this case the pdfviewer knows who called and is able to call back. On the other hand its not possible that you open the pdfviewer manually with an pdf and then want to invoke a inverse-search. Theoretically the pdfviewer uses the last used (the last calling) application. Additionally its only possible to use inverse-search if you compile the Tex-document for at least one time with the correct parameters.
– RoKi0815
Sep 19 '13 at 6:46
add a comment |
The Problem is, mentioned in the questions comment, that SumatraPDF is linked to the Latex-Compiler through synctex and doesnt know, which created the resulting PDF.
You can use the inverse-search command through the a commandlineswitch of SumatraPDF:-inverse-search
. The commands are:
TeXnicCenter:
-inverse-search ""C:Program FilesTeXnicCenterTEXCNTR.EXE" /ddecmd "[goto('%f', '%l')]""
Note the escapecharacters for doublequotes.
WinEdt:
-inverse-search ""C:Program FilesWinEdt TeamWinEdtwinedt.exe" "[Open(|%f|);SelPar(%l,8)]""
Note the escapecharacters for doublequotes.
TexMaker:
-inverse-search ""C:Program FilesTexmakertexmaker.exe" "%f" -line %l"
Note the escapecharacters for doublequotes.
Explanations
Most applications use DDE-commands to interact. So does TeXnicCenter and WinEdt. For inverse-search SumatraPDF has to comunicate with the PDF-producing application. In that case you have to say SumatraPDF which application is the PDF-producer to communicate with. This works with the commandlineswitch I mentioned above. By clicking the view button in the LatexIDE you should start SumatraPDF with the correct parameters.
"C:Program FilesSumatraPDFSumatraPDF.exe" "PathToPDF" -inverse-search "PathToEditor InverseSearchCommand"
Additional you can use -reuse-instance
to not open a new PDF-window each time. Also its possible to use only the Latexide applications filename instead of the full path, if the Path of the LatexIDE application is in the systems PATH variable.
Inverse search works for TeXnicCenter, because you added the "TeXnicCenter inverse Search DDE command" correct in SumatraPDFs commandline.
In WinEdt you inserted the correct commandlineswitch but no executable to use for the inverse-search. So use the parameter I mentioned above.
In TexMaker you used no comandlineswitch after all. Add the parameter I mentioned above.
All the informations found in the net: TeXnicCenter and WinEdt, TexMaker
Nice explanation, but this doesn't answer the question... How to let SumatraPDF know which editor has been called by? BTW it is WinEdt, not WinEdit.
– karlkoeller
Sep 18 '13 at 17:53
1
@karlkoeller I edited the misspelling of WinEdt. The answer of the question is that you call the pdfviewer with an additional commandlineswitch which includes the path to the caller. In this case the pdfviewer knows who called and is able to call back. On the other hand its not possible that you open the pdfviewer manually with an pdf and then want to invoke a inverse-search. Theoretically the pdfviewer uses the last used (the last calling) application. Additionally its only possible to use inverse-search if you compile the Tex-document for at least one time with the correct parameters.
– RoKi0815
Sep 19 '13 at 6:46
add a comment |
The Problem is, mentioned in the questions comment, that SumatraPDF is linked to the Latex-Compiler through synctex and doesnt know, which created the resulting PDF.
You can use the inverse-search command through the a commandlineswitch of SumatraPDF:-inverse-search
. The commands are:
TeXnicCenter:
-inverse-search ""C:Program FilesTeXnicCenterTEXCNTR.EXE" /ddecmd "[goto('%f', '%l')]""
Note the escapecharacters for doublequotes.
WinEdt:
-inverse-search ""C:Program FilesWinEdt TeamWinEdtwinedt.exe" "[Open(|%f|);SelPar(%l,8)]""
Note the escapecharacters for doublequotes.
TexMaker:
-inverse-search ""C:Program FilesTexmakertexmaker.exe" "%f" -line %l"
Note the escapecharacters for doublequotes.
Explanations
Most applications use DDE-commands to interact. So does TeXnicCenter and WinEdt. For inverse-search SumatraPDF has to comunicate with the PDF-producing application. In that case you have to say SumatraPDF which application is the PDF-producer to communicate with. This works with the commandlineswitch I mentioned above. By clicking the view button in the LatexIDE you should start SumatraPDF with the correct parameters.
"C:Program FilesSumatraPDFSumatraPDF.exe" "PathToPDF" -inverse-search "PathToEditor InverseSearchCommand"
Additional you can use -reuse-instance
to not open a new PDF-window each time. Also its possible to use only the Latexide applications filename instead of the full path, if the Path of the LatexIDE application is in the systems PATH variable.
Inverse search works for TeXnicCenter, because you added the "TeXnicCenter inverse Search DDE command" correct in SumatraPDFs commandline.
In WinEdt you inserted the correct commandlineswitch but no executable to use for the inverse-search. So use the parameter I mentioned above.
In TexMaker you used no comandlineswitch after all. Add the parameter I mentioned above.
All the informations found in the net: TeXnicCenter and WinEdt, TexMaker
The Problem is, mentioned in the questions comment, that SumatraPDF is linked to the Latex-Compiler through synctex and doesnt know, which created the resulting PDF.
You can use the inverse-search command through the a commandlineswitch of SumatraPDF:-inverse-search
. The commands are:
TeXnicCenter:
-inverse-search ""C:Program FilesTeXnicCenterTEXCNTR.EXE" /ddecmd "[goto('%f', '%l')]""
Note the escapecharacters for doublequotes.
WinEdt:
-inverse-search ""C:Program FilesWinEdt TeamWinEdtwinedt.exe" "[Open(|%f|);SelPar(%l,8)]""
Note the escapecharacters for doublequotes.
TexMaker:
-inverse-search ""C:Program FilesTexmakertexmaker.exe" "%f" -line %l"
Note the escapecharacters for doublequotes.
Explanations
Most applications use DDE-commands to interact. So does TeXnicCenter and WinEdt. For inverse-search SumatraPDF has to comunicate with the PDF-producing application. In that case you have to say SumatraPDF which application is the PDF-producer to communicate with. This works with the commandlineswitch I mentioned above. By clicking the view button in the LatexIDE you should start SumatraPDF with the correct parameters.
"C:Program FilesSumatraPDFSumatraPDF.exe" "PathToPDF" -inverse-search "PathToEditor InverseSearchCommand"
Additional you can use -reuse-instance
to not open a new PDF-window each time. Also its possible to use only the Latexide applications filename instead of the full path, if the Path of the LatexIDE application is in the systems PATH variable.
Inverse search works for TeXnicCenter, because you added the "TeXnicCenter inverse Search DDE command" correct in SumatraPDFs commandline.
In WinEdt you inserted the correct commandlineswitch but no executable to use for the inverse-search. So use the parameter I mentioned above.
In TexMaker you used no comandlineswitch after all. Add the parameter I mentioned above.
All the informations found in the net: TeXnicCenter and WinEdt, TexMaker
edited Apr 13 '17 at 12:35
Community♦
1
1
answered Sep 18 '13 at 14:17
RoKi0815RoKi0815
1088
1088
Nice explanation, but this doesn't answer the question... How to let SumatraPDF know which editor has been called by? BTW it is WinEdt, not WinEdit.
– karlkoeller
Sep 18 '13 at 17:53
1
@karlkoeller I edited the misspelling of WinEdt. The answer of the question is that you call the pdfviewer with an additional commandlineswitch which includes the path to the caller. In this case the pdfviewer knows who called and is able to call back. On the other hand its not possible that you open the pdfviewer manually with an pdf and then want to invoke a inverse-search. Theoretically the pdfviewer uses the last used (the last calling) application. Additionally its only possible to use inverse-search if you compile the Tex-document for at least one time with the correct parameters.
– RoKi0815
Sep 19 '13 at 6:46
add a comment |
Nice explanation, but this doesn't answer the question... How to let SumatraPDF know which editor has been called by? BTW it is WinEdt, not WinEdit.
– karlkoeller
Sep 18 '13 at 17:53
1
@karlkoeller I edited the misspelling of WinEdt. The answer of the question is that you call the pdfviewer with an additional commandlineswitch which includes the path to the caller. In this case the pdfviewer knows who called and is able to call back. On the other hand its not possible that you open the pdfviewer manually with an pdf and then want to invoke a inverse-search. Theoretically the pdfviewer uses the last used (the last calling) application. Additionally its only possible to use inverse-search if you compile the Tex-document for at least one time with the correct parameters.
– RoKi0815
Sep 19 '13 at 6:46
Nice explanation, but this doesn't answer the question... How to let SumatraPDF know which editor has been called by? BTW it is WinEdt, not WinEdit.
– karlkoeller
Sep 18 '13 at 17:53
Nice explanation, but this doesn't answer the question... How to let SumatraPDF know which editor has been called by? BTW it is WinEdt, not WinEdit.
– karlkoeller
Sep 18 '13 at 17:53
1
1
@karlkoeller I edited the misspelling of WinEdt. The answer of the question is that you call the pdfviewer with an additional commandlineswitch which includes the path to the caller. In this case the pdfviewer knows who called and is able to call back. On the other hand its not possible that you open the pdfviewer manually with an pdf and then want to invoke a inverse-search. Theoretically the pdfviewer uses the last used (the last calling) application. Additionally its only possible to use inverse-search if you compile the Tex-document for at least one time with the correct parameters.
– RoKi0815
Sep 19 '13 at 6:46
@karlkoeller I edited the misspelling of WinEdt. The answer of the question is that you call the pdfviewer with an additional commandlineswitch which includes the path to the caller. In this case the pdfviewer knows who called and is able to call back. On the other hand its not possible that you open the pdfviewer manually with an pdf and then want to invoke a inverse-search. Theoretically the pdfviewer uses the last used (the last calling) application. Additionally its only possible to use inverse-search if you compile the Tex-document for at least one time with the correct parameters.
– RoKi0815
Sep 19 '13 at 6:46
add a comment |
This is a kludge I would try (I didn't): just install SumatraPDF on several locations, each one configured against a different program. If the configuration is stored by directory (and not in the registry or similar) I see no reason why this won't work. Is quite inelegant, but if you don't mind...
SumatraPDF can support multiple configurations via -appdata command thus you can call one per editor
– KJO
28 mins ago
add a comment |
This is a kludge I would try (I didn't): just install SumatraPDF on several locations, each one configured against a different program. If the configuration is stored by directory (and not in the registry or similar) I see no reason why this won't work. Is quite inelegant, but if you don't mind...
SumatraPDF can support multiple configurations via -appdata command thus you can call one per editor
– KJO
28 mins ago
add a comment |
This is a kludge I would try (I didn't): just install SumatraPDF on several locations, each one configured against a different program. If the configuration is stored by directory (and not in the registry or similar) I see no reason why this won't work. Is quite inelegant, but if you don't mind...
This is a kludge I would try (I didn't): just install SumatraPDF on several locations, each one configured against a different program. If the configuration is stored by directory (and not in the registry or similar) I see no reason why this won't work. Is quite inelegant, but if you don't mind...
answered Aug 1 '13 at 12:31
manman
112
112
SumatraPDF can support multiple configurations via -appdata command thus you can call one per editor
– KJO
28 mins ago
add a comment |
SumatraPDF can support multiple configurations via -appdata command thus you can call one per editor
– KJO
28 mins ago
SumatraPDF can support multiple configurations via -appdata command thus you can call one per editor
– KJO
28 mins ago
SumatraPDF can support multiple configurations via -appdata command thus you can call one per editor
– KJO
28 mins ago
add a comment |
I do not have enough reputation to comment and my is just a small update of what @RoKi0815 wrote:
At least for WinEdt 9, the correct inverse search command is
-inverse-search ""%Bwinedt.exe" "[Open(|%%f|);SelPar(%%l,8)]""
Note the %B
for WinEdt installation directory, and %%f
and %%l
that will become %f
and %l
in SumatraPDF to denote the file name that will be opened and source code line that will be highlighted by inverse search (WinEdt would expand the original %f
to current WinEdt file and %l
would expand to the current WinEdt line, instead of the line that has been double-clicked in SumatraPDF).
This has changed in WinEdt 10 and the auto configurator adds the corrected syntax
– KJO
Dec 14 '18 at 22:53
add a comment |
I do not have enough reputation to comment and my is just a small update of what @RoKi0815 wrote:
At least for WinEdt 9, the correct inverse search command is
-inverse-search ""%Bwinedt.exe" "[Open(|%%f|);SelPar(%%l,8)]""
Note the %B
for WinEdt installation directory, and %%f
and %%l
that will become %f
and %l
in SumatraPDF to denote the file name that will be opened and source code line that will be highlighted by inverse search (WinEdt would expand the original %f
to current WinEdt file and %l
would expand to the current WinEdt line, instead of the line that has been double-clicked in SumatraPDF).
This has changed in WinEdt 10 and the auto configurator adds the corrected syntax
– KJO
Dec 14 '18 at 22:53
add a comment |
I do not have enough reputation to comment and my is just a small update of what @RoKi0815 wrote:
At least for WinEdt 9, the correct inverse search command is
-inverse-search ""%Bwinedt.exe" "[Open(|%%f|);SelPar(%%l,8)]""
Note the %B
for WinEdt installation directory, and %%f
and %%l
that will become %f
and %l
in SumatraPDF to denote the file name that will be opened and source code line that will be highlighted by inverse search (WinEdt would expand the original %f
to current WinEdt file and %l
would expand to the current WinEdt line, instead of the line that has been double-clicked in SumatraPDF).
I do not have enough reputation to comment and my is just a small update of what @RoKi0815 wrote:
At least for WinEdt 9, the correct inverse search command is
-inverse-search ""%Bwinedt.exe" "[Open(|%%f|);SelPar(%%l,8)]""
Note the %B
for WinEdt installation directory, and %%f
and %%l
that will become %f
and %l
in SumatraPDF to denote the file name that will be opened and source code line that will be highlighted by inverse search (WinEdt would expand the original %f
to current WinEdt file and %l
would expand to the current WinEdt line, instead of the line that has been double-clicked in SumatraPDF).
answered Apr 20 '16 at 11:06
Jan PřikrylJan Přikryl
1556
1556
This has changed in WinEdt 10 and the auto configurator adds the corrected syntax
– KJO
Dec 14 '18 at 22:53
add a comment |
This has changed in WinEdt 10 and the auto configurator adds the corrected syntax
– KJO
Dec 14 '18 at 22:53
This has changed in WinEdt 10 and the auto configurator adds the corrected syntax
– KJO
Dec 14 '18 at 22:53
This has changed in WinEdt 10 and the auto configurator adds the corrected syntax
– KJO
Dec 14 '18 at 22:53
add a comment |
SumatraPDF has an undocumented setting that allows you to select different advanced settings files for multiple inverse searches. This is most useful for portable configurations but can also be beneficial for normal installed. Simply add -appdata "path to desired settings file" from each editor this replaces the need to -inverse-search ….
Avoid using DDE (its no longer recommended) ONLY use -inverse-search ONCE to set it up (OR switch ONCE between editors, do not call it repeatedly for every compilation) -reuse-instance is not needed (basically its now ignored in tabbed mode)
Most of the answers on this forum for configuring SumatraPDF are now well out of date. Avoid using DDE to SumatraPDF though it is still needed when starting TeXnicCenter from SumatraPDF see the following.
For TeXnicCenter see Adobe Reader makes TexNicCenter crash - Alternative Sumatra
For WinEdt 10 see How to configure Inverse Search with WinEdt + Okular configuration?
add a comment |
SumatraPDF has an undocumented setting that allows you to select different advanced settings files for multiple inverse searches. This is most useful for portable configurations but can also be beneficial for normal installed. Simply add -appdata "path to desired settings file" from each editor this replaces the need to -inverse-search ….
Avoid using DDE (its no longer recommended) ONLY use -inverse-search ONCE to set it up (OR switch ONCE between editors, do not call it repeatedly for every compilation) -reuse-instance is not needed (basically its now ignored in tabbed mode)
Most of the answers on this forum for configuring SumatraPDF are now well out of date. Avoid using DDE to SumatraPDF though it is still needed when starting TeXnicCenter from SumatraPDF see the following.
For TeXnicCenter see Adobe Reader makes TexNicCenter crash - Alternative Sumatra
For WinEdt 10 see How to configure Inverse Search with WinEdt + Okular configuration?
add a comment |
SumatraPDF has an undocumented setting that allows you to select different advanced settings files for multiple inverse searches. This is most useful for portable configurations but can also be beneficial for normal installed. Simply add -appdata "path to desired settings file" from each editor this replaces the need to -inverse-search ….
Avoid using DDE (its no longer recommended) ONLY use -inverse-search ONCE to set it up (OR switch ONCE between editors, do not call it repeatedly for every compilation) -reuse-instance is not needed (basically its now ignored in tabbed mode)
Most of the answers on this forum for configuring SumatraPDF are now well out of date. Avoid using DDE to SumatraPDF though it is still needed when starting TeXnicCenter from SumatraPDF see the following.
For TeXnicCenter see Adobe Reader makes TexNicCenter crash - Alternative Sumatra
For WinEdt 10 see How to configure Inverse Search with WinEdt + Okular configuration?
SumatraPDF has an undocumented setting that allows you to select different advanced settings files for multiple inverse searches. This is most useful for portable configurations but can also be beneficial for normal installed. Simply add -appdata "path to desired settings file" from each editor this replaces the need to -inverse-search ….
Avoid using DDE (its no longer recommended) ONLY use -inverse-search ONCE to set it up (OR switch ONCE between editors, do not call it repeatedly for every compilation) -reuse-instance is not needed (basically its now ignored in tabbed mode)
Most of the answers on this forum for configuring SumatraPDF are now well out of date. Avoid using DDE to SumatraPDF though it is still needed when starting TeXnicCenter from SumatraPDF see the following.
For TeXnicCenter see Adobe Reader makes TexNicCenter crash - Alternative Sumatra
For WinEdt 10 see How to configure Inverse Search with WinEdt + Okular configuration?
answered 8 mins ago
KJOKJO
1,5611114
1,5611114
add a comment |
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f125546%2fthe-sumatrapdf-inverse-search-for-any-arbitrary-editor%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
Here is a detailed manual on how to use
synctex
with Sumatra PDF: william.famille-blum.org/blog/…– Henri Menke
Jul 27 '13 at 11:34
WinEdt and TC already recognizes SumatraPDF. But you need to choose what to do for inverse search.
– percusse
Jul 27 '13 at 11:35
I edited my question.
– Angel
Jul 27 '13 at 13:13
2
@Angel SumatraPDF doesn't know which editor compiled the document. It only knows which editor it should send the inverse-search request as given in the SumatraPDF configuration. Even if you compile with WinEdt it will call TeXnicCenter if it is setup like that. In other words, they don't know each other, they are connected via SyncTeX
– percusse
Jul 27 '13 at 13:46
anybody help me
– Angel
Jul 28 '13 at 21:31