Re: Strategies for locating errors

[Rainer M Krug]

Will Furnass wrfurna...@sheffield.ac.uk writes:

 On 05/05/15 12:47, Nikos Alexandris wrote:
 * Will Furnass wrfurna...@sheffield.ac.uk [2015-05-05 11:51:56 +0100]:
 
 How do others locate compilation errors in large multi-file documents?

 snip
 
 Something like binary search: split in two halfs, try to find out
 which half does not compile. Then, again, repeat the same: split in
 half, identify the erroneous part. Sooner or later you'll nail the
 source of the error.

 A good idea, but could LyX be improved to make locating errors less
 manual though?  For example, if a mapping was generated at compile time
 from LyX lines to TeX lines then buttons could be added to the
 compilation pane to move the cursor between the lines referenced in
 error messages.

I am by no means a LaTeX expert -0 so I might be wrong, but - the LaTeX
error messages are already quite cryptic, and the error you quote
(Missing } inserted' error for 'l.1052') means that the missing } is
inserted in this line - where it is actually missing and what is causing
this does not even LaTeX know - so there is no chance that LyX will be
able to tell you.

Rainer


 Will







-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: Strategies for locating errors

[Nikos Alexandris]

* Will Furnass wrfurna...@sheffield.ac.uk [2015-05-05 11:51:56 +0100]:

 How do others locate compilation errors in large multi-file documents?
 
 I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
 relate that line number to the LyX source.  I then try exporting to tex
 using pdflatex into a temporary directory and search through all 16 tex
 files looking for errors on or near line 1052.
 
 An alternative approach would have been to comment the
 'includes'/'inputs' for various chapters of my thesis then try to
 recompile but this partitioning approach would be slow given that it
 currently takes ~5mins to compile my thesis.
 
 I'm sure I can find the cause of the error eventually; I was just
 wondering if there were a neat way of identifying the location of
 errors.  At present pretty much everything in LyX is a joy and very
 slick apart from locating the source of errors.
 
 FYI, yes I am using a little Evil Red Text (to use \resizebox within
 table floats).

Something like binary search: split in two halfs, try to find out
which half does not compile. Then, again, repeat the same: split in
half, identify the erroneous part. Sooner or later you'll nail the
source of the error.

Cheers, Nikos

Wrong numbering of appendix

[Aline Gautrein]

Hey Lyx-friends,

I use Koma-script class book. I added an appendix to my dissertation and in
the Lyx-file it is correctly numbered with Appendix A. Figure A.1... etc.

My problem: In the pdf-file the A is missing in the headings and the
captions. Headings look like this:

.1.1 Blabla
.1.3 blabla

captions like this:

Figure .1:
Figure .2:

Do I have to insert something in the preamble, saying that letters are
allowed in heading- and caption numbers?

Which command do I need?

Thanks a lot!

Re: Wrong numbering of appendix

[Aline Gautrein]

Hey!

I solved the problem: You must not put an \backmatter in front of the
appendix.


Greetings!

2015-05-05 13:34 GMT+02:00 Aline Gautrein gautr...@googlemail.com:

 Hey Lyx-friends,

 I use Koma-script class book. I added an appendix to my dissertation and
 in the Lyx-file it is correctly numbered with Appendix A. Figure A.1... etc.

 My problem: In the pdf-file the A is missing in the headings and the
 captions. Headings look like this:

 .1.1 Blabla
 .1.3 blabla

 captions like this:

 Figure .1:
 Figure .2:

 Do I have to insert something in the preamble, saying that letters are
 allowed in heading- and caption numbers?

 Which command do I need?

 Thanks a lot!

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 12:47, Nikos Alexandris wrote:
 * Will Furnass wrfurna...@sheffield.ac.uk [2015-05-05 11:51:56 +0100]:
 
 How do others locate compilation errors in large multi-file documents?

snip
 
 Something like binary search: split in two halfs, try to find out
 which half does not compile. Then, again, repeat the same: split in
 half, identify the erroneous part. Sooner or later you'll nail the
 source of the error.

A good idea, but could LyX be improved to make locating errors less
manual though?  For example, if a mapping was generated at compile time
from LyX lines to TeX lines then buttons could be added to the
compilation pane to move the cursor between the lines referenced in
error messages.

Will

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 13:27, Rainer M Krug wrote:
 Will Furnass wrfurna...@sheffield.ac.uk writes:
 
 could LyX be improved to make locating errors less manual
 though? For example, if a mapping was generated at compile time
 from LyX lines to TeX lines then buttons could be added to the
 compilation pane to move the cursor between the lines referenced
 in error messages.
 
 I am by no means a LaTeX expert -0 so I might be wrong, but - the 
 LaTeX error messages are already quite cryptic, and the error you 
 quote (Missing } inserted' error for 'l.1052') means that the 
 missing } is inserted in this line - where it is actually
 missing and what is causing this does not even LaTeX know - so
 there is no chance that LyX will be able to tell you.

True, but the line number associated with a LaTeX error is a useful
clue when fault-finding and being able to quickly move the cursor to
the corresponding line in LyX could make fixing broken documents much
quicker in many situations.  The compilation pane could display a
caveat next to buttons for moving the cursor between error line
numbers saying something like 'the root cause of this error may not
lie at this location'.

Will

Re: Strategies for locating errors

[Gordon Cooper]

On 06/05/15 09:57, Will Furnass wrote:

That works perfectly if the error is in the master document but not if
the error is in a child document (of which I have quite a few).


I have been having similar problems with errors, mainly relating to 
producing printable pdf versions
of a Software User Manual that has fairly frequent updates and changes. 
This manual is a team effort
written with Lyx with an on-line HTML version being the primary release 
format. The HTML does not
show some Latex errors but they do appear when a pdf conversion is 
attempted, and my team task

is to deal with the pdfs.

Error reports give a line number, which has been difficult to translate 
into a location in the Lyx file.
However, I'm now experimenting with the Latex Editor, Texmaker.  It 
appears to happily present the
Lyx files, all with line numbers. Perhaps this will help my error 
finding, we can but see.


Gordon
Tauranga
New Zealand.

Re: Disable editing / read only menu option?

[Stephan Witt]

Am 05.05.2015 um 13:21 schrieb Rainer M Krug rai...@krugs.de:

 Liviu Andronic landronim...@gmail.com writes:
 
 On Tue, May 5, 2015 at 10:40 AM, Rainer M Krug rai...@krugs.de wrote:
 Liviu Andronic landronim...@gmail.com writes:
 
 On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak skost...@lyx.org wrote:
 On Mon, May 4, 2015 at 8:05 AM, Helge Hafting helge.haft...@hist.no 
 wrote:
 
 
 Den 23. mars 2015 17:57, skrev Scott Kostyshak:
 
 Dear LyX users,
 
 What are your thoughts on having an option in the menu called
 something like Disable editing or Read only, which would make it
 so you could not edit the current document?
 
 Have you tried making the file itself read-only? LyX already knows about
 read-only files and will not allow editing then.
 
 Good point. I think the advantage of the feature being discussed at
 http://www.lyx.org/trac/ticket/6692
 is to give users a user-friendly way to do it inside of LyX.
 
 
 Indeed. Setting a file read-only on the disk may work well enough for
 Linux users, but Windows or Mac users can't be bothered with such
 low-level details.
 
 Hang on - I am a Mac user, use emacs, know (and love!) the terminal,
 regularly edit file permissions and owners - maybe because in my heart I
 am a Linux person? :-)
 

I'm a Unix-user with a Mac too. But there is no need to use the terminal for 
this task.
Using the Finder there is the Command-i or RBM-Info and you get a panel to set 
the file permissions.

