On Sat, 16 Mar 2024, Paul Rubin wrote:
I'd never heard of ptex before. Uncle Google says it's used to publish in
Japanese. I take it that's what you are trying to do?
Paul,
No, I write in English. For some reason the fresh installation of
TeXLive2024 and attempted update of fmtutil failed.
continuum),
that buffer directory and its contents should stay put.
Paul,
The issue since the TeXLive2024 upgrade is lyx finding a pdflatex error.
While updating tlmgr and fmtutils from within /etc/cron.weekly earlier
this
morning I ran it again manually just now and it exited with an error
code 3:
Thank you so much for telling me what it SHOULD do.
It didn't in the Mac case (two different laptops).
el
On 2024-03-16 20:40, Rich Shepard wrote:
> On Sat, 16 Mar 2024, Eberhard W Lisse wrote:
[...]
> A fresh installation of TeXLive2024 yesterday should have installed all
> necessary files.
>
On Sat, 16 Mar 2024, Eberhard W Lisse wrote:
I needed to (re-)install footmisc with the tlmgr.
El,
A fresh installation of TeXLive2024 yesterday should have installed all
necessary files.
But Lyx has an option of looking at the logfiles.
And you did not mention what OS you use, on the Mac
nts should stay put.
Paul,
The issue since the TeXLive2024 upgrade is lyx finding a pdflatex error.
While updating tlmgr and fmtutils from within /etc/cron.weekly earlier this
morning I ran it again manually just now and it exited with an error code 3:
No pages of output.
Transcript written o
(mwe.tex) was written to the buffer directory, but there
was no LaTeX log file because LyX never reached the point of running
pdflatex (or whatever), since the export was flagged as incorrect.
Clicking "View Complete Log..." in the error message pane caused LyX to
calculate a name and location for the lo
On Sat, 16 Mar 2024, Paul Rubin wrote:
I trust you are leaving LyX open while you look for the temp directory. If
you go to Tools > Preferences... > Paths, what do you have filled in for
"Temporary directory:"?
Paul,
/tmp, and that's where I've found LyX_tempbuf* before.
Thanks,
Rich
--
ied compiling the MWE for
> the math issues still unresolve. A message box displayed: The
> external program pdflatex finished with an error. It is recommended
> you fix the cause of the external program's error (check the logs).
>
> 1. Where do I find the appropriate log file
On 3/16/24 11:39, Rich Shepard wrote:
On Sat, 16 Mar 2024, Rich Shepard wrote:
The first place I looked was /tmp/lyx_* but both subdirectories were
empty.
Just invoked Lyx-2.3.6.1 and tried compiling mwe.lyx using pdflatex. Same
message box displayed; image attached.
There is no lyx
On Sat, 16 Mar 2024, Rich Shepard wrote:
The first place I looked was /tmp/lyx_* but both subdirectories were
empty.
Just invoked Lyx-2.3.6.1 and tried compiling mwe.lyx using pdflatex. Same
message box displayed; image attached.
There is no lyx directory in /tmp.
All new issues for me
On Fri, 15 Mar 2024, Paul Rubin wrote:
The log file will be in the temp directory created by LyX for the document.
Most likely you'll start spelunking in /tmp, but if you set up the temp
directory to be somewhere else you can find out where in Tools > Preferences
Paths > Temporary directory.
On 3/15/24 17:54, Rich Shepard wrote:
I upgraded TeXLive from 2023 to 2024 and tried compiling the MWE for the
math issues still unresolve. A message box displayed:
The external program
pdflatex finished with an error. It is recommended you fix the cause
of the external
program's error
I upgraded TeXLive from 2023 to 2024 and tried compiling the MWE for the
math issues still unresolve. A message box displayed:
The external program
pdflatex
finished with an error. It is recommended you fix the cause of the external
program's error (check the logs).
1. Where do I find
no expectation there would be distro installed files that weren't
removed when I removed the TL packages. Removing those remnant files
eliminated the error I got when running a document through pdflatex.
All's well now.
Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman
Herbert Voss said on Tue, 20 Jun 2023 07:01:36 +0200
>Rich,
>
>that looks like a mismatch between TeXLive from TUG
>(/usr/local/texlive/)
>and from your linux distribution (/usr/share/tex...)
>
>what is the output of
>which -a fmtutil-sys
Several years ago I de-installed the
On Tue, 20 Jun 2023, Herbert Voss wrote:
that looks like a mismatch between TeXLive from TUG
(/usr/local/texlive/) and from your linux distribution
(/usr/share/tex...)
Herbert,
I removed the SBo TL packages so there shouldn't be conflicts. Regardless,
if there was something left behind
Am 19.06.23 um 22:16 schrieb Rich Shepard:
###
fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
/usr/share/texmf-var/web2c
for details.
On Mon, 19 Jun 2023, Herbert Voss wrote:
Herbert,
I'm the only user of this host.
fmtutil-sys --all
$ fmtutil-sys --all
fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order):
fmtutil: /usr/local/texlive/2023/texmf-dist/web2c/fmtutil.cnf
fmtutil: fmtutil is using
On Mon, 19 Jun 2023, Paul A. Rubin wrote:
I think the stuff about UTF-8 right above the error message has nothing to
do with the error. The error just got discovered after that log line.
Paul,
Makes sense to me.
Taking the error message at face value, it looks like you somehow ended up
Am 19.06.23 um 19:52 schrieb Rich Shepard:
The problem seems to be a biblatex/utf8 issue. The whole error log is
attached and the error starts at line 500.
Please teach me how to fix this and avoid future occurrences.
it is a problem with your different latex (expl3) files, they don't
On 6/19/23 13:52, Rich Shepard wrote:
The problem seems to be a biblatex/utf8 issue. The whole error log is
attached and the error starts at line 500.
Please teach me how to fix this and avoid future occurrences.
TIA,
Rich
I think the stuff about UTF-8 right above the error message has
On Mon, 19 Jun 2023, Rich Shepard wrote:
The problem seems to be a biblatex/utf8 issue. The whole error log is
attached and the error starts at line 500.
Er, not so. This just popped up again in a different doc without a
bibliography. But, a second ctrl-h to copy the whole error log produced
The problem seems to be a biblatex/utf8 issue. The whole error log is
attached and the error starts at line 500.
Please teach me how to fix this and avoid future occurrences.
TIA,
RichThis is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023) (preloaded
format=pdflatex 2023.5.23) 19 JUN
On Sat, 10 Sep 2022, Paul A. Rubin wrote:
Here's what I would do. Assuming that you have the original document (the
one that won't compile) salted away somewhere, I would take your MWE and
add Chapter 1 and anything else that's missing. If it still compiles, I'd
compare it to the original using
today pdflatex couldn't digest. But,
copying
from the end of the report forward, chapter-by-chapter everything builds.
What other procedure should I use to find what's causing the error?
Rich
Rich,
Here's what I would do. Assuming that you have the original document
(the one that won't compile
. No error. I then added chapters
individually to mwe.lyx, saved and built. No errors. Continued up through
Chapter 2; didn't add Chapter 1 because the report had no issues before I
added text, citations, and the appendices.
So, somewhere in what I added today pdflatex couldn't digest. But, copying
Am 20.12.21 um 19:46 schrieb Jürgen Spitzmüller via lyx-users:
Am Montag, dem 20.12.2021 um 19:39 +0100 schrieb Wolfgang Engelmann via
lyx-users:
I have no \usepackage{scrpage2} in the preamble.
So again: If KOMA-script Book is selected, all is fine?
Yes, as written.
Jürgen
Good! and
Am Montag, dem 20.12.2021 um 19:39 +0100 schrieb Wolfgang Engelmann via
lyx-users:
> I have no \usepackage{scrpage2} in the preamble.
> So again: If KOMA-script Book is selected, all is fine?
Yes, as written.
Jürgen
signature.asc
Description: This is a digitally signed message part
--
Am 20.12.21 um 18:20 schrieb Jürgen Spitzmüller via lyx-users:
Am Montag, dem 20.12.2021 um 18:02 +0100 schrieb Wolfgang Engelmann via
lyx-users:
Is this taken care of if I select in Document Settings > Document
class
> KOMA-script Book
No, but this is not needed.
Hi, Jürgen, and
On Mon, 20 Dec 2021, Jürgen Spitzmüller via lyx-users wrote:
(Whereas the original German version, l2tabu, is of 2016 and also
correctly advises to replace scrpage2 by scrlayer-scrpage.
Jürgen,
I've downloaded both versions.
Thanks very much,
Rich
--
lyx-users mailing list
Am Montag, dem 20.12.2021 um 18:22 +0100 schrieb Jürgen Spitzmüller via
lyx-users:
> There is l2tabuen, but this only has a limited selection and is
> outdated (2007; it mentions scrpage but isn't up to date in this
> regard).
(Whereas the original German version, l2tabu, is of 2016 and also
Am Montag, dem 20.12.2021 um 08:36 -0800 schrieb Rich Shepard via lyx-
users:
> Is there a list of superseded packages and their replacement
> somewhere?
There is l2tabuen, but this only has a limited selection and is
outdated (2007; it mentions scrpage but isn't up to date in this
regard).
Am Montag, dem 20.12.2021 um 18:02 +0100 schrieb Wolfgang Engelmann via
lyx-users:
> Is this taken care of if I select in Document Settings > Document
> class
> > KOMA-script Book
No, but this is not needed.
>
> (I use Version 2.4.0dev (not released yet)
> Built from git commit hash 53ed3dc0
Am 20.12.21 um 17:26 schrieb Jürgen Spitzmüller via lyx-users:
Am Montag, dem 20.12.2021 um 08:12 -0800 schrieb Rich Shepard via lyx-
users:
Using the KOMA-Script letter template I've used before I cannot
compile a
letter using pdflatex. The LaTeX error is: File `scrpage2.sty' not
found
On Mon, 20 Dec 2021, Jürgen Spitzmüller via lyx-users wrote:
Try
\usepackage{scrlayer-scrpage}
instead. This package has superseded scrpage2. It should work as a
drop-in replacement.
Jürgen,
Yes, that helps. And it shows how long it's been since I used that template.
Is there a list of
Am Montag, dem 20.12.2021 um 08:12 -0800 schrieb Rich Shepard via lyx-
users:
> Using the KOMA-Script letter template I've used before I cannot
> compile a
> letter using pdflatex. The LaTeX error is: File `scrpage2.sty' not
> found.
>
> The file is present in /usr/share/te
Using the KOMA-Script letter template I've used before I cannot compile a
letter using pdflatex. The LaTeX error is: File `scrpage2.sty' not found.
The file is present in /usr/share/texmf/tex/latex/koma-script/scrpage2.sty
and the file's settings include it: \usepackage{scrpage2,url}.
How do I
On Mon, 27 Jul 2020, Paul A. Rubin wrote:
Just to be clear, you removed not just the bibliography but also all the
citations?
Paul,
Oops! Some but not all. Now all are removed and the issue's resolved.
Mea culpa!
Stay well,
Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
On 7/27/20 12:16 PM, Rich Shepard wrote:
I'm converting a publication with references and a bibliography to a
slide
presentation. In the Settings the document class is KOMA-Script
article and
I leave the bibliography choices at their defaults. I've removed the
bibliography from the end of the
I'm converting a publication with references and a bibliography to a slide
presentation. In the Settings the document class is KOMA-Script article and
I leave the bibliography choices at their defaults. I've removed the
bibliography from the end of the document.
Yet, when I compile it lyx
Am Mittwoch, den 12.02.2020, 07:28 +0100 schrieb Jürgen Spitzmüller:
>> Am Dienstag, den 11.02.2020, 21:44 +0100 schrieb Martin Weise:
>>> Ok, here's something I (just) noticed: pdflatex, when run without
>>> arguments, produces a .dvi file from HelloWorld.tex. It is only if
&g
On 12.02.20 09:16, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 12.02.2020, 08:41 +0100 schrieb Martin Weise:
>> That did the trick!
> Excellent.
>
>> No clue though as to why I had to take the extra step of adding
>> something to a config file. Never happened to me with a fresh texlive
>> install
Am Mittwoch, den 12.02.2020, 08:41 +0100 schrieb Martin Weise:
> That did the trick!
Excellent.
> No clue though as to why I had to take the extra step of adding
> something to a config file. Never happened to me with a fresh texlive
> install before. And obviously, it had nothing to do with
d this one line, but use the whole file I sent.
>
>> Unfortunately, pdflatex still
>> produces a dvi file.
>>
>> Anything I need to do additionally, i.e. to activate the new config
>> file?
> Yes, you need to run (as root presumably)
>
> fmtutil --al
Am Mittwoch, den 12.02.2020, 07:51 +0100 schrieb Martin Weise:
> The file was there; however, it was empty.
So this is definitely the culprit.
> I added the line as per your suggestion.
I suggest to not only add this one line, but use the whole file I sent.
> Unfortunately, pdfla
On 12.02.20 07:32, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 12.02.2020, 07:28 +0100 schrieb Jürgen Spitzmüller:
>> Am Dienstag, den 11.02.2020, 21:44 +0100 schrieb Martin Weise:
>>> Ok, here's something I (just) noticed: pdflatex, when run without
>>> arguments
Am Mittwoch, den 12.02.2020, 07:28 +0100 schrieb Jürgen Spitzmüller:
> Am Dienstag, den 11.02.2020, 21:44 +0100 schrieb Martin Weise:
> > Ok, here's something I (just) noticed: pdflatex, when run without
> > arguments, produces a .dvi file from HelloWorld.tex. It is only if
&g
Am Dienstag, den 11.02.2020, 21:44 +0100 schrieb Martin Weise:
> Ok, here's something I (just) noticed: pdflatex, when run without
> arguments, produces a .dvi file from HelloWorld.tex. It is only if I
> specify "-output-format=pdf" that it creates a .pdf file.
>
&g
On 2/11/20 3:44 PM, Martin Weise wrote:
> On 11.02.20 20:44, Kornel Benko wrote:
>> Am Tue, 11 Feb 2020 14:33:23 -0500
>> schrieb "Paul A. Rubin" :
>>
>>>>> If you open a terminal in the temp directory and run pdflatex against
>>>>>
On 2/11/20 3:44 PM, Martin Weise wrote:
On 11.02.20 20:44, Kornel Benko wrote:
Am Tue, 11 Feb 2020 14:33:23 -0500
schrieb "Paul A. Rubin" :
If you open a terminal in the temp directory and run pdflatex against
the .tex file, does it compile? If not, is there a meaningful err
On 11.02.20 20:44, Kornel Benko wrote:
> Am Tue, 11 Feb 2020 14:33:23 -0500
> schrieb "Paul A. Rubin" :
>
>>>> If you open a terminal in the temp directory and run pdflatex against
>>>> the .tex file, does it compile? If not, is there a meaningful error
&
Am Tue, 11 Feb 2020 14:33:23 -0500
schrieb "Paul A. Rubin" :
> >> If you open a terminal in the temp directory and run pdflatex against
> >> the .tex file, does it compile? If not, is there a meaningful error
> >> message in the terminal?
> >>
> &
) for almost two years). However, I recently switched
laptops and therefore needed to reinstall ubuntu.
On the new machine, LyX fails to export pdf files via pdflatex and
LuaTeX. There is no pdf file after running export. The only thing that
does work is using ps2pdf.
Here's the message output from Lyx
On 11.02.20 19:57, Paul A. Rubin wrote:
> On 2/11/20 11:34 AM, Martin Weise wrote:
>>
>> LaTeX.cpp (658): Log line: )) (/home/martin/Desktop/HelloWord.aux)
>> LaTeX.cpp (658): Log line: \openout1 = `HelloWord.aux'.
>>
> It seems to have grabbed an existing .aux file from your desktop (as
> opposed
Am Tue, 11 Feb 2020 13:57:09 -0500
schrieb "Paul A. Rubin" :
> On 2/11/20 11:34 AM, Martin Weise wrote:
> >
> > LaTeX.cpp (658): Log line: )) (/home/martin/Desktop/HelloWord.aux)
> > LaTeX.cpp (658): Log line: \openout1 = `HelloWord.aux'.
> >
> It seems to have grabbed an existing .aux file
On 11.02.20 19:57, Paul A. Rubin wrote:
> On 2/11/20 11:34 AM, Martin Weise wrote:
>>
>> LaTeX.cpp (658): Log line: )) (/home/martin/Desktop/HelloWord.aux)
>> LaTeX.cpp (658): Log line: \openout1 = `HelloWord.aux'.
>>
> It seems to have grabbed an existing .aux file from your desktop (as
>
On 2/11/20 11:34 AM, Martin Weise wrote:
LaTeX.cpp (658): Log line: )) (/home/martin/Desktop/HelloWord.aux)
LaTeX.cpp (658): Log line: \openout1 = `HelloWord.aux'.
It seems to have grabbed an existing .aux file from your desktop (as
opposed to generating a clean one in the LyX temp
On 2/11/20 11:34 AM, Martin Weise wrote:
LaTeX.cpp (658): Log line: Output written on HelloWord.dvi (1 page, 236
bytes).
Kornel was correct about the .dvi file being a clue. When I compile your
HelloWorld example here, the corresponding line shows a .pdf file being
written, as one would
paragraph 0 ptr 0x5565b5aebf00 ''
Paragraph.cpp (2313): Paragraph::latex... 0x5565b5aebf00
Paragraph.cpp (2737): Paragraph::latex... done 0x5565b5aebf00
output_latex.cpp (1255): TeXOnePar for paragraph 0 done; ptr
0x5565b5aebf00 next 0
Buffer.cpp (1965): makeLaTeXFile...done
Converter.cpp (377): Con
Am Tue, 11 Feb 2020 10:38:58 -0500
schrieb "Paul A. Rubin" :
> >> The lock file is a bit odd. I would expect that to be deleted after
> >> configuration completed.
I too, but here it is also not deleted.
> >> It might help to see the contents of configure.log. Possibly something
> >> went splat
On 2/11/20 10:20 AM, Martin Weise wrote:
On 11.02.20 16:13, Paul A. Rubin wrote:
On 2/11/20 6:04 AM, Martin Weise wrote:
On 11.02.20 11:55, Kornel Benko wrote:
Am Tue, 11 Feb 2020 11:21:11 +0100
schrieb Martin Weise :
[snip]
Yes, it looks related. Apparently the 'pdflatex' called from lyx
On 11.02.20 16:13, Paul A. Rubin wrote:
> On 2/11/20 6:04 AM, Martin Weise wrote:
>> On 11.02.20 11:55, Kornel Benko wrote:
>>> Am Tue, 11 Feb 2020 11:21:11 +0100
>>> schrieb Martin Weise :
>>>
>>> [snip]
>>>>> Yes, it looks related. App
On 2/11/20 6:04 AM, Martin Weise wrote:
On 11.02.20 11:55, Kornel Benko wrote:
Am Tue, 11 Feb 2020 11:21:11 +0100
schrieb Martin Weise :
[snip]
Yes, it looks related. Apparently the 'pdflatex' called from lyx does not create
the required pdf file to be used to display the image.
Maybe
+0100
schrieb Martin Weise :
I'm wondering whether LyX successfully compiles the PDF file in the
temp directory but then fails to copy or move it to the target
directory.
Paul
No, Document -> View (pdflatex) produces nothing either. Nor does
the
LuaTeX way. LyX leaves no pdf f
On 11.02.20 11:55, Kornel Benko wrote:
> Am Tue, 11 Feb 2020 11:21:11 +0100
> schrieb Martin Weise :
>
> [snip]
>>> Yes, it looks related. Apparently the 'pdflatex' called from lyx does not
>>> create
>>> the required pdf file to be used to display the image
Am Tue, 11 Feb 2020 11:21:11 +0100
schrieb Martin Weise :
[snip]
> > Yes, it looks related. Apparently the 'pdflatex' called from lyx does not
> > create
> > the required pdf file to be used to display the image.
> > Maybe the environment used by lyx is different fro
>>>>>>>> schrieb Martin Weise :
>>>>>>>>
>>>>>>>>>> I'm wondering whether LyX successfully compiles the PDF file in the
>>>>>>>>>> temp directory but then fails to copy or move it to the target
&
>
> >>>>>>>> I'm wondering whether LyX successfully compiles the PDF file in the
> >>>>>>>> temp directory but then fails to copy or move it to the target
> >>>>>>>> directory.
> >>>>>>>&g
in the
>>>>>>>> temp directory but then fails to copy or move it to the target
>>>>>>>> directory.
>>>>>>>>
>>>>>>>> Paul
>>>>>>> No, Document -> View (pdflatex) produces nothing either. No
Feb 2020 16:54:27 +0100
>>>>> schrieb Martin Weise :
>>>>>
>>>>>>> I'm wondering whether LyX successfully compiles the PDF file in the
>>>>>>> temp directory but then fails to copy or move it to the target
>&g
> > > temp directory but then fails to copy or move it to the target
> > > > > > > directory.
> > > > > > >
> > > > > > > Paul
> > > > > > No, Document -> View (pdflatex) produces nothing either. Nor does
> &
the PDF file in the
temp directory but then fails to copy or move it to the target directory.
Paul
No, Document -> View (pdflatex) produces nothing either. Nor does the
LuaTeX way. LyX leaves no pdf file in the temp dir. It just leaves .aux,
.dvi,. log, .tex and .dep-pdf files.
Mar
ring whether LyX successfully compiles the PDF file in the
>>>>> temp directory but then fails to copy or move it to the target directory.
>>>>>
>>>>> Paul
>>>>>
>>>> No, Document -> View (pdflatex) produces nothing either. Nor d
temp directory but then fails to copy or move it to the target directory.
> >>>
> >>> Paul
> >>>
> >> No, Document -> View (pdflatex) produces nothing either. Nor does the
> >> LuaTeX way. LyX leaves no pdf file in the temp dir. It just l
t;>> Paul
>>>
>> No, Document -> View (pdflatex) produces nothing either. Nor does the
>> LuaTeX way. LyX leaves no pdf file in the temp dir. It just leaves .aux,
>> .dvi,. log, .tex and .dep-pdf files.
>>
>> Martin
>
> That (.dvi) is the clue
been doing so
>>>> (successfully) for almost two years). However, I recently switched
>>>> laptops and therefore needed to reinstall ubuntu.
>>>>
>>>> On the new machine, LyX fails to export pdf files via pdflatex and
>>>> LuaTeX. There is
to reinstall ubuntu.
On the new machine, LyX fails to export pdf files via pdflatex and
LuaTeX. There is no pdf file after running export. The only thing that
does work is using ps2pdf.
Here's the message output from Lyx:
***
05:44:25.151: Previewing ...
05:44:25.154: (buffer-view: Ctrl+R)
05:44
Am Mon, 10 Feb 2020 16:54:27 +0100
schrieb Martin Weise :
> > I'm wondering whether LyX successfully compiles the PDF file in the
> > temp directory but then fails to copy or move it to the target directory.
> >
> > Paul
> >
> No, Document -> View (pdflate
I am using LyX 2.3.3 on Ubuntu 18.04 (and i have been doing so
>>>> (successfully) for almost two years). However, I recently switched
>>>> laptops and therefore needed to reinstall ubuntu.
>>>>
>>>> On the new machine, LyX fails to export pdf files
refore needed to reinstall ubuntu.
>>
>> On the new machine, LyX fails to export pdf files via pdflatex and
>> LuaTeX. There is no pdf file after running export. The only thing that
>> does work is using ps2pdf.
>>
>> Here's the message output from Lyx:
>>
>> **
On 2/9/20 1:56 PM, Martin Weise wrote:
Dear all,
I am using LyX 2.3.3 on Ubuntu 18.04 (and i have been doing so
(successfully) for almost two years). However, I recently switched
laptops and therefore needed to reinstall ubuntu.
On the new machine, LyX fails to export pdf files via pdflatex
o
> >> (successfully) for almost two years). However, I recently switched
> >> laptops and therefore needed to reinstall ubuntu.
> >>
> >> On the new machine, LyX fails to export pdf files via pdflatex and
> >> LuaTeX. There is no pdf file after run
> laptops and therefore needed to reinstall ubuntu.
>>
>> On the new machine, LyX fails to export pdf files via pdflatex and
>> LuaTeX. There is no pdf file after running export. The only thing that
>> does work is using ps2pdf.
>>
>> Here's the message output from Ly
ew machine, LyX fails to export pdf files via pdflatex and
> LuaTeX. There is no pdf file after running export. The only thing that
> does work is using ps2pdf.
>
> Here's the message output from Lyx:
>
> ***
> 05:44:25.151: Previewing ...
> 05:44:25.154: (buffer-view: Ct
Dear all,
I am using LyX 2.3.3 on Ubuntu 18.04 (and i have been doing so
(successfully) for almost two years). However, I recently switched
laptops and therefore needed to reinstall ubuntu.
On the new machine, LyX fails to export pdf files via pdflatex and
LuaTeX. There is no pdf file after
Am Montag, 30. Juli 2018 11:44:00 CEST schrieb Baris Erkus
:
> On 28-Jul-18 3:28 PM, Murat Yildizoglu wrote:
> Hello,
> I am working on a new book and suddenly I have started to meet a problem with
> the graphics that are included in the document : when I pdflatex the doc, I
Benko
Sujet : Re: Grrr! Loosing my mind on graphic options in pdflatex
> Thank you Kornel,
> This has solved my second problem. I have the bad habit of not directly
> working in the LyX document with a text editor. Searching for turkish, I have
> been able to locate two empty pl
Am Samstag, 28. Juli 2018 10:12:20 CEST schrieb Rich Shepard
:
> On Sat, 28 Jul 2018, Murat Yildizoglu wrote:
>
> > *OK, I think I have located the source of the problem, but I do not know
> > how to solve it in LyX: *I have pasted a citation in English coming from
> > an article I have written
On Sat, 28 Jul 2018, Murat Yildizoglu wrote:
*OK, I think I have located the source of the problem, but I do not know
how to solve it in LyX: *I have pasted a citation in English coming from
an article I have written in Turkish, and then, Lyx automatically puts the
option turkish in the
have any text in
> Turkish in my document)?
>
> All help would be very much appreciated.
>
> Murat
>
> Le sam. 28 juil. 2018 à 16:30, Rich Shepard a
> écrit :
>
>> On Sat, 28 Jul 2018, Murat Yildizoglu wrote:
>>
>> > I am working on a new book and s
et a problem
> > with the graphics that are included in the document : when I pdflatex the
> > doc, I get a lot of error messages all concerning the options set in the
> > \includegraphics instructions. If I fo not scale the graph, it prints
> > (with the original size of course), and if I
On Sat, 28 Jul 2018, Murat Yildizoglu wrote:
I am working on a new book and suddenly I have started to meet a problem
with the graphics that are included in the document : when I pdflatex the
doc, I get a lot of error messages all concerning the options set in the
\includegraphics instructions
You can tell knitr where to put the figures exactly, it does create a
figure directory, but I do not have this issue either, when using knitr.
Latest version of everything?
el
On 2018-05-16 16:22 , Uwe Thuemmel wrote:
> I realised that the problem appears when I am using the knitr module
> (but
;accou...@uwethuemmel.com
> <mailto:accou...@uwethuemmel.com>> wrote:
>
> Dear fellow users,
>
> I have figures (as pdf) and tables (as LyX child documents) in
> subdirectories ./figures and ./tables. When I export from LyX
> 2.3.0 on Mac to LaTeX (pdflatex), the
./tables. When I export from LyX
> 2.3.0 on Mac to LaTeX (pdflatex), the relative paths to these
> figures and tables are messed up. In particular, they are
> replaced by absolute paths where ‘/‘ is replaced by ‘_'. For
> example, a relative path /figures/fi
On Sun, May 13, 2018 at 9:37 AM, Uwe Thuemmel <accou...@uwethuemmel.com>
wrote:
> Dear fellow users,
>
> I have figures (as pdf) and tables (as LyX child documents) in
> subdirectories ./figures and ./tables. When I export from LyX 2.3.0 on Mac
> to LaTeX (pdflatex
Dear fellow users,
I have figures (as pdf) and tables (as LyX child documents) in subdirectories
./figures and ./tables. When I export from LyX 2.3.0 on Mac to LaTeX
(pdflatex), the relative paths to these figures and tables are messed up. In
particular, they are replaced by absolute paths
e problems most of the time.
If you post a minimal example, someone might have a suggestion.
> Can I tell lyx to run pdflatex, say, three times and/or delete all temporary
> files before compiling?
I think that LyX should delete temporary files when compiling after the
previous compile
Hello all,
I'm having issues with misaligned float elements, TOC items, captions
and such (tufte-book class). Restarting lyx and compiling a fresh pdf
document (whicht takes longer than otherwise) solves these problems most
of the time.
Can I tell lyx to run pdflatex, say, three times
>
> "The following LaTeX backend has been configured to allow execution of
> external programs for any document:
> pdflatex --shell-escape $$i
> This is a dangerous configuration. Please, consider using the support
> offered by LyX for allowing this privilege on
1 - 100 of 1918 matches
Mail list logo
