Re: Latex Error.

2017-01-13 Thread Richard Heck
On 01/14/2017 12:11 AM, Scott Kostyshak wrote:
> On Sat, Jan 14, 2017 at 05:56:21PM +1300, gordon cooper wrote:
>> Happy New Year to All.
>>
>> This has been solved (after some detective work) but am reporting
>> it, just in case it happens to others.
>>
>> Had a recent mysterious error when trying an Lyx to pdf conversion.
>> The program reported a Latex error but gave no error report.
>>
>> The same Lyx file converted to html immediately, no errors. I had
>> a coding error, ignored by one converter. A look at the source code
>> was not a success.
>>
>> So,  used the traditional system of halving the file, testing halving again,
>> until there only a single line of code left. There was the problem, a
>> Hyperlink
>> with a irreconcilable character, a beginning  itemize dot, like this :
>>
>>
>> • http://www.debian.org/doc/FAQ/ch-pkgtools.en.html
>>
>> Removing the dot fixed the problem, but an hour or two wasted looking
>> for it.
>>
>> Gordon.
>>
> Happy New Year, Gordon!
>
> Thanks for reporting this problem. Next time it would be helpful if you
> sent an example file. I went ahead and created an example file and I can
> reproduce the same problem you saw. The example file is attached. If you
> open LyX in the terminal, you see the following message when compiling:
>
>   Error 84 returned from iconv when converting from UCS-4LE to
>   ISO-8859-15: Invalid or incomplete multibyte or wide character
>
> It does not give a clue where the error comes from, and indeed the LyX
> GUI is not helpful at all in indicating where the error might be.
>
> I'm moving this thread to the lyx-devel list now. I think you wanted to
> just give lyx-users a warning in case they come across the problem, and
> I think potential discussion of how to improve LyX to handle this case
> should proceed on lyx-devel.

This kind of error does seem to crop up quite a bit. It'd be nice if we
could say something more informative. Could we at least say what the
character was? Or report its location in the file?

Richard



Re: Latex Error.

2017-01-13 Thread Scott Kostyshak
On Sat, Jan 14, 2017 at 05:56:21PM +1300, gordon cooper wrote:
> Happy New Year to All.
> 
> This has been solved (after some detective work) but am reporting
> it, just in case it happens to others.
> 
> Had a recent mysterious error when trying an Lyx to pdf conversion.
> The program reported a Latex error but gave no error report.
> 
> The same Lyx file converted to html immediately, no errors. I had
> a coding error, ignored by one converter. A look at the source code
> was not a success.
> 
> So,  used the traditional system of halving the file, testing halving again,
> until there only a single line of code left. There was the problem, a
> Hyperlink
> with a irreconcilable character, a beginning  itemize dot, like this :
> 
> 
> • http://www.debian.org/doc/FAQ/ch-pkgtools.en.html
> 
> Removing the dot fixed the problem, but an hour or two wasted looking
> for it.
> 
> Gordon.
> 

Happy New Year, Gordon!

Thanks for reporting this problem. Next time it would be helpful if you
sent an example file. I went ahead and created an example file and I can
reproduce the same problem you saw. The example file is attached. If you
open LyX in the terminal, you see the following message when compiling:

  Error 84 returned from iconv when converting from UCS-4LE to
  ISO-8859-15: Invalid or incomplete multibyte or wide character

It does not give a clue where the error comes from, and indeed the LyX
GUI is not helpful at all in indicating where the error might be.

I'm moving this thread to the lyx-devel list now. I think you wanted to
just give lyx-users a warning in case they come across the problem, and
I think potential discussion of how to improve LyX to handle this case
should proceed on lyx-devel.

Scott
#LyX 2.3 created this file. For more info see http://www.lyx.org/
\lyxformat 508
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass article
\use_default_options true
\maintain_unincluded_children false
\language english
\language_package default
\inputencoding auto
\fontencoding global
\font_roman "default" "default"
\font_sans "default" "default"
\font_typewriter "default" "default"
\font_math "auto" "auto"
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100 100
\font_tt_scale 100 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 1
\use_package cancel 1
\use_package esint 1
\use_package mathdots 1
\use_package mathtools 1
\use_package mhchem 1
\use_package stackrel 1
\use_package stmaryrd 1
\use_package undertilde 1
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 1
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header

\begin_body

\begin_layout Standard
\begin_inset CommandInset href
LatexCommand href
target "• http://www.debian.org/doc/FAQ/ch-pkgtools.en.html;

\end_inset

hello
\end_layout

\end_body
\end_document


signature.asc
Description: PGP signature


Re: Biblatex

2017-01-13 Thread Pavel Sanda
Jürgen Spitzmüller wrote:
> I have put most energy into a design that enables portability between
> the diverse citation engines as much as possible, so it should be very
> easy to switch an existing document from, say, natbib to biblatex and
> (to a limited degree, since the feature set is larger) back.

This is exciting, Juergen!
Pavel


Re: [LyX/master] configure.py: Make 'notepad' last in text editor list

2017-01-13 Thread Pavel Sanda
Paul A. Rubin wrote:
> I don't know why Linux distributions store MIME associations in so many 
> different places, but in any event we apparently can't count on xdg-mime to 
> find the correct associations, and there is no painless way for a user to 
> fix that (at least none that I can find). My laptop has a MIME type editor, 