With Windows it's similar.

 
 Mac users addicted to Emacs must be a very rare breed indeed... :)
 
 I don't think so - I am surprised how many are there actually when you
 look in the mailing lists of emacs, org-mode or ess (Emacs Speaks
 Statistics). I see a Mac as a hybrid: on the one side, you have the GUI
 which works perfectly (in contrast to windows...) and *requires* not
 much tinkering to make it work nearly perfect, while on the other side
 you can use easily all the Linux software (see e.g. the homebrew project
 http://brew.sh for the terminal / console software or LyX ...) - under
 the hood, OSX is not much different then Linux. So I have the best from
 both worlds, and probably the best hardware in the world.
 
 
 
 Having a quick way to set this within LyX can be useful, and even
 within the same LyX session you can set/unset this status.
 
 I completely agree - an option to set a file read-only from within LyX
 would be quite useful. Even Emacs can do this - and emacs users are
 addicted to the terminal!
 
 I even think this should not be hidden in a menu, but in the open dialog
 and in the tab itself, so that one can easily set it when opening a file
 and change (and see the actual status!) without having to go into a menu.

I don't like the proposal to extend the open dialog. This is nearly impossible
with native dialogs and the Qt-specific dialogs look so strange.

Stephan

Set location of Source and Messages panes in Lyx UI

[Gilles Moyse]

Hi.

I have got a slight problem to set the location of the Source and Messages
panes in the Lyx UI (Debian, LyX Version 2.1.3). For some reason, my Lyx UI
has been reset, so the Source and Messages panes were not displayed. After
having them displayed again (View / Source Pane and View / Messages Pane),
I cannot find a way to display them side by side: they are either undocked
and hence on top of the main pane, or displayed as two tabs - I cannot have
them shown simultaneously side by side.

Am I missing something ?

Thanks,

Gilles

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 15:06, Wolfgang Engelmann wrote:
 That was the reason I was asking a while ago, whether the latex
 source panel (under view) could show the tex line number. But I was
 told it is not possible under lyx.

That would certainly be a step in the right direction.  Given that we
already have forward and backward search between LyX and a PDF viewer
using SyncTeX then something similar for LyX to/from TeX should be feasible.

Will

Re: Strategies for locating errors

[Wolfgang Engelmann]

Am 05.05.2015 um 15:18 schrieb Will Furnass:

On 05/05/15 13:27, Rainer M Krug wrote:

Will Furnass wrfurna...@sheffield.ac.uk writes:

could LyX be improved to make locating errors less manual
though? For example, if a mapping was generated at compile time
from LyX lines to TeX lines then buttons could be added to the
compilation pane to move the cursor between the lines referenced
in error messages.

I am by no means a LaTeX expert -0 so I might be wrong, but - the
LaTeX error messages are already quite cryptic, and the error you
quote (Missing } inserted' error for 'l.1052') means that the
missing } is inserted in this line - where it is actually
missing and what is causing this does not even LaTeX know - so
there is no chance that LyX will be able to tell you.

True, but the line number associated with a LaTeX error is a useful
clue when fault-finding and being able to quickly move the cursor to
the corresponding line in LyX could make fixing broken documents much
quicker in many situations.  The compilation pane could display a
caveat next to buttons for moving the cursor between error line
numbers saying something like 'the root cause of this error may not
lie at this location'.

Will

That was the reason I was asking a while ago, whether the latex source 
panel (under view) could show the tex line number. But I was told it is 
not possible under lyx.

Wolfgang

quick question

[Kolokytha, Selina]

Kindly advise if LYX works on Windows 8 as I do not see the relevant download 
option on your website.

Many thanks
Selina

Re: Strategies for locating errors

[Will Furnass]

On 5 May 2015 at 21:38, Georg Baum georg.b...@post.rwth-aachen.de wrote:


 If you select the error item in the error dialog then the corresponding LyX
 contents should should be selected in the main area as well. This is not
 always 100% correct, but usually the error cause is nearby. Does this not
 work in your case?


Ah, I hadn't noticed that before!  That works perfectly if the error is in
the master document but not if the error is in a child document (of which I
have quite a few).

If would be great if LyX would switch to/open the child document containing
the likely location of the error and move the cursor to that location.

Will

Re: Disable editing / read only menu option?

[Liviu Andronic]

On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak skost...@lyx.org wrote:
 On Mon, May 4, 2015 at 8:05 AM, Helge Hafting helge.haft...@hist.no wrote:


 Den 23. mars 2015 17:57, skrev Scott Kostyshak:

 Dear LyX users,

 What are your thoughts on having an option in the menu called
 something like Disable editing or Read only, which would make it
 so you could not edit the current document?

 Have you tried making the file itself read-only? LyX already knows about
 read-only files and will not allow editing then.

 Good point. I think the advantage of the feature being discussed at
 http://www.lyx.org/trac/ticket/6692
 is to give users a user-friendly way to do it inside of LyX.

Indeed. Setting a file read-only on the disk may work well enough for
Linux users, but Windows or Mac users can't be bothered with such
low-level details. Having a quick way to set this within LyX can be
useful, and even within the same LyX session you can set/unset this status.

Liviu



 Scott



-- 
Do you think you know what math is?
http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02
Or what it means to be intelligent?
http://www.ideasroadshow.com/issues/john-duncan-2013-08-30
Think again:
http://www.ideasroadshow.com/library

Re: Disable editing / read only menu option?

[Rainer M Krug]

Liviu Andronic landronim...@gmail.com writes:

 On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak skost...@lyx.org wrote:
 On Mon, May 4, 2015 at 8:05 AM, Helge Hafting helge.haft...@hist.no wrote:


 Den 23. mars 2015 17:57, skrev Scott Kostyshak:

 Dear LyX users,

 What are your thoughts on having an option in the menu called
 something like Disable editing or Read only, which would make it
 so you could not edit the current document?

 Have you tried making the file itself read-only? LyX already knows about
 read-only files and will not allow editing then.

 Good point. I think the advantage of the feature being discussed at
 http://www.lyx.org/trac/ticket/6692
 is to give users a user-friendly way to do it inside of LyX.


 Indeed. Setting a file read-only on the disk may work well enough for
 Linux users, but Windows or Mac users can't be bothered with such
 low-level details.

Hang on - I am a Mac user, use emacs, know (and love!) the terminal,
regularly edit file permissions and owners - maybe because in my heart I
am a Linux person? :-)

 Having a quick way to set this within LyX can be useful, and even
 within the same LyX session you can set/unset this status.

I completely agree - an option to set a file read-only from within LyX
would be quite useful. Even Emacs can do this - and emacs users are
addicted to the terminal!

I even think this should not be hidden in a menu, but in the open dialog
and in the tab itself, so that one can easily set it when opening a file
and change (and see the actual status!) without having to go into a menu.

It would be quite nice, if read-only buffers would have e.g. a red
border, independent of why they are read-only.

Cheers,

Rainer


 Liviu



 Scott

-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: Strategies for locating errors

[Georg Baum]

Will Furnass wrote:

 How do others locate compilation errors in large multi-file documents?
 
 I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
 relate that line number to the LyX source.  I then try exporting to tex
 using pdflatex into a temporary directory and search through all 16 tex
 files looking for errors on or near line 1052.

If you select the error item in the error dialog then the corresponding LyX 
contents should should be selected in the main area as well. This is not 
always 100% correct, but usually the error cause is nearby. Does this not 
work in your case?


Georg

Re: Strategies for locating errors

[Georg Baum]

Wolfgang Engelmann wrote:

 That was the reason I was asking a while ago, whether the latex source
 panel (under view) could show the tex line number. But I was told it is
 not possible under lyx.

Why that? Of course it would only be possible if the panel is set to show 
the full source (otherwise the line number would be wrong), but in that case 
it should not be a problem.



Georg

Re: quick question

[John Kane]

Apparently yes.
http://wiki.lyx.org/Windows/Windows

On 5 May 2015 at 13:15, Kolokytha, Selina s.koloky...@ucl.ac.uk wrote:

  Kindly advise if LYX works on Windows 8 as I do not see the relevant
 download option on your website.



 Many thanks

 Selina








-- 
John Kane
Kingston ON Canada

Strategies for locating errors

[Will Furnass]

How do others locate compilation errors in large multi-file documents?

I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
relate that line number to the LyX source.  I then try exporting to tex
using pdflatex into a temporary directory and search through all 16 tex
files looking for errors on or near line 1052.

An alternative approach would have been to comment the
'includes'/'inputs' for various chapters of my thesis then try to
recompile but this partitioning approach would be slow given that it
currently takes ~5mins to compile my thesis.

