Cursor position when view is split

2018-10-08 Thread Andrew Parsloe
When the view is split into left and right windows, the cursor is placed at the *start* of the document in the right window. I wonder if this is the best place? Shouldn't it initially be placed at the same position as in the left pane? My pattern of work is to start LyX, open a document and

Re: 2.3.x compilation error with -Werror

2018-10-08 Thread Scott Kostyshak
On Mon, Oct 08, 2018 at 11:33:19AM +0200, Jürgen Spitzmüller wrote: > Thanks, fixed. Compiles now without error. Thanks. Scott signature.asc Description: PGP signature

Re: #9368: Apostrophe a problem in file name

2018-10-08 Thread Michael Maltenfort
I can confirm that the problem still exists on a Windows 7 machine with LyX 2.3.1-1 and Adobe Acrobat Pro DC Continuous Release | Version 2019.008.20071 ---Michael Maltenfort On Saturday, October 6, 2018, 5:58:51 AM CDT, LyX Ticket Tracker wrote: #9368: Apostrophe a problem in file

Re: Should biber be called when there is no bib inset?

2018-10-08 Thread Jürgen Spitzmüller
Am Freitag, den 05.10.2018, 18:34 +1300 schrieb Andrew Parsloe: > My document defaults are set up so that under Document > Settings > > Bibliography, Biblatex is set. I was puzzled by the length of time > compilation of even the simplest document took. Looking at the > message > pane, I see

Re: 2.3.x compilation error with -Werror

2018-10-08 Thread Jürgen Spitzmüller
Am Montag, den 08.10.2018, 01:07 -0400 schrieb Scott Kostyshak: > I get the following on current 2.3.x (e94ea46b) when compiling with > -Werror: > > /home/scott/lyxbuilds/2.3.x/repo/src/insets/InsetBibtex.cpp:883:2: > error: this ‘if’ clause does not guard... [-Werror=misleading- > indentation] >

Re: [LyX/2.3.x] Skip paint event when in the middle of a buffer operation

2018-10-08 Thread Stephan Witt
Am 07.10.2018 um 13:46 schrieb Jean-Marc Lasgouttes : > > Le 04/10/2018 à 15:22, Jean-Marc Lasgouttes a écrit : >> Actually, as can be seen in >> https://www.lyx.org/trac/ticket/11323 >> there is a case for rushing out 2.3.2 with a fix for this. I therefore >> backported for 2.3.2 so that it