Hi,
WinShell offers "Macros". With that you can make your own templates.
best regards
Ingo
Search found 6 matches
PDFView
Hi,
unclear what the actual problem was at that time. Also that was never reported to me by email. Although, WinShell works with Adobe, I personally recommend using SumatraPDF.
best regards
Ingo
unclear what the actual problem was at that time. Also that was never reported to me by email. Although, WinShell works with Adobe, I personally recommend using SumatraPDF.
best regards
Ingo
- Wed Nov 03, 2021 1:39 pm
- Forum: WinShell
- Topic: Integrate Gnuplot
- Replies: 8
- Views: 24244
Integrate Gnuplot
Hi,
synctex and enable-write18 are automatically part of the cmd-line call in WinShell.
best regards
Ingo
synctex and enable-write18 are automatically part of the cmd-line call in WinShell.
best regards
Ingo
- Wed Nov 03, 2021 1:37 pm
- Forum: WinShell
- Topic: One or more errors occurred! Please check the options!
- Replies: 2
- Views: 14049
One or more errors occurred! Please check the options!
Hi, as the FAQ page is not online any longer, here is the information: This problem occurs when the Latex binary path is not in your PATH environment variable and should not happen after a correct installation of the LaTeX package. WinShell should be installed at the end of the complete installation...
- Wed Nov 03, 2021 1:28 pm
- Forum: WinShell
- Topic: WinShell Release 4.0
- Replies: 1
- Views: 20127
WinShell Release 4.0
Dear all, as the "WinShell Releases" topic is locked, I cannot add the information there. Please be informed that WinShell 4.0 has been released and can be downloaded from the website. WinShell is a free multilingual integrated development environment (IDE) for LaTeX and TeX. The program i...
- Wed Nov 03, 2021 1:23 pm
- Forum: WinShell
- Topic: pdflatex (F10) problem
- Replies: 1
- Views: 36001
pdflatex (F10) problem
Hi,
although this post is a bit old: The problem was on Adobe, with a wrong registry key. The message box on this topic has been improved for WinShell 4.0
best regards
Ingo
although this post is a bit old: The problem was on Adobe, with a wrong registry key. The message box on this topic has been improved for WinShell 4.0
best regards
Ingo