I'm sure I can find the cause of the error eventually; I was just
wondering if there were a neat way of identifying the location of
errors.  At present pretty much everything in LyX is a joy and very
slick apart from locating the source of errors.

FYI, yes I am using a little Evil Red Text (to use \resizebox within
table floats).

Cheers,

Will

Re: Disable editing / read only menu option?

[Liviu Andronic]

On Tue, May 5, 2015 at 10:40 AM, Rainer M Krug rai...@krugs.de wrote:
 Liviu Andronic landronim...@gmail.com writes:

 On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak skost...@lyx.org wrote:
 On Mon, May 4, 2015 at 8:05 AM, Helge Hafting helge.haft...@hist.no wrote:


 Den 23. mars 2015 17:57, skrev Scott Kostyshak:

 Dear LyX users,

 What are your thoughts on having an option in the menu called
 something like Disable editing or Read only, which would make it
 so you could not edit the current document?

 Have you tried making the file itself read-only? LyX already knows about
 read-only files and will not allow editing then.

 Good point. I think the advantage of the feature being discussed at
 http://www.lyx.org/trac/ticket/6692
 is to give users a user-friendly way to do it inside of LyX.


 Indeed. Setting a file read-only on the disk may work well enough for
 Linux users, but Windows or Mac users can't be bothered with such
 low-level details.

 Hang on - I am a Mac user, use emacs, know (and love!) the terminal,
 regularly edit file permissions and owners - maybe because in my heart I
 am a Linux person? :-)


Mac users addicted to Emacs must be a very rare breed indeed... :)


 Having a quick way to set this within LyX can be useful, and even
 within the same LyX session you can set/unset this status.

 I completely agree - an option to set a file read-only from within LyX
 would be quite useful. Even Emacs can do this - and emacs users are
 addicted to the terminal!

 I even think this should not be hidden in a menu, but in the open dialog
 and in the tab itself, so that one can easily set it when opening a file
 and change (and see the actual status!) without having to go into a menu.

 It would be quite nice, if read-only buffers would have e.g. a red
 border, independent of why they are read-only.

Or have the tab text colored green (as Geany does it), or have the
'(ro)' flag appended to the file name (just like we have * for
modified files).

Liviu


 Cheers,

 Rainer


 Liviu



 Scott

 --
 Rainer M. Krug
 email: Raineratkrugsdotde
 PGP: 0x0F52F982



-- 
Do you think you know what math is?
http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02
Or what it means to be intelligent?
http://www.ideasroadshow.com/issues/john-duncan-2013-08-30
Think again:
http://www.ideasroadshow.com/library

Re: Disable editing / read only menu option?

[Rainer M Krug]

Liviu Andronic landronim...@gmail.com writes:

 On Tue, May 5, 2015 at 10:40 AM, Rainer M Krug rai...@krugs.de wrote:
 Liviu Andronic landronim...@gmail.com writes:

 On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak skost...@lyx.org wrote:
 On Mon, May 4, 2015 at 8:05 AM, Helge Hafting helge.haft...@hist.no 
 wrote:


 Den 23. mars 2015 17:57, skrev Scott Kostyshak:

 Dear LyX users,

 What are your thoughts on having an option in the menu called
 something like Disable editing or Read only, which would make it
 so you could not edit the current document?

 Have you tried making the file itself read-only? LyX already knows about
 read-only files and will not allow editing then.

 Good point. I think the advantage of the feature being discussed at
 http://www.lyx.org/trac/ticket/6692
 is to give users a user-friendly way to do it inside of LyX.


 Indeed. Setting a file read-only on the disk may work well enough for
 Linux users, but Windows or Mac users can't be bothered with such
 low-level details.

 Hang on - I am a Mac user, use emacs, know (and love!) the terminal,
 regularly edit file permissions and owners - maybe because in my heart I
 am a Linux person? :-)


 Mac users addicted to Emacs must be a very rare breed indeed... :)

I don't think so - I am surprised how many are there actually when you
look in the mailing lists of emacs, org-mode or ess (Emacs Speaks
Statistics). I see a Mac as a hybrid: on the one side, you have the GUI
which works perfectly (in contrast to windows...) and *requires* not
much tinkering to make it work nearly perfect, while on the other side
you can use easily all the Linux software (see e.g. the homebrew project
http://brew.sh for the terminal / console software or LyX ...) - under
the hood, OSX is not much different then Linux. So I have the best from
both worlds, and probably the best hardware in the world.



 Having a quick way to set this within LyX can be useful, and even
 within the same LyX session you can set/unset this status.

 I completely agree - an option to set a file read-only from within LyX
 would be quite useful. Even Emacs can do this - and emacs users are
 addicted to the terminal!

 I even think this should not be hidden in a menu, but in the open dialog
 and in the tab itself, so that one can easily set it when opening a file
 and change (and see the actual status!) without having to go into a menu.

 It would be quite nice, if read-only buffers would have e.g. a red
 border, independent of why they are read-only.

 Or have the tab text colored green (as Geany does it), or have the
 '(ro)' flag appended to the file name (just like we have * for
 modified files).

Yup - just something very visible.

Rainer


 Liviu


 Cheers,

 Rainer


 Liviu



 Scott

 --
 Rainer M. Krug
 email: Raineratkrugsdotde
 PGP: 0x0F52F982

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: Disable editing / read only menu option?

[Liviu Andronic]

On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak skost...@lyx.org wrote:
 On Mon, May 4, 2015 at 8:05 AM, Helge Hafting helge.haft...@hist.no wrote:


 Den 23. mars 2015 17:57, skrev Scott Kostyshak:

 Dear LyX users,

 What are your thoughts on having an option in the menu called
 something like Disable editing or Read only, which would make it
 so you could not edit the current document?

 Have you tried making the file itself read-only? LyX already knows about
 read-only files and will not allow editing then.

 Good point. I think the advantage of the feature being discussed at
 http://www.lyx.org/trac/ticket/6692
 is to give users a user-friendly way to do it inside of LyX.

Indeed. Setting a file read-only on the disk may work well enough for
Linux users, but Windows or Mac users can't be bothered with such
low-level details. Having a quick way to set this within LyX can be
useful, and even within the same LyX session you can set/unset this status.

Liviu



 Scott



-- 
Do you think you know what math is?
http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02
Or what it means to be intelligent?
http://www.ideasroadshow.com/issues/john-duncan-2013-08-30
Think again:
http://www.ideasroadshow.com/library

Re: Disable editing / read only menu option?

[Rainer M Krug]

Liviu Andronic landronim...@gmail.com writes:

 On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak skost...@lyx.org wrote:
 On Mon, May 4, 2015 at 8:05 AM, Helge Hafting helge.haft...@hist.no wrote:


 Den 23. mars 2015 17:57, skrev Scott Kostyshak:

 Dear LyX users,

 What are your thoughts on having an option in the menu called
 something like Disable editing or Read only, which would make it
 so you could not edit the current document?

 Have you tried making the file itself read-only? LyX already knows about
 read-only files and will not allow editing then.

 Good point. I think the advantage of the feature being discussed at
 http://www.lyx.org/trac/ticket/6692
 is to give users a user-friendly way to do it inside of LyX.


 Indeed. Setting a file read-only on the disk may work well enough for
 Linux users, but Windows or Mac users can't be bothered with such
 low-level details.

Hang on - I am a Mac user, use emacs, know (and love!) the terminal,
regularly edit file permissions and owners - maybe because in my heart I
am a Linux person? :-)

 Having a quick way to set this within LyX can be useful, and even
 within the same LyX session you can set/unset this status.

I completely agree - an option to set a file read-only from within LyX
would be quite useful. Even Emacs can do this - and emacs users are
addicted to the terminal!

I even think this should not be hidden in a menu, but in the open dialog
and in the tab itself, so that one can easily set it when opening a file
and change (and see the actual status!) without having to go into a menu.

It would be quite nice, if read-only buffers would have e.g. a red
border, independent of why they are read-only.

Cheers,

Rainer


 Liviu



 Scott

-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Strategies for locating errors

[Will Furnass]

How do others locate compilation errors in large multi-file documents?

