Cursor position when view is split

[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 split the view 
into left and right halves. I like to work in the right pane (a relic of 
#9085 in the days of LyX 2.0) but the cursor is always at the start of 
the document rather than the position saved from the last time I worked 
on the document.


Andrew


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Re: 2.3.x compilation error with -Werror

[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

[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 name
+-
 Reporter:  maltenfort              |      Owner:  lasgouttes
    Type:  defect                  |      Status:  new
 Priority:  low                    |  Milestone:
Component:  general                |    Version:  2.1.2
 Severity:  minor                  |  Resolution:
 Keywords:  os=windows, infoneeded  |
+-

Comment (by forenr):

 I think it is now clear that the problem is due to the pdfview wrapper. I
 see two possible choices: either fix pdfview or commit the patch in
 comment:4. However, in this last case, someone has to test it, because I
 am not confident in testing it due to my mixed environment.

-- 
Ticket URL: 
The LyX Project 
LyX -- The Document Processor
  

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

[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 that biber is always called, even when no bibliography
> inset 
> is inserted.  For the first document of this session the complete
> biber 
> call took about 50 seconds (attached -- I was testing for bug #9368
> on 
> apostrophes in filenames ). For subsequent documents it was a few 
> seconds, but still a noticeable delay. Should biber be called when
> there 
> is no bibliography inset inserted?

As opposed to BibTeX, biblatex doesn't necessarily need a bibliography
inset (it can output citations without having to output a bibliography,
if you use \addbibresource in the preamble or the class file).
Currently, we run biber whenever a *.bcf file exists in the tmp dir.
This is apparently also the case if there are no citations.

So: yes, biber should not only be called  when there is a bibliography
inset. But still we call it in cases where we shouldn't. I have not
idea for a more fine-grained solution ATM.

Jürgen




signature.asc
Description: This is a digitally signed message part

Re: 2.3.x compilation error with -Werror

[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]
>   if
> (buffer().masterParams().documentClass().hasLaTeXLayout("chapter"))
>   ^~
> /home/scott/lyxbuilds/2.3.x/repo/src/insets/InsetBibtex.cpp:885:3:
> note: ...this statement, but the latter is misleadingly indented as
> if it were guarded by the ‘if’
>return buffer().B_("References");
>^~

Thanks, fixed.

Jürgen

> 
> Scott


signature.asc
Description: This is a digitally signed message part