Finding the generated latex file
After compiling a file in Lyx, I no longer see the full path to the Latex file in the log. It used to be in the first lines of the Latex log window. Is there any way to get it back? That way I can easily copy and paste the path in order to debug the Latex file directly.
Re: Have trouble running Lyx 2.1.4 in Win10
On 10/28/2015 03:28 AM, QIN Peng wrote: I have installed MikTex 2.9 through ProTex before. Then I installed Lyx 2.1.4 bundle version and during the installing process, it reminded me to update MikTex's package, and I updated it with MikTeX Package Manager through the internet. I don't know about Win10, but several of my attempts to install MikTeX and LyX failed until I downloaded the whole MikTeX package, started installation from the complete source (but still installing a subset of packages, that'll be offered by the installer). After that I installed LyX and things finally worked. I have no idea why!
Have trouble running Lyx 2.1.4 in Win10
Hello, It is my first time to use Lyx and LaTex. I have installed MikTex 2.9 through ProTex before. Then I installed Lyx 2.1.4 bundle version and during the installing process, it reminded me to update MikTex's package, and I updated it with MikTeX Package Manager through the internet. When I opened Lyx, error message showed as: LyX: No textclass is found. And it let me to choose from three choices, "Reconfigure", "Without LaTeX" and "Continue". I chose Reconfigure and LyX opened, but no document classes are available. When I attempt to reconfigure LyX, I get an error message: The system reconfiguration has failed. Default textclass is used but LyX may not be able to work properly. Please reconfigure again if needed. And the error log showed in the messsage pane was: 15:41:15.285: (dialog-toggle progress) 15:41:20.755: Running configure... 15:41:20.807: python -tt "C:/Program Files (x86)/Documents/LyX/Resources/configure.py" --binary-dir="C:/Program Files (x86)/Documents/LyX/bin/" 15:41:21.132: checking for DVI to DTL converter... 15:41:21.139: +checking for "dv2dt"... yes 15:41:21.143: checking for DTL to DVI converter... 15:41:21.147: +checking for "dt2dv"... yes 15:41:21.150: checking for a Latex2e program... 15:41:21.151: +checking for "latex"... yes 15:41:21.153: checking for a DVI postprocessing program... 15:41:21.154: +checking for "pplatex"... yes 15:41:21.157: checking for pLaTeX, the Japanese LaTeX... 15:41:21.163: +checking for "platex"... yes 15:41:21.176: Traceback (most recent call last): 15:41:21.179: File "C:/Program Files (x86)/Documents/LyX/Resources/configure.py", line 1557, in 15:41:21.184: LATEX = checkLatex(dtl_tools) 15:41:21.187: File "C:/Program Files (x86)/Documents/LyX/Resources/configure.py", line 482, in checkLatex 15:41:21.189: if cmdOutput(PLATEX + ' chklatex.ltx').find('pLaTeX2e') != -1: 15:41:21.195: File "C:/Program Files (x86)/Documents/LyX/Resources/configure.py", line 72, in cmdOutput 15:41:21.196: stdout=subprocess.PIPE, universal_newlines=True) 15:41:21.199: File "C:\Program Files (x86)\Documents\LyX\Python\lib\subprocess.py", line 710, in __init__ 15:41:21.200: errread, errwrite) 15:41:21.201: File "C:\Program Files (x86)\Documents\LyX\Python\lib\subprocess.py", line 958, in _execute_child 15:41:21.203: startupinfo) 15:41:21.204: UnicodeEncodeError: 'ascii' codec can't encode character u'\u9e4f' in position 25: ordinal not in range(128) 15:41:21.210: Reloading configuration.\..\..\src\support\Systemcall.cpp (292): Systemcall: 'python -tt "C:/Program Files (x86)/Documents/LyX/Resources/configure.py" --binary-dir="C:/Program Files (x86)/Documents/LyX/bin/"' finished with exit code 1 15:41:23.269: (reconfigure) How can I sovle this problem and use LyX? Thanks for help. A new user of LyX
Re: Setting double-spaced output also causes double-spaced on-screen LyX display
On 2015-10-28, Scott Kostyshak wrote: > On Tue, Oct 27, 2015 at 05:24:41PM -0700, Jerry wrote: >> I hope the devs see this post wrt providing different on-screen versus >> rendered appearance regarding line spacing. Maybe I'll file a feature >> request. > I think it would be a good feature request. Also note that 2.2 beta has > not been released yet (alpha will be released soon). But perhaps you > just meant 2.2dev. This would be similar to the "justified" vs. "right aligned" setting, where finally there is a "Use justification in LyX work area" tick-box now under Documents>Settings>Text Layout. (BTW: Documents>Settings vs. Tools>Preferences is not so much about output vs. GUI but in the first space "document specific" vs. "LyX defaults". Fortunately, you can configure defaults for "document specific" settings in the templates. These will then be used for all new documents.) Günter
Re: Finding the generated latex file
Thanks David and Stephan. My problem is that I'm working on a multi-file project so under the tmp directory there are several directories and the location of the Latex file depends on the file I compiled (and of course the tmp directory has a different name each time under windows). What I used to do until few months ago is opening the Latex log, and there I saw the full path to the compiled file, so I could copy it to a Latex editor. After some updates to Lyx & Latex, I see in the log only the file name without the path. I can (and this is what I do) to find the current tmp directory and then searching for all the Latex files to find the right one by its name. I hoped there is an option to return to the previous state of easily finding the directory with a click.
Re: Have trouble running Lyx 2.1.4 in Win10
On 10/28/2015 05:33 AM, Michael Berger wrote: You got errors in the first place because some packages were still missing. By installing the complete content of MiKTeX you got every single packag needed or not. Michael No, I never installed the complete content of MikTeX, I only had it downloaded before I started the installation (as I said).
Re: Finding the generated latex file
On Wed, Oct 28, 2015 at 04:39:23PM +, Ilan wrote: > Thanks David and Stephan. > > My problem is that I'm working on a multi-file project so under the tmp > directory there are several directories and the location of the Latex file > depends on the file I compiled (and of course the tmp directory has a > different > name each time under windows). > > What I used to do until few months ago is opening the Latex log, and there I > saw the full path to the compiled file, so I could copy it to a Latex editor. > After some updates to Lyx & Latex, I see in the log only the file name > without > the path. I'm not aware of a LyX update that meant to change this so perhaps it was an update to the LaTeX file? LyX does not (and has never AFAIK) changed the log in any way after you click on "View Complete Log". However, this might be worth a feature request. If you can think of a good way LyX can show the path to the log in an unintrusive way (e.g. not changing the LaTeX log), then it might be considered. Please make a ticket at http://www.lyx.org/trac > I can (and this is what I do) to find the current tmp directory and then > searching for all the Latex files to find the right one by its name. > I hoped there is an option to return to the previous state of easily finding > the directory with a click. Another possibility is: on Linux when I preview with Evince, I can just right-click on the PDF that is opened in Evince and there is an option "Open Containing Folder". I think that is the folder you want. Scott
Re: Finding the generated latex file
Am 28.10.2015 um 17:47 schrieb Scott Kostyshak: > On Wed, Oct 28, 2015 at 04:39:23PM +, Ilan wrote: >> Thanks David and Stephan. >> > > Another possibility is: > on Linux when I preview with Evince, I can just right-click on the PDF > that is opened in Evince and there is an option "Open Containing > Folder". I think that is the folder you want. > > A very similiar method when viewing the PDF preview: most PDF viewers have something like File/Properties where the path to the file is displayed.
Re: Finding the generated latex file
Am 28.10.2015 um 15:09 schrieb Ilan: > After compiling a file in Lyx, I no longer see the full path to the Latex > file > in the log. > It used to be in the first lines of the Latex log window. > > Is there any way to get it back? That way I can easily copy and paste the > path > in order to debug the Latex file directly. > > If you are under Linux, you can start Lyx from the command line. The tmp folder is printed to stdout at some point. (At least under Lyx 2.1.3 and 2.1.4)
Re: Finding the generated latex file
Am 28.10.2015 um 15:09 schrieb Ilan: > After compiling a file in Lyx, I no longer see the full path to the Latex > file > in the log. > It used to be in the first lines of the Latex log window. > > Is there any way to get it back? That way I can easily copy and paste the > path > in order to debug the Latex file directly. Hi Ilan, there are many possible answers/suggestions: 1. You can lookup the current temporary in the settings dialog. It's in the section for the path names. 2. There is the so called Source Pane. There you can see the live TeX code LyX will produce for the paragraph or the document. 3. You may use one of the Export menu items with "LaTeX" to place the output in the directory where your LyX file is. Stephan
Re: Finding the generated latex file
Am 28.10.2015 um 17:39 schrieb Ilan: > Thanks David and Stephan. > > My problem is that I'm working on a multi-file project so under the tmp > directory there are several directories and the location of the Latex file > depends on the file I compiled (and of course the tmp directory has a > different > name each time under windows). > > What I used to do until few months ago is opening the Latex log, and there I > saw the full path to the compiled file, so I could copy it to a Latex editor. > After some updates to Lyx & Latex, I see in the log only the file name > without > the path. > > I can (and this is what I do) to find the current tmp directory and then > searching for all the Latex files to find the right one by its name. > I hoped there is an option to return to the previous state of easily finding > the directory with a click. You may create a directory somewhere and assign it as temporary directory in the settings dialog. LyX creates the temporary files in sub-directories of this assigned temporary directory after a restart of the LyX application. Hope this is useful. Stephan
Re: Have trouble running Lyx 2.1.4 in Win10
I believe that " MiKTeX you got" should read " MiKTeX you will get". Michael is suggesting installing the complete MiKTeX. It takes up a lot of space but can be awfully useful when you need some obscure package to tweak that last formatting problem. Otherwise you waste a lot of time loading individual packages on an ad hoc basis. On 28 October 2015 at 12:54, PhilipPirripwrote: > On 10/28/2015 05:33 AM, Michael Berger wrote: > >> You got errors in the first place because some packages were still >> missing. By installing the complete content of MiKTeX you got every >> single packag needed or not. >> Michael >> > > No, I never installed the complete content of MikTeX, I only had it > downloaded before I started the installation (as I said). > > > -- John Kane Kingston ON Canada
Re: Where is float figure* in tufte-book?
John Kane: > How long is the caption? I have tried a figure with an 84 word caption and > it looks okay to me. See attached pdf. I am trying to visualise it. Will report back once I have it. For now, I copy the figure* environment, or check it manually (Span columns). It works and it's ok like that. Maybe I ask for too much! Ideally, in a Tufte Book document with many full page-width figures, it'll be nice to avoid the "Right click > Settings > Span columns", or even the Copy-Paste action. Just a (custom) figure* float? Thanks, Nikos > It may be that very long captions such as one sees in some medical (and > biology?) journals are just too long for a Tufte approach?
Re: Have trouble running Lyx 2.1.4 in Win10
On 10/28/2015 09:44 AM, PhilipPirrip wrote: On 10/28/2015 03:28 AM, QIN Peng wrote: I have installed MikTex 2.9 through ProTex before. Then I installed Lyx 2.1.4 bundle version and during the installing process, it reminded me to update MikTex's package, and I updated it with MikTeX Package Manager through the internet. I don't know about Win10, but several of my attempts to install MikTeX and LyX failed until I downloaded the whole MikTeX package, started installation from the complete source (but still installing a subset of packages, that'll be offered by the installer). After that I installed LyX and things finally worked. I have no idea why! You got errors in the first place because some packages were still missing. By installing the complete content of MiKTeX you got every single packag needed or not. Michael