I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
relate that line number to the LyX source.  I then try exporting to tex
using pdflatex into a temporary directory and search through all 16 tex
files looking for errors on or near line 1052.

An alternative approach would have been to comment the
'includes'/'inputs' for various chapters of my thesis then try to
recompile but this partitioning approach would be slow given that it
currently takes ~5mins to compile my thesis.

I'm sure I can find the cause of the error eventually; I was just
wondering if there were a neat way of identifying the location of
errors.  At present pretty much everything in LyX is a joy and very
slick apart from locating the source of errors.

FYI, yes I am using a little Evil Red Text (to use \resizebox within
table floats).

Cheers,

Will

Re: Disable editing / read only menu option?

[Liviu Andronic]

On Tue, May 5, 2015 at 10:40 AM, Rainer M Krug rai...@krugs.de wrote:
 Liviu Andronic landronim...@gmail.com writes:

 On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak skost...@lyx.org wrote:
 On Mon, May 4, 2015 at 8:05 AM, Helge Hafting helge.haft...@hist.no wrote:


 Den 23. mars 2015 17:57, skrev Scott Kostyshak:

 Dear LyX users,

 What are your thoughts on having an option in the menu called
 something like Disable editing or Read only, which would make it
 so you could not edit the current document?

 Have you tried making the file itself read-only? LyX already knows about
 read-only files and will not allow editing then.

 Good point. I think the advantage of the feature being discussed at
 http://www.lyx.org/trac/ticket/6692
 is to give users a user-friendly way to do it inside of LyX.


 Indeed. Setting a file read-only on the disk may work well enough for
 Linux users, but Windows or Mac users can't be bothered with such
 low-level details.

 Hang on - I am a Mac user, use emacs, know (and love!) the terminal,
 regularly edit file permissions and owners - maybe because in my heart I
 am a Linux person? :-)


Mac users addicted to Emacs must be a very rare breed indeed... :)


 Having a quick way to set this within LyX can be useful, and even
 within the same LyX session you can set/unset this status.

 I completely agree - an option to set a file read-only from within LyX
 would be quite useful. Even Emacs can do this - and emacs users are
 addicted to the terminal!

 I even think this should not be hidden in a menu, but in the open dialog
 and in the tab itself, so that one can easily set it when opening a file
 and change (and see the actual status!) without having to go into a menu.

 It would be quite nice, if read-only buffers would have e.g. a red
 border, independent of why they are read-only.

Or have the tab text colored green (as Geany does it), or have the
'(ro)' flag appended to the file name (just like we have * for
modified files).

Liviu


 Cheers,

 Rainer


 Liviu



 Scott

 --
 Rainer M. Krug
 email: Raineratkrugsdotde
 PGP: 0x0F52F982



-- 
Do you think you know what math is?
http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02
Or what it means to be intelligent?
http://www.ideasroadshow.com/issues/john-duncan-2013-08-30
Think again:
http://www.ideasroadshow.com/library

Re: Disable editing / read only menu option?

[Rainer M Krug]

Liviu Andronic landronim...@gmail.com writes:

 On Tue, May 5, 2015 at 10:40 AM, Rainer M Krug rai...@krugs.de wrote:
 Liviu Andronic landronim...@gmail.com writes:

 On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak skost...@lyx.org wrote:
 On Mon, May 4, 2015 at 8:05 AM, Helge Hafting helge.haft...@hist.no 
 wrote:


 Den 23. mars 2015 17:57, skrev Scott Kostyshak:

 Dear LyX users,

 What are your thoughts on having an option in the menu called
 something like Disable editing or Read only, which would make it
 so you could not edit the current document?

 Have you tried making the file itself read-only? LyX already knows about
 read-only files and will not allow editing then.

 Good point. I think the advantage of the feature being discussed at
 http://www.lyx.org/trac/ticket/6692
 is to give users a user-friendly way to do it inside of LyX.


 Indeed. Setting a file read-only on the disk may work well enough for
 Linux users, but Windows or Mac users can't be bothered with such
 low-level details.

 Hang on - I am a Mac user, use emacs, know (and love!) the terminal,
 regularly edit file permissions and owners - maybe because in my heart I
 am a Linux person? :-)


 Mac users addicted to Emacs must be a very rare breed indeed... :)

I don't think so - I am surprised how many are there actually when you
look in the mailing lists of emacs, org-mode or ess (Emacs Speaks
Statistics). I see a Mac as a hybrid: on the one side, you have the GUI
which works perfectly (in contrast to windows...) and *requires* not
much tinkering to make it work nearly perfect, while on the other side
you can use easily all the Linux software (see e.g. the homebrew project
http://brew.sh for the terminal / console software or LyX ...) - under
the hood, OSX is not much different then Linux. So I have the best from
both worlds, and probably the best hardware in the world.



 Having a quick way to set this within LyX can be useful, and even
 within the same LyX session you can set/unset this status.

 I completely agree - an option to set a file read-only from within LyX
 would be quite useful. Even Emacs can do this - and emacs users are
 addicted to the terminal!

 I even think this should not be hidden in a menu, but in the open dialog
 and in the tab itself, so that one can easily set it when opening a file
 and change (and see the actual status!) without having to go into a menu.

 It would be quite nice, if read-only buffers would have e.g. a red
 border, independent of why they are read-only.

 Or have the tab text colored green (as Geany does it), or have the
 '(ro)' flag appended to the file name (just like we have * for
 modified files).

Yup - just something very visible.

Rainer


 Liviu


 Cheers,

 Rainer


 Liviu



 Scott

 --
 Rainer M. Krug
 email: Raineratkrugsdotde
 PGP: 0x0F52F982

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature

Wrong numbering of appendix

[Aline Gautrein]

Hey Lyx-friends,

I use Koma-script class book. I added an appendix to my dissertation and in
the Lyx-file it is correctly numbered with Appendix A. Figure A.1... etc.

My problem: In the pdf-file the A is missing in the headings and the
captions. Headings look like this:

.1.1 Blabla
.1.3 blabla

captions like this:

Figure .1:
Figure .2:

Do I have to insert something in the preamble, saying that letters are
allowed in heading- and caption numbers?

Which command do I need?

Thanks a lot!

Re: Strategies for locating errors

[Nikos Alexandris]

* Will Furnass wrfurna...@sheffield.ac.uk [2015-05-05 11:51:56 +0100]:

 How do others locate compilation errors in large multi-file documents?
 
 I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
 relate that line number to the LyX source.  I then try exporting to tex
 using pdflatex into a temporary directory and search through all 16 tex
 files looking for errors on or near line 1052.
 
 An alternative approach would have been to comment the
 'includes'/'inputs' for various chapters of my thesis then try to
 recompile but this partitioning approach would be slow given that it
 currently takes ~5mins to compile my thesis.
 
 I'm sure I can find the cause of the error eventually; I was just
 wondering if there were a neat way of identifying the location of
 errors.  At present pretty much everything in LyX is a joy and very
 slick apart from locating the source of errors.
 
 FYI, yes I am using a little Evil Red Text (to use \resizebox within
 table floats).

Something like binary search: split in two halfs, try to find out
which half does not compile. Then, again, repeat the same: split in
half, identify the erroneous part. Sooner or later you'll nail the
source of the error.

Cheers, Nikos

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 12:47, Nikos Alexandris wrote:
 * Will Furnass wrfurna...@sheffield.ac.uk [2015-05-05 11:51:56 +0100]:
 
 How do others locate compilation errors in large multi-file documents?

snip
 
 Something like binary search: split in two halfs, try to find out
 which half does not compile. Then, again, repeat the same: split in
 half, identify the erroneous part. Sooner or later you'll nail the
 source of the error.

A good idea, but could LyX be improved to make locating errors less
manual though?  For example, if a mapping was generated at compile time
from LyX lines to TeX lines then buttons could be added to the
compilation pane to move the cursor between the lines referenced in
error messages.

Will

Re: Strategies for locating errors

[Rainer M Krug]

Will Furnass wrfurna...@sheffield.ac.uk writes:

 On 05/05/15 12:47, Nikos Alexandris wrote:
 * Will Furnass wrfurna...@sheffield.ac.uk [2015-05-05 11:51:56 +0100]:
 
 How do others locate compilation errors in large multi-file documents?

 snip
 
 Something like binary search: split in two halfs, try to find out
 which half does not compile. Then, again, repeat the same: split in
 half, identify the erroneous part. Sooner or later you'll nail the
 source of the error.

 A good idea, but could LyX be improved to make locating errors less
 manual though?  For example, if a mapping was generated at compile time
 from LyX lines to TeX lines then buttons could be added to the
 compilation pane to move the cursor between the lines referenced in
 error messages.

I am by no means a LaTeX expert -0 so I might be wrong, but - the LaTeX
error messages are already quite cryptic, and the error you quote
(Missing } inserted' error for 'l.1052') means that the missing } is
inserted in this line - where it is actually missing and what is causing
this does not even LaTeX know - so there is no chance that LyX will be
able to tell you.

Rainer


 Will







-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: Wrong numbering of appendix

[Aline Gautrein]

Hey!

I solved the problem: You must not put an \backmatter in front of the
appendix.


Greetings!

2015-05-05 13:34 GMT+02:00 Aline Gautrein gautr...@googlemail.com:

 Hey Lyx-friends,

 I use Koma-script class book. I added an appendix to my dissertation and
 in the Lyx-file it is correctly numbered with Appendix A. Figure A.1... etc.

 My problem: In the pdf-file the A is missing in the headings and the
 captions. Headings look like this:

 .1.1 Blabla
 .1.3 blabla

 captions like this:

 Figure .1:
 Figure .2:

 Do I have to insert something in the preamble, saying that letters are
 allowed in heading- and caption numbers?

 Which command do I need?

 Thanks a lot!

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 13:27, Rainer M Krug wrote:
 Will Furnass wrfurna...@sheffield.ac.uk writes:
 
 could LyX be improved to make locating errors less manual
 though? For example, if a mapping was generated at compile time
 from LyX lines to TeX lines then buttons could be added to the
 compilation pane to move the cursor between the lines referenced
 in error messages.
 
 I am by no means a LaTeX expert -0 so I might be wrong, but - the 
 LaTeX error messages are already quite cryptic, and the error you 
 quote (Missing } inserted' error for 'l.1052') means that the 
 missing } is inserted in this line - where it is actually
 missing and what is causing this does not even LaTeX know - so
 there is no chance that LyX will be able to tell you.