:) Welcome. I believe the (currently) correct way is to push your distro
to fix MIME config and if xdg works fine on top of that then push
the distro maintainer of lyx to patch lyx with xdg-open in configure.py.
This used to be the case with debian, where mime machinery seemed to work (tm).

Fundamentally you are having much deeper request - to unify how mime and
associations are handled across the desktop managers and distributions.

I will be happy to be proved wrong (haven't actually re-checked that for years)
but all this file extension association business was heterogenous across
different desktop managers and linux distributions as well. 
If that still applies then your original request is very hard to get right,
because after you spend weeks of research of the problems and possible
approaches you end up with code which will do something very similar to
xdg-utils. 

Pavel


Re: [LyX/master] configure.py: Make 'notepad' last in text editor list

2017-01-13 Thread Pavel Sanda
Guenter Milde wrote:
> A more general question to all developers:
> 
> When checking for default viewer/editor applications during (re)configure,
> should LyX
>   
> a) prefer feature rich applications, or
> b) prefer small and fast-starting applications.

As I don't see any obvious choice I would prefer
c) don't mess with the order unless something really buggy starts appearing
   (not so much because I believe the current order is right, but rather
   not to disturb people who are used to the current situation).

Pavel


EmDash Problems

2017-01-13 Thread Richard Heck
The attached files illustrate a problem that I raised, and was told not
to worry about, when "---" was exchanged for \textemdash. The problem is
that the latter does not break the way the former does. What can we do
about this. It's very annoying. (Note that this file is format 530 from
latest master.)


Richard




emdash.lyx
Description: application/lyx


emdash.pdf
Description: Adobe PDF document


Re: [LyX/master] configure.py: Make 'notepad' last in text editor list

2017-01-13 Thread Paul A. Rubin

On 01/13/2017 09:19 AM, Guenter Milde wrote:

IMV, using xdg-mime query seems the right way but not easy.
Maybe you can open an enhancement ticket.


tl;dr

I'm now having second thoughts about it. I discovered xdg-mime returns 
incorrect information on my laptop (including naming applications that 
are no longer installed). As noted here 
, the problem seems 
to be that xdg-utils programs focus on 
~/.local/share/applications/mimeapps.list and ignore 
~/.config/mimeapps.list (which I think is supposed to take precedence).


I don't know why Linux distributions store MIME associations in so many 
different places, but in any event we apparently can't count on xdg-mime 
to find the correct associations, and there is no painless way for a 
user to fix that (at least none that I can find). My laptop has a MIME 
type editor, but it shows the correct associations (presumably meaning 
those in ~/.config) and has no provision for tracking down and deleting 
associations in other obscure locations.


There's an alternative to xdg-open, namely gvfs-open, that seems to do a 
better job of reading the correct MIME association list. Unfortunately, 
where xdg-open defaults to Firefox (or whatever the default browser is?) 
on an unrecognized file type, gvfs-open on my PC tried to open a binary 
file (proprietary format, no MIME association) with Libre Office, which 
expectedly did not go well. So I'm hesitant to suggest setting gvfs-open 
as the default for unknown MIME types.


A possibility is to have the script run 'gvfs-mime --query ' 
and extract the default program from the first line of the return value 
(or ascertain that no default is set). Given the way xdg-mime blew up in 
my face, though, I'd like to hear from others before making a formal 
recommendation. In particular, since both my systems run Linux Mint, I 
have no idea how ubiquitous gvfs-mime is in other distributions.


Paul


Re: [LyX/master] Add an "Automatic" bibliography processor pref option

2017-01-13 Thread Richard Heck

Format change?