True, but the line number associated with a LaTeX error is a useful
clue when fault-finding and being able to quickly move the cursor to
the corresponding line in LyX could make fixing broken documents much
quicker in many situations.  The compilation pane could display a
caveat next to buttons for moving the cursor between error line
numbers saying something like 'the root cause of this error may not
lie at this location'.

Will

Re: Disable editing / read only menu option?

[Stephan Witt]

Am 05.05.2015 um 13:21 schrieb Rainer M Krug rai...@krugs.de:

 Liviu Andronic landronim...@gmail.com writes:
 
 On Tue, May 5, 2015 at 10:40 AM, Rainer M Krug rai...@krugs.de wrote:
 Liviu Andronic landronim...@gmail.com writes:
 
 On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak skost...@lyx.org wrote:
 On Mon, May 4, 2015 at 8:05 AM, Helge Hafting helge.haft...@hist.no 
 wrote:
 
 
 Den 23. mars 2015 17:57, skrev Scott Kostyshak:
 
 Dear LyX users,
 
 What are your thoughts on having an option in the menu called
 something like Disable editing or Read only, which would make it
 so you could not edit the current document?
 
 Have you tried making the file itself read-only? LyX already knows about
 read-only files and will not allow editing then.
 
 Good point. I think the advantage of the feature being discussed at
 http://www.lyx.org/trac/ticket/6692
 is to give users a user-friendly way to do it inside of LyX.
 
 
 Indeed. Setting a file read-only on the disk may work well enough for
 Linux users, but Windows or Mac users can't be bothered with such
 low-level details.
 
 Hang on - I am a Mac user, use emacs, know (and love!) the terminal,
 regularly edit file permissions and owners - maybe because in my heart I
 am a Linux person? :-)
 

I'm a Unix-user with a Mac too. But there is no need to use the terminal for 
this task.
Using the Finder there is the Command-i or RBM-Info and you get a panel to set 
the file permissions.

With Windows it's similar.

 
 Mac users addicted to Emacs must be a very rare breed indeed... :)
 
 I don't think so - I am surprised how many are there actually when you
 look in the mailing lists of emacs, org-mode or ess (Emacs Speaks
 Statistics). I see a Mac as a hybrid: on the one side, you have the GUI
 which works perfectly (in contrast to windows...) and *requires* not
 much tinkering to make it work nearly perfect, while on the other side
 you can use easily all the Linux software (see e.g. the homebrew project
 http://brew.sh for the terminal / console software or LyX ...) - under
 the hood, OSX is not much different then Linux. So I have the best from
 both worlds, and probably the best hardware in the world.
 
 
 
 Having a quick way to set this within LyX can be useful, and even
 within the same LyX session you can set/unset this status.
 
 I completely agree - an option to set a file read-only from within LyX
 would be quite useful. Even Emacs can do this - and emacs users are
 addicted to the terminal!
 
 I even think this should not be hidden in a menu, but in the open dialog
 and in the tab itself, so that one can easily set it when opening a file
 and change (and see the actual status!) without having to go into a menu.

I don't like the proposal to extend the open dialog. This is nearly impossible
with native dialogs and the Qt-specific dialogs look so strange.

Stephan

Re: Strategies for locating errors

[Wolfgang Engelmann]

Am 05.05.2015 um 15:18 schrieb Will Furnass:

On 05/05/15 13:27, Rainer M Krug wrote:

Will Furnass wrfurna...@sheffield.ac.uk writes:

could LyX be improved to make locating errors less manual
though? For example, if a mapping was generated at compile time
from LyX lines to TeX lines then buttons could be added to the
compilation pane to move the cursor between the lines referenced
in error messages.

I am by no means a LaTeX expert -0 so I might be wrong, but - the
LaTeX error messages are already quite cryptic, and the error you
quote (Missing } inserted' error for 'l.1052') means that the
missing } is inserted in this line - where it is actually
missing and what is causing this does not even LaTeX know - so
there is no chance that LyX will be able to tell you.

True, but the line number associated with a LaTeX error is a useful
clue when fault-finding and being able to quickly move the cursor to
the corresponding line in LyX could make fixing broken documents much
quicker in many situations.  The compilation pane could display a
caveat next to buttons for moving the cursor between error line
numbers saying something like 'the root cause of this error may not
lie at this location'.

Will

That was the reason I was asking a while ago, whether the latex source 
panel (under view) could show the tex line number. But I was told it is 
not possible under lyx.

Wolfgang

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 15:06, Wolfgang Engelmann wrote:
 That was the reason I was asking a while ago, whether the latex
 source panel (under view) could show the tex line number. But I was
 told it is not possible under lyx.

That would certainly be a step in the right direction.  Given that we
already have forward and backward search between LyX and a PDF viewer
using SyncTeX then something similar for LyX to/from TeX should be feasible.

Will

Set location of Source and Messages panes in Lyx UI

[Gilles Moyse]

Hi.

I have got a slight problem to set the location of the Source and Messages
panes in the Lyx UI (Debian, LyX Version 2.1.3). For some reason, my Lyx UI
has been reset, so the Source and Messages panes were not displayed. After
having them displayed again (View / Source Pane and View / Messages Pane),
I cannot find a way to display them side by side: they are either undocked
and hence on top of the main pane, or displayed as two tabs - I cannot have
them shown simultaneously side by side.

Am I missing something ?

Thanks,

Gilles

quick question

[Kolokytha, Selina]

Kindly advise if LYX works on Windows 8 as I do not see the relevant download 
option on your website.

Many thanks
Selina

Re: quick question

[John Kane]

Apparently yes.
http://wiki.lyx.org/Windows/Windows

On 5 May 2015 at 13:15, Kolokytha, Selina s.koloky...@ucl.ac.uk wrote:

  Kindly advise if LYX works on Windows 8 as I do not see the relevant
 download option on your website.



 Many thanks

 Selina








-- 
John Kane
Kingston ON Canada

Re: Strategies for locating errors

[Georg Baum]

Wolfgang Engelmann wrote:

 That was the reason I was asking a while ago, whether the latex source
 panel (under view) could show the tex line number. But I was told it is
 not possible under lyx.

Why that? Of course it would only be possible if the panel is set to show 
the full source (otherwise the line number would be wrong), but in that case 
it should not be a problem.



Georg

Re: Strategies for locating errors

[Georg Baum]

Will Furnass wrote:

 How do others locate compilation errors in large multi-file documents?
 
 I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
 relate that line number to the LyX source.  I then try exporting to tex
 using pdflatex into a temporary directory and search through all 16 tex
 files looking for errors on or near line 1052.

If you select the error item in the error dialog then the corresponding LyX 
contents should should be selected in the main area as well. This is not 
always 100% correct, but usually the error cause is nearby. Does this not 
work in your case?


Georg

Re: Strategies for locating errors

[Will Furnass]

On 5 May 2015 at 21:38, Georg Baum georg.b...@post.rwth-aachen.de wrote:


 If you select the error item in the error dialog then the corresponding LyX
 contents should should be selected in the main area as well. This is not
 always 100% correct, but usually the error cause is nearby. Does this not
 work in your case?


Ah, I hadn't noticed that before!  That works perfectly if the error is in
the master document but not if the error is in a child document (of which I
have quite a few).

If would be great if LyX would switch to/open the child document containing
the likely location of the error and move the cursor to that location.

Will

Re: Strategies for locating errors

[Gordon Cooper]

On 06/05/15 09:57, Will Furnass wrote:

That works perfectly if the error is in the master document but not if
the error is in a child document (of which I have quite a few).


I have been having similar problems with errors, mainly relating to 
producing printable pdf versions
of a Software User Manual that has fairly frequent updates and changes. 
This manual is a team effort
written with Lyx with an on-line HTML version being the primary release 
format. The HTML does not
show some Latex errors but they do appear when a pdf conversion is 
attempted, and my team task

is to deal with the pdfs.

Error reports give a line number, which has been difficult to translate 
into a location in the Lyx file.
However, I'm now experimenting with the Latex Editor, Texmaker.  It 
appears to happily present the
Lyx files, all with line numbers. Perhaps this will help my error 
finding, we can but see.


Gordon
Tauranga
New Zealand.

Re: "Disable editing" / "read only" menu option?

[Liviu Andronic]

On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak  wrote:
> On Mon, May 4, 2015 at 8:05 AM, Helge Hafting  wrote:
>>
>>
>> Den 23. mars 2015 17:57, skrev Scott Kostyshak:
>>>
>>> Dear LyX users,
>>>
>>> What are your thoughts on having an option in the menu called
>>> something like "Disable editing" or "Read only", which would make it
>>> so you could not edit the current document?
>>>
>> Have you tried making the file itself read-only? LyX already knows about
>> read-only files and will not allow editing then.
>
> Good point. I think the advantage of the feature being discussed at
> http://www.lyx.org/trac/ticket/6692
> is to give users a user-friendly way to do it inside of LyX.
>
Indeed. Setting a file read-only on the disk may work well enough for
Linux users, but Windows or Mac users can't be bothered with such
low-level details. Having a quick way to set this within LyX can be
useful, and even within the same LyX session you can set/unset this status.

Liviu



> Scott



-- 
Do you think you know what math is?
http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02
Or what it means to be intelligent?
http://www.ideasroadshow.com/issues/john-duncan-2013-08-30
Think again:
http://www.ideasroadshow.com/library

Re: "Disable editing" / "read only" menu option?

[Rainer M Krug]

Liviu Andronic  writes:

> On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak  wrote:
>> On Mon, May 4, 2015 at 8:05 AM, Helge Hafting  wrote:
>>>
>>>
>>> Den 23. mars 2015 17:57, skrev Scott Kostyshak:

 Dear LyX users,

 What are your thoughts on having an option in the menu called
 something like "Disable editing" or "Read only", which would make it
 so you could not edit the current document?

>>> Have you tried making the file itself read-only? LyX already knows about
>>> read-only files and will not allow editing then.
>>
>> Good point. I think the advantage of the feature being discussed at
>> http://www.lyx.org/trac/ticket/6692
>> is to give users a user-friendly way to do it inside of LyX.
>>

> Indeed. Setting a file read-only on the disk may work well enough for
> Linux users, but Windows or Mac users can't be bothered with such
> low-level details.

Hang on - I am a Mac user, use emacs, know (and love!) the terminal,
regularly edit file permissions and owners - maybe because in my heart I
am a Linux person? :-)

> Having a quick way to set this within LyX can be useful, and even
> within the same LyX session you can set/unset this status.

I completely agree - an option to set a file read-only from within LyX
would be quite useful. Even Emacs can do this - and emacs users are
addicted to the terminal!

I even think this should not be hidden in a menu, but in the open dialog
and in the tab itself, so that one can easily set it when opening a file
and change (and see the actual status!) without having to go into a menu.

It would be quite nice, if read-only buffers would have e.g. a red
border, independent of why they are read-only.

Cheers,

Rainer

>
> Liviu
>
>
>
>> Scott

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Strategies for locating errors

[Will Furnass]

How do others locate compilation errors in large multi-file documents?

I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
relate that line number to the LyX source.  I then try exporting to tex
using pdflatex into a temporary directory and search through all 16 tex
files looking for errors on or near line 1052.

An alternative approach would have been to comment the
'includes'/'inputs' for various chapters of my thesis then try to
recompile but this partitioning approach would be slow given that it
currently takes ~5mins to compile my thesis.

I'm sure I can find the cause of the error eventually; I was just
wondering if there were a neat way of identifying the location of
errors.  At present pretty much everything in LyX is a joy and very
slick apart from locating the source of errors.

FYI, yes I am using a little Evil Red Text (to use \resizebox within
table floats).

Cheers,

Will

Re: "Disable editing" / "read only" menu option?

[Liviu Andronic]

On Tue, May 5, 2015 at 10:40 AM, Rainer M Krug  wrote:
> Liviu Andronic  writes:
>
>> On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak  wrote:
>>> On Mon, May 4, 2015 at 8:05 AM, Helge Hafting  wrote:


 Den 23. mars 2015 17:57, skrev Scott Kostyshak:
>
> Dear LyX users,
>
> What are your thoughts on having an option in the menu called
> something like "Disable editing" or "Read only", which would make it
> so you could not edit the current document?
>
 Have you tried making the file itself read-only? LyX already knows about
 read-only files and will not allow editing then.
>>>
>>> Good point. I think the advantage of the feature being discussed at
>>> http://www.lyx.org/trac/ticket/6692
>>> is to give users a user-friendly way to do it inside of LyX.
>>>
>
>> Indeed. Setting a file read-only on the disk may work well enough for
>> Linux users, but Windows or Mac users can't be bothered with such
>> low-level details.
>
> Hang on - I am a Mac user, use emacs, know (and love!) the terminal,
> regularly edit file permissions and owners - maybe because in my heart I
> am a Linux person? :-)
>

Mac users addicted to Emacs must be a very rare breed indeed... :)


>> Having a quick way to set this within LyX can be useful, and even
>> within the same LyX session you can set/unset this status.
>
> I completely agree - an option to set a file read-only from within LyX
> would be quite useful. Even Emacs can do this - and emacs users are
> addicted to the terminal!
>
> I even think this should not be hidden in a menu, but in the open dialog
> and in the tab itself, so that one can easily set it when opening a file
> and change (and see the actual status!) without having to go into a menu.
>
> It would be quite nice, if read-only buffers would have e.g. a red
> border, independent of why they are read-only.
>
Or have the tab text colored green (as Geany does it), or have the
'(ro)' flag appended to the file name (just like we have * for
modified files).

Liviu


> Cheers,
>
> Rainer
>
>>
>> Liviu
>>
>>
>>
>>> Scott
>
> --
> Rainer M. Krug
> email: Rainerkrugsde
> PGP: 0x0F52F982