On 01/13/2017 01:21 PM, Juergen Spitzmueller wrote:
> commit 1eb43536da25a9617e3d471b3e24d0c4a239c21b
> Author: Juergen Spitzmueller 
> Date:   Fri Jan 13 19:18:35 2017 +0100
>
> Add an "Automatic" bibliography processor pref option
> 
> This is now set as default. It selects biber for Biblatex (with
> fall-back to first bibtex8, then bibtex, if the former is not
> installed), and bibtex for BibTeX-based engines.
> 
> With this, users do not normally need to care for the processor when
> they switch cite engines.
> ---
>  lib/doc/UserGuide.lyx  |   75 
> +---
>  src/BufferParams.cpp   |   16 +++-
>  src/BufferParams.h |2 +-
>  src/LyXRC.cpp  |2 +-
>  src/frontends/qt4/GuiPrefs.cpp |1 +
>  5 files changed, 79 insertions(+), 17 deletions(-)
>
> diff --git a/lib/doc/UserGuide.lyx b/lib/doc/UserGuide.lyx
> index 0a4d137..9774567 100644
> --- a/lib/doc/UserGuide.lyx
> +++ b/lib/doc/UserGuide.lyx
> @@ -1,5 +1,5 @@
>  #LyX 2.3 created this file. For more info see http://www.lyx.org/
> -\lyxformat 528
> +\lyxformat 530
>  \begin_document
>  \begin_header
>  \save_transient_properties true
> @@ -29322,7 +29322,7 @@ bibtex8 allows all characters that are possible to 
> encode in an 8-bit encoding
>  bibtex
>  \family default
>  , works with all bibliography packages
> -\change_inserted -712698321 1483887200
> +\change_inserted -712698321 1484330876
>  , although more complex 
>  \family sans
>  Biblatex
> @@ -29336,16 +29336,57 @@ Biblatex
>  
>  \begin_layout Standard
>  
> -\change_inserted -712698321 1483887384
> -In addition to these, you can set a specific processor for Japanese documents
> - in 
> +\change_inserted -712698321 1484331301
> +By default (with 
> +\begin_inset Quotes eld
> +\end_inset
> +
> +Default
> +\begin_inset Quotes erd
> +\end_inset
> +
> + bibliography processor set in 
> +\family sans
> +Document\SpecialChar menuseparator
> +Settings\SpecialChar menuseparator
> +Bibliography
> +\family default
> + and 
> +\begin_inset Quotes eld
> +\end_inset
> +
> +Automatic
> +\begin_inset Quotes erd
> +\end_inset
> +
> + bibliography processor in 
>  \family sans
>  Tools\SpecialChar menuseparator
>  Preferences\SpecialChar menuseparator
>  Output\SpecialChar menuseparator
>  LaTeX
>  \family default
> -.
> +), \SpecialChar LyX
> + selects the most appropriate (available) processor for the current bibliogra
> +phy approach (
> +\family sans
> +biber
> +\family default
> + for Biblatex, 
> +\family sans
> +bibtex
> +\family default
> + for Bib\SpecialChar TeX
> +-based bibliography styles).
> + This should suit most needs.
> +\change_unchanged
> +
> +\end_layout
> +
> +\begin_layout Standard
> +
> +\change_inserted -712698321 1484331395
> +In Japanese documents, a specific processor is used.
>   By default, this is 
>  \family sans
>  pbibtex
> @@ -29355,11 +29396,14 @@ pbibtex
>  bibtex
>  \family default
>   variant specifically aimed at Japanese.
> - It is automatically used, instead of 
> + You can adjust it in 
>  \family sans
> -bibtex
> +Tools\SpecialChar menuseparator
> +Preferences\SpecialChar menuseparator
> +Output\SpecialChar menuseparator
> +LaTeX
>  \family default
> -, in Japanese documents.
> +.
>  \change_unchanged
>  
>  \end_layout
> @@ -29369,11 +29413,16 @@ bibtex
>  \change_deleted -712698321 1483886683
>  Bib\SpecialChar TeX
>  
> -\change_inserted -712698321 1483887395
> -The selected processor
> +\change_inserted -712698321 1484331419
> +Selected bibliography processors
>  \change_unchanged
> - can be controlled with options that you can add below the specification
> - of the variants.
> + can be controlled with options that you can add below the 
> +\change_deleted -712698321 1484331437
> +specification of the variants
> +\change_inserted -712698321 1484331439
> +selection
> +\change_unchanged
> +.
>   Before adding options, it is strongly recommended that you read the manual
>   
>  \change_inserted -712698321 1483886810
> diff --git a/src/BufferParams.cpp b/src/BufferParams.cpp
> index f6e7f50..46baa3b 100644
> --- a/src/BufferParams.cpp
> +++ b/src/BufferParams.cpp
> @@ -3355,14 +3355,26 @@ vector BufferParams::citeStyles() const
>  }
>  
>  
> -string const & BufferParams::bibtexCommand() const
> +string const BufferParams::bibtexCommand() const
>  {
> + // Return document-specific setting if available
>   if (bibtex_command != "default")
>   return bibtex_command;
> + // For Japanese, return the specific program
>   else if (encoding().package() == Encoding::japanese)
>   return lyxrc.jbibtex_command;
> - else
> + // Else return the processor set in prefs
> + else if (lyxrc.bibtex_command != "automatic")
>   return lyxrc.bibtex_command;
> + // Automatic means: find the most suitable for the current cite 
> framework
> + if (useBiblatex()) {
> 

Re: [LyX/2.2.x] Assure long tooltip is correctly formatted.

2017-01-13 Thread Guillaume Munch

Le 13/01/2017 à 11:32, Jürgen Spitzmüller a écrit :

Am Freitag, den 13.01.2017, 11:11 +0100 schrieb Guillaume Munch:

(Independently,
I will try to see why this was not called automatically in master.)


OK. Maybe because this is a sub-dialog?



Weird, it displays fine here at 119dfcb1. Are there precise steps that I
must follow to reproduce the bug?

Guillaume



Re: biblatex (features/biblatex2) branch and master/child

2017-01-13 Thread PhilipPirrip
On Fri, 13 Jan 2017 18:47:12 +0100, Jürgen Spitzmüller wrote:

> Right. As I wrote you: please update to the most recent version (which
> is in master meanwhile, not features/biblatex2!).
> 
> Please report back if this issue still persists.

This is what I understand you did: even if the child does not use biblatex 
and its code contains bibtex commands \bibliographystyle and 
\bibliography those won't be used when compiling the master document. All 
good.


I'm reporting that the master document won't compile with a child 
document containing some commands specific to natbib.
In the attached examples, it will be because of a citation command in 
childOne.lyx. 
Can this be translated on the fly? 

Thanks a lot for working on biblatex support, Juergen!



Re: biblatex (features/biblatex2) branch and master/child - "childOne.lyx" yEnc

2017-01-13 Thread PhilipPirrip
=ybegin line=128 size=1856 name=childOne.lyx
Mv��J\X]J���JJXJp��JJJ���JdYY���X���X���Y4��J_]Z4���4�4�
�J4���J���4��J���4J4���J��X���4�
J�4�J���4�J���4��J4�J��4���JL���LJL���L4
��JL���LJL���L4JL���LJL���L4��JLLJLL4J���4��
J�4J�4�J�4��J[ZZJ[ZZ4��J[ZZJ[ZZ4��J�4�J�
��4��J���4JZ4���J���4��J���4��J���4J
��4�J�4��J���4�J�4J���J[4J���J[4J���
���J[4J�J[4JJ[4J�J[4J��J[4JJ[4��
��JJ[4J��J[4J��4�J��4�J4
��J��4���J��4�J�4J�4�J4�
�J�4��J4�J[4��Js4�J���4��JMZZbZZZ4��4J]4�J]4
�J��4��J���4�J���4���JZ4�J[4���J[4��
�J���4�J�4���J�4�JZ4�JZ4���J
�4���44���44�J}���4J��J�Jy��J4Jm��sJ4vm��J�4���J
L�d��d�L44��444���44�4�4
=yend size=1856 crc32=515fab52




Re: biblatex (features/biblatex2) branch and master/child - "childTwo.lyx" yEnc

2017-01-13 Thread PhilipPirrip
=ybegin line=128 size=1919 name=childTwo.lyx
Mv��J\X]J���JJXJp��JJJ���JdYY���X���X���Y4��J_]Z4���4�4�
�J4���J���4��J���4J4���J��X���4�
J�4�J���4�J���4��J4�J��4���JL���LJL���L4
��JL���LJL���L4JL���LJL���L4��JLLJLL4J���4��
J�4J�4�J�4��J[ZZJ[ZZ4��J[ZZJ[ZZ4��J�4�J�
��4��J���4JZ4���J���4��J���4��J���4J
��4�J�4��J���4�J�4J���J[4J���J[4J���
���J[4J�J[4JJ[4J�J[4J��J[4JJ[4��
��JJ[4J��J[4J��4�J��4�J4
��J��4���J��4�J�4J�4�J4�
�J�4��J4�J[4��Js4�J���4��JMZZbZZZ4��4J]4�J]4
�J��4��J���4�J���4���JZ4�J[4���J[4��
�J���4�J�4���J�4�JZ4�JZ4���J
�4���44���44�J}���4J��J�J~��J4���44�J}���4Jm��s�
���J��4vm��J��4JLWL4���JL�L44��444���44�4�4
=yend size=1919 crc32=f5cb8f05




Re: biblatex (features/biblatex2) branch and master/child - "master.lyx" yEnc

2017-01-13 Thread PhilipPirrip
=ybegin line=128 size=2094 name=master.lyx
Mv��J\X]J���JJXJp��JJJ���JdYY���X���X���Y4��J_]Z4���4�4�
�J4���J���4��J���4J4�J�4�J��
�4�J���4��J4�J��4���JL���LJL���L4��JL���LJL�
��L4JL���LJL���L4��JLLJLL4J���4��J�4
J�4�J�4��J[ZZJ[ZZ4��J[ZZJ[ZZ4��J�4�J���4
��J���4JZ4���J���4��J���4��J���4J��4
�J�4��J���4�J�4J���J[4J���J[4J��J[4J
�J[4JJ[4J�J[4J��J[4JJ[4JJ[4�
���J��J[4J4�J��4�J�4���JJ4��
J��4���J��4�J�4J�4�J4��J
�4��J4�J[4��Js4�J���4��JMZZbZZZ4��4J]4�J]4��
���J��4��J���4�J���4���JZ4�J[4���J[4
���J���4�J�4���J�4�JZ4�JZ4���J�4
���44���44�J}���4J��J��J4Jm��sJ4vm��J�4���JL
VY�V���L44��444���44�J}���4Jm��sJ���4vm��J��
�4JL�y��X���L44��444Jm��sJ���4vm��J���4JL�~��X���L44
��444���44�4�4
=yend size=2094 crc32=395bf9a5




Re: biblatex (features/biblatex2) settings dialog

2017-01-13 Thread PhilipPirrip
On Fri, 13 Jan 2017 18:48:13 +0100, Jürgen Spitzmüller wrote:
> I think I have fixed this today.
> Please try again with recent master (not features/biblatex2).

OK, thanks. This works now. 

Hope you don't mind if I report other findings here. Reporting on lyx.org 
bug tracker takes too much time:

New document. Choose biblatex in Document Settings. Insert an option, 
Apply. Delete the option - it remains in the arguments to biblatex call, 
and it's back there when reopening the document.



Re: biblatex (features/biblatex2) settings dialog

2017-01-13 Thread Jürgen Spitzmüller
Am Freitag, den 13.01.2017, 17:40 + schrieb PhilipPirrip:
> The biblatex settings dialog enters some undefined state when one 
> - chooses Style engine Biblatex
> - changes, for example, Biblatex bibliography style field to some
> other 
> value
> - presses either of the two Reset buttons or Match
> 
> The other style (in this example Biblatex citation style) dropdown
> menu 
> becomes inactive, i.e. it shows no items, and pressing the Reset
> button 
> gives unpredictable results in exported latex code.

I think I have fixed this today.

Please try again with recent master (not features/biblatex2).

Jürgen

> 
> Can anyone confirm this? 
> 

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


Re: biblatex (features/biblatex2) branch and master/child

2017-01-13 Thread Jürgen Spitzmüller
Am Freitag, den 13.01.2017, 12:32 -0500 schrieb Richard Heck:
> On 01/13/2017 12:29 PM, PhilipPirrip wrote:
> > This is probably more of a general issue: when *master* is set to
> > use 
> > biblatex, and a child hasn't been changed to use biblatex as well
> > but 
> > uses, for example, natbib, two inconsistencies can happen:
> > 1) when child contains "Insert>...>Bibliography", it will have 
> > \bibliographystyle and \bibliography commands, but will add the
> > correct  
> > \addbibresource to the master. The solution would be to
> > automatically 
> > switch the child to biblatex or at least warn the users of this 
> > inconsistency on their side. 
> > 2) child can have commands like \citeyearpar that will not be
> > recognized 
> > by biblatex when the master document is compiled. 
> 
> I think I saw a recent commit that addressed this kind of problem.

Right. As I wrote you: please update to the most recent version (which
is in master meanwhile, not features/biblatex2!).

Please report back if this issue still persists.

> > I'm actually wondering if there's really need for child documents
> > to have 
> > their own Document>Settings (their own preamble), independent of
> > the 
> > master document's settings. 
> 
> This has been discussed many times. Being a child document isn't an
> intrinsic feature of a file. It could
> be a child of many different documents, and also sometimes be used on
> its own. I have many such files.

Such as beamer presentations, that could be children of beamer
handouts. Master/child is much more than book/chapters.

> That said, it wouldn't be terrible to have some option that meant:
> Always treat this document as a child,
> and do not attempt to use its own settings. But then it's not clear
> what
> that means if it isn't a child

I am not sure what we will gain by this.

Thanks for testing!

Jürgen

> 
> Richard
> 

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


biblatex (features/biblatex2) settings dialog

2017-01-13 Thread PhilipPirrip
The biblatex settings dialog enters some undefined state when one 
- chooses Style engine Biblatex
- changes, for example, Biblatex bibliography style field to some other 
value
- presses either of the two Reset buttons or Match

The other style (in this example Biblatex citation style) dropdown menu 
becomes inactive, i.e. it shows no items, and pressing the Reset button 
gives unpredictable results in exported latex code.

Can anyone confirm this? 



Re: biblatex (features/biblatex2) branch and master/child

2017-01-13 Thread Richard Heck
On 01/13/2017 12:29 PM, PhilipPirrip wrote:
> This is probably more of a general issue: when *master* is set to use 
> biblatex, and a child hasn't been changed to use biblatex as well but 
> uses, for example, natbib, two inconsistencies can happen:
> 1) when child contains "Insert>...>Bibliography", it will have 
> \bibliographystyle and \bibliography commands, but will add the correct  
> \addbibresource to the master. The solution would be to automatically 
> switch the child to biblatex or at least warn the users of this 
> inconsistency on their side. 
> 2) child can have commands like \citeyearpar that will not be recognized 
> by biblatex when the master document is compiled. 

I think I saw a recent commit that addressed this kind of problem.

> I'm actually wondering if there's really need for child documents to have 
> their own Document>Settings (their own preamble), independent of the 
> master document's settings. 

This has been discussed many times. Being a child document isn't an
intrinsic feature of a file. It could
be a child of many different documents, and also sometimes be used on
its own. I have many such files.

That said, it wouldn't be terrible to have some option that meant:
Always treat this document as a child,
and do not attempt to use its own settings. But then it's not clear what
that means if it isn't a child

Richard



biblatex (features/biblatex2) branch and master/child

2017-01-13 Thread PhilipPirrip
This is probably more of a general issue: when *master* is set to use 
biblatex, and a child hasn't been changed to use biblatex as well but 
uses, for example, natbib, two inconsistencies can happen:
1) when child contains "Insert>...>Bibliography", it will have 
\bibliographystyle and \bibliography commands, but will add the correct  
\addbibresource to the master. The solution would be to automatically 
switch the child to biblatex or at least warn the users of this 
inconsistency on their side. 
2) child can have commands like \citeyearpar that will not be recognized 
by biblatex when the master document is compiled. 

I'm actually wondering if there's really need for child documents to have 
their own Document>Settings (their own preamble), independent of the 
master document's settings. 

What are your thoughts?






Re: Cannot use lyx anymore because of missing cite-engine basic

2017-01-13 Thread Jürgen Spitzmüller
Am Freitag, den 13.01.2017, 17:23 +0100 schrieb Kornel Benko:
> Works now, thanks.

I have to thank you. Sorry for being so ignorant about cmake.

Jürgen

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


Re: Cannot use lyx anymore because of missing cite-engine basic

2017-01-13 Thread Kornel Benko
Am Freitag, 13. Januar 2017 um 17:04:18, schrieb Kornel Benko 
> Am Freitag, 13. Januar 2017 um 16:43:12, schrieb Jürgen Spitzmüller 
> 
> > 2017-01-13 16:37 GMT+01:00 Jürgen Spitzmüller :
> > 
> > > 2017-01-13 16:18 GMT+01:00 Kornel Benko :
> > >
> > >> Todays lyx(master-branch) opens documents with the dialog-message
> > >>
> > >> The cite engine basic has been requested by this document ...
> > >>
> > >> If clocking OK, the file is opened. But if trying to use
> > >> Document->Settings...
> > >> the error-dialog displays again. Click on OK now leads to crash
> > >>
> > >> Anyone there with the same experience?
> > >>
> > >
> > > Did you run Tools > Reconfigure?
> > >
> 
> Of course.
> 
> > Also, make sure the files in the new lib/citeengines directory are properly
> > installed. As I have no idea how CMake works, I have not tested that (I was
> > thinking that, as opposed to autotools, new files do not need to be
> > specifially registered for CMake).
> 
> Probably this is the reason. I missed this new directory, will try to handle 
> it.
> 
> > Jürgen
> 

Works now, thanks.

Kornel

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


Re: Cannot use lyx anymore because of missing cite-engine basic

2017-01-13 Thread Kornel Benko
Am Freitag, 13. Januar 2017 um 16:43:12, schrieb Jürgen Spitzmüller 

> 2017-01-13 16:37 GMT+01:00 Jürgen Spitzmüller :
> 
> > 2017-01-13 16:18 GMT+01:00 Kornel Benko :
> >
> >> Todays lyx(master-branch) opens documents with the dialog-message
> >>
> >> The cite engine basic has been requested by this document ...
> >>
> >> If clocking OK, the file is opened. But if trying to use
> >> Document->Settings...
> >> the error-dialog displays again. Click on OK now leads to crash
> >>
> >> Anyone there with the same experience?
> >>
> >
> > Did you run Tools > Reconfigure?
> >

Of course.

> Also, make sure the files in the new lib/citeengines directory are properly
> installed. As I have no idea how CMake works, I have not tested that (I was
> thinking that, as opposed to autotools, new files do not need to be
> specifially registered for CMake).

Probably this is the reason. I missed this new directory, will try to handle it.

> Jürgen

Kornel

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


Re: Cannot use lyx anymore because of missing cite-engine basic

2017-01-13 Thread Jürgen Spitzmüller
2017-01-13 16:37 GMT+01:00 Jürgen Spitzmüller :

> 2017-01-13 16:18 GMT+01:00 Kornel Benko :
>
>> Todays lyx(master-branch) opens documents with the dialog-message
>>
>> The cite engine basic has been requested by this document ...
>>
>> If clocking OK, the file is opened. But if trying to use
>> Document->Settings...
>> the error-dialog displays again. Click on OK now leads to crash
>>
>> Anyone there with the same experience?
>>
>
> Did you run Tools > Reconfigure?
>

Also, make sure the files in the new lib/citeengines directory are properly
installed. As I have no idea how CMake works, I have not tested that (I was
thinking that, as opposed to autotools, new files do not need to be
specifially registered for CMake).

Jürgen


Re: Cannot use lyx anymore because of missing cite-engine basic

2017-01-13 Thread Jürgen Spitzmüller
2017-01-13 16:18 GMT+01:00 Kornel Benko :

> Todays lyx(master-branch) opens documents with the dialog-message
>
> The cite engine basic has been requested by this document ...
>
> If clocking OK, the file is opened. But if trying to use
> Document->Settings...
> the error-dialog displays again. Click on OK now leads to crash
>
> Anyone there with the same experience?
>

Did you run Tools > Reconfigure?

Jürgen


>
> Kornel
>
>


Cannot use lyx anymore because of missing cite-engine basic

2017-01-13 Thread Kornel Benko
Todays lyx(master-branch) opens documents with the dialog-message

The cite engine basic has been requested by this document ...

If clocking OK, the file is opened. But if trying to use Document->Settings...
the error-dialog displays again. Click on OK now leads to crash

Anyone there with the same experience?

Kornel



signature.asc
Description: This is a digitally signed message part.
(  1) lyx2.3: lyx::frontend::Alert::doError(std::__cxx11::basic_string const&, 
std::__cxx11::basic_string const&, bool)
(  2) lyx2.3: void std::_Bind, std::allocator > const>, 
std::reference_wrapper const>, 
std::reference_wrapper))(std::__cxx11::basic_string const&, 
std::__cxx11::basic_string const&, bool)>::__call(std::tuple<>&&, std::_Index_tuple<0ul, 1ul, 2ul>)
(  3) lyx2.3: void std::_Bind, std::allocator > const>, 
std::reference_wrapper const>, 
std::reference_wrapper))(std::__cxx11::basic_string const&, 
std::__cxx11::basic_string const&, bool)>::operator()<, void>()
(  4) lyx2.3: std::_Function_handler, std::allocator > const>, 
std::reference_wrapper const>, 
std::reference_wrapper))(std::__cxx11::basic_string const&, 
std::__cxx11::basic_string const&, bool)> >::_M_invoke(std::_Any_data const&)
(  5) lyx2.3: std::function::operator()() const
(  6) lyx2.3: lyx::frontend::InGuiThread::synchronousFunctionCall()
(  7) lyx2.3: lyx::frontend::IntoGuiThreadMover::callInGuiThread()
(  8) lyx2.3: void lyx::frontend::InGuiThread::call const>, 
std::reference_wrapper const>, 
std::reference_wrapper))(std::__cxx11::basic_string const&, 
std::__cxx11::basic_string const&, bool)> >(std::_Bind, std::allocator > const>, 
std::reference_wrapper const>, 
std::reference_wrapper))(std::__cxx11::basic_string const&, 
std::__cxx11::basic_string const&, bool)>)
(  9) lyx2.3: void lyx::frontend::InGuiThread::call, 
std::allocator > const&, std::__cxx11::basic_string const&, bool), 
std::__cxx11::basic_string const, std::__cxx11::basic_string const, bool>(void 
(*)(std::__cxx11::basic_string const&, std::__cxx11::basic_string const&, bool), 
std::__cxx11::basic_string const&, std::__cxx11::basic_string const&, bool&)
( 10) lyx2.3: lyx::frontend::Alert::error(std::__cxx11::basic_string const&, 
std::__cxx11::basic_string const&, bool)
( 11) lyx2.3: lyx2.3() [0xd9a14e]
( 12) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(+0x36cb0) [0x7f41b5ddecb0]
( 13) /usr/local/gcc6.1/lib64/libstdc: 
/usr/local/gcc6.1/lib64/libstdc++.so.6(_ZNKSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE7compareEPKc+0x10)
 [0x7f41b67af2a0]
( 14) lyx2.3: bool std::operator==(std::__cxx11::basic_string const&, char const*)
( 15) lyx2.3: lyx::frontend::GuiDocument::isBiblatex() const
( 16) lyx2.3: lyx::frontend::GuiDocument::updateEngineDependends()
( 17) lyx2.3: lyx::frontend::GuiDocument::paramsToDialog()
( 18) lyx2.3: 
lyx::frontend::GuiDocument::initialiseParams(std::__cxx11::basic_string const&)
( 19) lyx2.3: lyx::frontend::Dialog::showData(std::__cxx11::basic_string const&)
( 20) lyx2.3: lyx::frontend::GuiView::doShowDialog(QString const&, QString 
const&, lyx::Inset*)
( 21) lyx2.3: lyx2.3() [0x1114e34]
( 22) /usr/BUILD/BuildQt5/5.7/gcc_64/lib/libQt5Core.so.5: 
QMetaObject::activate(QObject*, int, int, void**)
( 23) lyx2.3: lyx::frontend::GuiView::triggerShowDialog(QString const&, QString 
const&, lyx::Inset*)
( 24) lyx2.3: 
lyx::frontend::GuiView::showDialog(std::__cxx11::basic_string

Re: [LyX/master] configure.py: Make 'notepad' last in text editor list

2017-01-13 Thread Guenter Milde
On 2017-01-13, Paul A. Rubin wrote:
> On 01/13/2017 03:27 AM, Guenter Milde wrote:
>> A more general question to all developers:

>> When checking for default viewer/editor applications during (re)configure,
>> should LyX

>> a) prefer feature rich applications, or
>> b) prefer small and fast-starting applications.
...

> [...] what I would prefer is that my system default choices be used 
> (which circles back to the xdg-open problem). Can a Python script 
> "easily" obtain MIME settings from the environment?

The hard part is to get it in a way everyone is satisfied with.

> Assuming that the xdg-utils package is installed, the shell command 
> 'xdg-mime query default application/pdf' will return the default 
> application (if one is set) for PDF files. On my system, the return 
> value is 'xreader.desktop'. Unfortunately, for 'text/plain' the result 
> is the somewhat less easily interpreted 'userapp-xed-07V7SY.desktop' 
> (where xed is the correct answer -- no idea why it's so unclear). 

Here, I get "wine-extension-txt.desktop" (although better alternatives like
leafpad are installed), which is not what I want.

> For 'image/jpeg' and 'image/png' the default is 'xviewer.desktop'. When
> no default is set (as is the case for 'image/svg' on my system), the 
> xdg-mime query returns nothing.

IMV, using xdg-mime query seems the right way but not easy.
Maybe you can open an enhancement ticket.

Günter



Re: [LyX/master] configure.py: Make 'notepad' last in text editor list

2017-01-13 Thread Stephan Witt
Am 13.01.2017 um 14:32 schrieb Paul A. Rubin :
> 
> On 01/13/2017 03:27 AM, Guenter Milde wrote:
>> A more general question to all developers:
>> 
>> When checking for default viewer/editor applications during (re)configure,
>> should LyX
>>   a) prefer feature rich applications, or
>> b) prefer small and fast-starting applications.
>> 
>> Current praxis seems to be:
>>   1. KDE/QT applications
>>   2. GNOME/GTK applications
>>   3. Windows
>> and in these categories a) feature rich apps first.
>> 
>> I prefer "small first", but not so much that I would change
>> anything without a broad consensus.
>> 
>> 
> I think I would lean to fast-starting (not necessarily small footprint),

+1

> but really what I would prefer is that my system default choices be used 
> (which circles back to the xdg-open problem).

+1

> Can a Python script "easily" obtain MIME settings from the environment?
> 
> Assuming that the xdg-utils package is installed, the shell command 'xdg-mime 
> query default application/pdf' will return the default application (if one is 
> set) for PDF files. On my system, the return value is 'xreader.desktop'. 
> Unfortunately, for 'text/plain' the result is the somewhat less easily 
> interpreted 'userapp-xed-07V7SY.desktop' (where xed is the correct answer -- 
> no idea why it's so unclear). For 'image/jpeg' and 'image/png' the default is 
> 'xviewer.desktop'. When no default is set (as is the case for 'image/svg' on 
> my system), the xdg-mime query returns nothing.
> 
> If the configuration script started out by checking for default choices, and 
> honoring those it finds, I wouldn't worry too much about the order of the 
> options when it falls back to looking for installed applications for those 
> where no default is set.
> 
> Paul
> 



Re: [LyX/master] configure.py: Make 'notepad' last in text editor list

2017-01-13 Thread Joel Kulesza
On Fri, Jan 13, 2017 at 1:27 AM, Guenter Milde  wrote:

>
> A more general question to all developers:
>
> When checking for default viewer/editor applications during (re)configure,
> should LyX
>
> a) prefer feature rich applications, or
> b) prefer small and fast-starting applications.
>

I don't regard myself as much of a developer, but my opinion would be for
small/fast.


Re: [LyX/master] configure.py: Make 'notepad' last in text editor list

2017-01-13 Thread Paul A. Rubin

On 01/13/2017 03:27 AM, Guenter Milde wrote:

A more general question to all developers:

When checking for default viewer/editor applications during (re)configure,
should LyX
   
a) prefer feature rich applications, or

b) prefer small and fast-starting applications.

Current praxis seems to be:
   1. KDE/QT applications
   2. GNOME/GTK applications
   3. Windows
and in these categories a) feature rich apps first.

I prefer "small first", but not so much that I would change
anything without a broad consensus.


I think I would lean to fast-starting (not necessarily small footprint), 
but really what I would prefer is that my system default choices be used 
(which circles back to the xdg-open problem). Can a Python script 
"easily" obtain MIME settings from the environment?


Assuming that the xdg-utils package is installed, the shell command 
'xdg-mime query default application/pdf' will return the default 
application (if one is set) for PDF files. On my system, the return 
value is 'xreader.desktop'. Unfortunately, for 'text/plain' the result 
is the somewhat less easily interpreted 'userapp-xed-07V7SY.desktop' 
(where xed is the correct answer -- no idea why it's so unclear). For 
'image/jpeg' and 'image/png' the default is 'xviewer.desktop'. When no 
default is set (as is the case for 'image/svg' on my system), the 
xdg-mime query returns nothing.


If the configuration script started out by checking for default choices, 
and honoring those it finds, I wouldn't worry too much about the order 
of the options when it falls back to looking for installed applications 
for those where no default is set.


Paul



Re: [LyX/2.2.x] Assure long tooltip is correctly formatted.

2017-01-13 Thread Jürgen Spitzmüller
Am Freitag, den 13.01.2017, 11:11 +0100 schrieb Guillaume Munch:
> Hi Jürgen, I do not remember backporting formatToolTip to stable.
> Either
> one can backport it, or this should be only for master. 

Oops, sorry. I will use support::wrap for this specific case now.

> (Independently,
> I will try to see why this was not called automatically in master.)

OK. Maybe because this is a sub-dialog?

Jürgen

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


Re: [LyX/2.2.x] Assure long tooltip is correctly formatted.

2017-01-13 Thread Guillaume Munch

Le 13/01/2017 à 09:09, Juergen Spitzmueller a écrit :

commit ca9c8dbde1d8a3d4ceeba990bbfcab17bfecb940
Author: Juergen Spitzmueller 
Date:   Fri Jan 13 09:07:44 2017 +0100

Assure long tooltip is correctly formatted.

Amendment to ffb195b5e9fa

...

+   add_->bibLW->setToolTip(formatToolTip(qt_("This list consists of all 
databases that are indexed by LaTeX and thus are found without a file path. "

...

Hi Jürgen, I do not remember backporting formatToolTip to stable. Either
one can backport it, or this should be only for master. (Independently,
I will try to see why this was not called automatically in master.)



Re: [LyX/master] configure.py: Make 'notepad' last in text editor list

2017-01-13 Thread Guenter Milde
On 2017-01-12, Scott Kostyshak wrote:
> On Thu, Jan 12, 2017 at 04:08:18PM +0100, Günter Milde wrote:
>> commit 8e65250110cc0003b370c71e27c5713b8051ac0e
...
>> * Under Linux, notepad comes with the Windows emulator "wine"
>> but it is not a good choice for the default text editor.

> If I remember correctly from long ago, notepad is not even a good choice
> for Windows. It had problems simply with figuring out where linebreaks
> were. I remember wordpad being a better choice.
...

I would leave the organization of Windows default applications to the
Windows-using developers.


A more general question to all developers:

When checking for default viewer/editor applications during (re)configure,
should LyX
  
a) prefer feature rich applications, or
b) prefer small and fast-starting applications.

Current praxis seems to be:
  1. KDE/QT applications
  2. GNOME/GTK applications
  3. Windows
and in these categories a) feature rich apps first.

I prefer "small first", but not so much that I would change
anything without a broad consensus.

Günter