-- 
Do you think you know what math is?
http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02
Or what it means to be intelligent?
http://www.ideasroadshow.com/issues/john-duncan-2013-08-30
Think again:
http://www.ideasroadshow.com/library

Re: "Disable editing" / "read only" menu option?

[Rainer M Krug]

Liviu Andronic  writes:

> On Tue, May 5, 2015 at 10:40 AM, Rainer M Krug  wrote:
>> Liviu Andronic  writes:
>>
>>> On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak  wrote:
 On Mon, May 4, 2015 at 8:05 AM, Helge Hafting  
 wrote:
>
>
> Den 23. mars 2015 17:57, skrev Scott Kostyshak:
>>
>> Dear LyX users,
>>
>> What are your thoughts on having an option in the menu called
>> something like "Disable editing" or "Read only", which would make it
>> so you could not edit the current document?
>>
> Have you tried making the file itself read-only? LyX already knows about
> read-only files and will not allow editing then.

 Good point. I think the advantage of the feature being discussed at
 http://www.lyx.org/trac/ticket/6692
 is to give users a user-friendly way to do it inside of LyX.

>>
>>> Indeed. Setting a file read-only on the disk may work well enough for
>>> Linux users, but Windows or Mac users can't be bothered with such
>>> low-level details.
>>
>> Hang on - I am a Mac user, use emacs, know (and love!) the terminal,
>> regularly edit file permissions and owners - maybe because in my heart I
>> am a Linux person? :-)
>>
>
> Mac users addicted to Emacs must be a very rare breed indeed... :)

I don't think so - I am surprised how many are there actually when you
look in the mailing lists of emacs, org-mode or ess (Emacs Speaks
Statistics). I see a Mac as a hybrid: on the one side, you have the GUI
which works perfectly (in contrast to windows...) and *requires* not
much tinkering to make it work nearly perfect, while on the other side
you can use easily all the Linux software (see e.g. the homebrew project
http://brew.sh for the terminal / console software or LyX ...) - under
the hood, OSX is not much different then Linux. So I have the best from
both worlds, and probably the best hardware in the world.

>
>
>>> Having a quick way to set this within LyX can be useful, and even
>>> within the same LyX session you can set/unset this status.
>>
>> I completely agree - an option to set a file read-only from within LyX
>> would be quite useful. Even Emacs can do this - and emacs users are
>> addicted to the terminal!
>>
>> I even think this should not be hidden in a menu, but in the open dialog
>> and in the tab itself, so that one can easily set it when opening a file
>> and change (and see the actual status!) without having to go into a menu.
>>
>> It would be quite nice, if read-only buffers would have e.g. a red
>> border, independent of why they are read-only.
>>
> Or have the tab text colored green (as Geany does it), or have the
> '(ro)' flag appended to the file name (just like we have * for
> modified files).

Yup - just something very visible.

Rainer

>
> Liviu
>
>
>> Cheers,
>>
>> Rainer
>>
>>>
>>> Liviu
>>>
>>>
>>>
 Scott
>>
>> --
>> Rainer M. Krug
>> email: Rainerkrugsde
>> PGP: 0x0F52F982

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature

Wrong numbering of appendix

[Aline Gautrein]

Hey Lyx-friends,

I use Koma-script class book. I added an appendix to my dissertation and in
the Lyx-file it is correctly numbered with Appendix A. Figure A.1... etc.

My problem: In the pdf-file the "A" is missing in the headings and the
captions. Headings look like this:

.1.1 Blabla
.1.3 blabla

captions like this:

Figure .1:
Figure .2:

Do I have to insert something in the preamble, saying that letters are
allowed in heading- and caption numbers?

Which command do I need?

Thanks a lot!

Re: Strategies for locating errors

[Nikos Alexandris]

* Will Furnass  [2015-05-05 11:51:56 +0100]:

> How do others locate compilation errors in large multi-file documents?
> 
> I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
> relate that line number to the LyX source.  I then try exporting to tex
> using pdflatex into a temporary directory and search through all 16 tex
> files looking for errors on or near line 1052.
> 
> An alternative approach would have been to comment the
> 'includes'/'inputs' for various chapters of my thesis then try to
> recompile but this partitioning approach would be slow given that it
> currently takes ~5mins to compile my thesis.
> 
> I'm sure I can find the cause of the error eventually; I was just
> wondering if there were a neat way of identifying the location of
> errors.  At present pretty much everything in LyX is a joy and very
> slick apart from locating the source of errors.
> 
> FYI, yes I am using a little Evil Red Text (to use \resizebox within
> table floats).

Something like "binary search": split in two halfs, try to find out
which half does not compile. Then, again, repeat the same: split in
half, identify the erroneous part. Sooner or later you'll nail the
source of the error.

Cheers, Nikos

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 12:47, Nikos Alexandris wrote:
> * Will Furnass  [2015-05-05 11:51:56 +0100]:
> 
>> How do others locate compilation errors in large multi-file documents?
>>

> 
> Something like "binary search": split in two halfs, try to find out
> which half does not compile. Then, again, repeat the same: split in
> half, identify the erroneous part. Sooner or later you'll nail the
> source of the error.

A good idea, but could LyX be improved to make locating errors less
manual though?  For example, if a mapping was generated at compile time
from LyX lines to TeX lines then buttons could be added to the
compilation pane to move the cursor between the lines referenced in
error messages.

Will

Re: Strategies for locating errors

[Rainer M Krug]

Will Furnass  writes:

> On 05/05/15 12:47, Nikos Alexandris wrote:
>> * Will Furnass  [2015-05-05 11:51:56 +0100]:
>> 
>>> How do others locate compilation errors in large multi-file documents?
>>>
> 
>> 
>> Something like "binary search": split in two halfs, try to find out
>> which half does not compile. Then, again, repeat the same: split in
>> half, identify the erroneous part. Sooner or later you'll nail the
>> source of the error.
>
> A good idea, but could LyX be improved to make locating errors less
> manual though?  For example, if a mapping was generated at compile time
> from LyX lines to TeX lines then buttons could be added to the
> compilation pane to move the cursor between the lines referenced in
> error messages.

I am by no means a LaTeX expert -0 so I might be wrong, but - the LaTeX
error messages are already quite cryptic, and the error you quote
(Missing } inserted' error for 'l.1052') means that the missing "}" is
inserted in this line - where it is actually missing and what is causing
this does not even LaTeX know - so there is no chance that LyX will be
able to tell you.

Rainer

>
> Will
>
>
>
>
>
>

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: Wrong numbering of appendix

[Aline Gautrein]

Hey!

I solved the problem: You must not put an \backmatter in front of the
appendix.


Greetings!

2015-05-05 13:34 GMT+02:00 Aline Gautrein :

> Hey Lyx-friends,
>
> I use Koma-script class book. I added an appendix to my dissertation and
> in the Lyx-file it is correctly numbered with Appendix A. Figure A.1... etc.
>
> My problem: In the pdf-file the "A" is missing in the headings and the
> captions. Headings look like this:
>
> .1.1 Blabla
> .1.3 blabla
>
> captions like this:
>
> Figure .1:
> Figure .2:
>
> Do I have to insert something in the preamble, saying that letters are
> allowed in heading- and caption numbers?
>
> Which command do I need?
>
> Thanks a lot!
>

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 13:27, Rainer M Krug wrote:
> Will Furnass  writes:
>> 
>> could LyX be improved to make locating errors less manual
>> though? For example, if a mapping was generated at compile time
>> from LyX lines to TeX lines then buttons could be added to the
>> compilation pane to move the cursor between the lines referenced
>> in error messages.
> 
> I am by no means a LaTeX expert -0 so I might be wrong, but - the 
> LaTeX error messages are already quite cryptic, and the error you 
> quote (Missing } inserted' error for 'l.1052') means that the 
> missing "}" is inserted in this line - where it is actually
> missing and what is causing this does not even LaTeX know - so
> there is no chance that LyX will be able to tell you.

True, but the line number associated with a LaTeX error is a useful
clue when fault-finding and being able to quickly move the cursor to
the corresponding line in LyX could make fixing broken documents much
quicker in many situations.  The compilation pane could display a
caveat next to buttons for moving the cursor between error line
numbers saying something like 'the root cause of this error may not
lie at this location'.

Will

Re: "Disable editing" / "read only" menu option?

[Stephan Witt]

Am 05.05.2015 um 13:21 schrieb Rainer M Krug :

> Liviu Andronic  writes:
> 
>> On Tue, May 5, 2015 at 10:40 AM, Rainer M Krug  wrote:
>>> Liviu Andronic  writes:
>>> 
 On Tue, May 5, 2015 at 6:44 AM, Scott Kostyshak  wrote:
> On Mon, May 4, 2015 at 8:05 AM, Helge Hafting  
> wrote:
>> 
>> 
>> Den 23. mars 2015 17:57, skrev Scott Kostyshak:
>>> 
>>> Dear LyX users,
>>> 
>>> What are your thoughts on having an option in the menu called
>>> something like "Disable editing" or "Read only", which would make it
>>> so you could not edit the current document?
>>> 
>> Have you tried making the file itself read-only? LyX already knows about
>> read-only files and will not allow editing then.
> 
> Good point. I think the advantage of the feature being discussed at
> http://www.lyx.org/trac/ticket/6692
> is to give users a user-friendly way to do it inside of LyX.
> 
>>> 
 Indeed. Setting a file read-only on the disk may work well enough for
 Linux users, but Windows or Mac users can't be bothered with such
 low-level details.
>>> 
>>> Hang on - I am a Mac user, use emacs, know (and love!) the terminal,
>>> regularly edit file permissions and owners - maybe because in my heart I
>>> am a Linux person? :-)
>>> 

I'm a Unix-user with a Mac too. But there is no need to use the terminal for 
this task.
Using the Finder there is the Command-i or RBM-Info and you get a panel to set 
the file permissions.

With Windows it's similar.

>> 
>> Mac users addicted to Emacs must be a very rare breed indeed... :)
> 
> I don't think so - I am surprised how many are there actually when you
> look in the mailing lists of emacs, org-mode or ess (Emacs Speaks
> Statistics). I see a Mac as a hybrid: on the one side, you have the GUI
> which works perfectly (in contrast to windows...) and *requires* not
> much tinkering to make it work nearly perfect, while on the other side
> you can use easily all the Linux software (see e.g. the homebrew project
> http://brew.sh for the terminal / console software or LyX ...) - under
> the hood, OSX is not much different then Linux. So I have the best from
> both worlds, and probably the best hardware in the world.
> 
>> 
>> 
 Having a quick way to set this within LyX can be useful, and even
 within the same LyX session you can set/unset this status.
>>> 
>>> I completely agree - an option to set a file read-only from within LyX
>>> would be quite useful. Even Emacs can do this - and emacs users are
>>> addicted to the terminal!
>>> 
>>> I even think this should not be hidden in a menu, but in the open dialog
>>> and in the tab itself, so that one can easily set it when opening a file
>>> and change (and see the actual status!) without having to go into a menu.

I don't like the proposal to extend the open dialog. This is nearly impossible
with native dialogs and the Qt-specific dialogs look so strange.

Stephan

Re: Strategies for locating errors

[Wolfgang Engelmann]

Am 05.05.2015 um 15:18 schrieb Will Furnass:

On 05/05/15 13:27, Rainer M Krug wrote:

Will Furnass  writes:

could LyX be improved to make locating errors less manual
though? For example, if a mapping was generated at compile time
from LyX lines to TeX lines then buttons could be added to the
compilation pane to move the cursor between the lines referenced
in error messages.

I am by no means a LaTeX expert -0 so I might be wrong, but - the
LaTeX error messages are already quite cryptic, and the error you
quote (Missing } inserted' error for 'l.1052') means that the
missing "}" is inserted in this line - where it is actually
missing and what is causing this does not even LaTeX know - so
there is no chance that LyX will be able to tell you.

True, but the line number associated with a LaTeX error is a useful
clue when fault-finding and being able to quickly move the cursor to
the corresponding line in LyX could make fixing broken documents much
quicker in many situations.  The compilation pane could display a
caveat next to buttons for moving the cursor between error line
numbers saying something like 'the root cause of this error may not
lie at this location'.

Will

That was the reason I was asking a while ago, whether the latex source 
panel (under >view) could show the tex line number. But I was told it is 
not possible under lyx.

Wolfgang

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 15:06, Wolfgang Engelmann wrote:
> That was the reason I was asking a while ago, whether the latex
> source panel (under >view) could show the tex line number. But I was
> told it is not possible under lyx.

That would certainly be a step in the right direction.  Given that we
already have forward and backward search between LyX and a PDF viewer
using SyncTeX then something similar for LyX to/from TeX should be feasible.

Will

Set location of Source and Messages panes in Lyx UI

[Gilles Moyse]

Hi.

I have got a slight problem to set the location of the Source and Messages
panes in the Lyx UI (Debian, LyX Version 2.1.3). For some reason, my Lyx UI
has been reset, so the Source and Messages panes were not displayed. After
having them displayed again (View / Source Pane and View / Messages Pane),
I cannot find a way to display them side by side: they are either undocked
and hence on top of the main pane, or displayed as two tabs - I cannot have
them shown simultaneously side by side.

Am I missing something ?

Thanks,

Gilles

quick question

[Kolokytha, Selina]

Kindly advise if LYX works on Windows 8 as I do not see the relevant download 
option on your website.

Many thanks
Selina

Re: quick question

[John Kane]

Apparently yes.
http://wiki.lyx.org/Windows/Windows

On 5 May 2015 at 13:15, Kolokytha, Selina  wrote:

>  Kindly advise if LYX works on Windows 8 as I do not see the relevant
> download option on your website.
>
>
>
> Many thanks
>
> Selina
>
>
>
>
>



-- 
John Kane
Kingston ON Canada

Re: Strategies for locating errors

[Georg Baum]

Wolfgang Engelmann wrote:

> That was the reason I was asking a while ago, whether the latex source
> panel (under >view) could show the tex line number. But I was told it is
> not possible under lyx.

Why that? Of course it would only be possible if the panel is set to show 
the full source (otherwise the line number would be wrong), but in that case 
it should not be a problem.



Georg

Re: Strategies for locating errors

[Georg Baum]

Will Furnass wrote:

> How do others locate compilation errors in large multi-file documents?
> 
> I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
> relate that line number to the LyX source.  I then try exporting to tex
> using pdflatex into a temporary directory and search through all 16 tex
> files looking for errors on or near line 1052.

If you select the error item in the error dialog then the corresponding LyX 
contents should should be selected in the main area as well. This is not 
always 100% correct, but usually the error cause is nearby. Does this not 
work in your case?


Georg

Re: Strategies for locating errors

[Will Furnass]

On 5 May 2015 at 21:38, Georg Baum  wrote:

>
> If you select the error item in the error dialog then the corresponding LyX
> contents should should be selected in the main area as well. This is not
> always 100% correct, but usually the error cause is nearby. Does this not
> work in your case?
>

Ah, I hadn't noticed that before!  That works perfectly if the error is in
the master document but not if the error is in a child document (of which I
have quite a few).

If would be great if LyX would switch to/open the child document containing
the likely location of the error and move the cursor to that location.

Will

Re: Strategies for locating errors

[Gordon Cooper]

On 06/05/15 09:57, Will Furnass wrote:

That works perfectly if the error is in the master document but not if
the error is in a child document (of which I have quite a few).


I have been having similar problems with errors, mainly relating to 
producing printable pdf versions
of a Software User Manual that has fairly frequent updates and changes. 
This manual is a team effort
written with Lyx with an on-line HTML version being the primary release 
format. The HTML does not
show some Latex errors but they do appear when a pdf conversion is 
attempted, and my team task

is to deal with the pdfs.

Error reports give a line number, which has been difficult to translate 
into a location in the Lyx file.
However, I'm now experimenting with the Latex Editor, Texmaker.  It 
appears to happily present the
Lyx files, all with line numbers. Perhaps this will help my error 
finding, we can but see.


Gordon
Tauranga
New Zealand.