Insert Citation Dialog Kudos

[Joel Kulesza]

After some time working with it, my thanks to Jürgen for reworking the
Insert -> Citation dialog.  I find this **much** more pleasant to use than
previously.

- Joel

Re: Alt+A 0

[Andrew Parsloe]

On 26/05/2017 1:46 a.m., Scott Kostyshak wrote:

On Thu, May 25, 2017 at 12:51:26PM +1200, Andrew Parsloe wrote:

The shortcut keys Alt+A 1, ..., Alt+A 9 are assigned to argument-insert 1
... argument-insert 9. On all the keyboards I have used, the numbers run in
a row 1234567890 from left to right.


+1


On my system Alt+A 0 is unassigned. I
suggest assigning it to argument-insert post:1. A post argument follows the
main argument, so there is a natural sequence from the ordinary arguments to
the left of the main argument, then the main argument, then post arguments.
Given the arrangement of keys on a keyboard, there seems a certain
naturalness to assigning Alt+A 0 to the first post argument.


What is an example of where 'argument-insert post:1' is useful (e.g.  a
specific inset where I can test)? I don't actually know what post:1
means and haven't used it before.

Scott

The main reason for using a post argument is to avoid confusion with 
other optional arguments. The only real-life example I can give is from 
my own work, the calculyx package 
(http://wiki.lyx.org/Examples/Calculyx). In that I define a custom inset 
called Calculate. The main argument of the inset contains a user-entered 
formula like \sin x in a math inset. An optional argument inserts an 
argument inset in which a value can be given to x, say x=\pi/12, again 
in a math inset. If the custom inset is placed inside a preview inset 
then the value of \sin x is calculated. The calculational engine used is 
the l3fp module of the LaTeX3 project, which works to 16 significant 
figures which are almost always too many, so as a kind of afterthought, 
you might want to round to, say, 4 figures with another optional 
argument. Where to place it? If placed before the main argument, what 
happens when evaluating a formula like \sin(\pi/12) where there is no 
need for the first optional argument? It is simpler to put the two 
optional arguments on either side of the main argument. In LaTeX or the 
Code Preview pane the thing then looks like


\calculyx[$x=\pi/12$]{$\sin x$}[4]

The first optional argument is entered either from the Insert menu or 
the context menu but most simply from the keyboard with the now built-in 
Alt+A 1. For the post-argument you have only the menus, there is no 
built-in shortcut. If you want one you need to assign it yourself. Given 
the happy correspondence between the run of keys on a keyboard and the 
distribution of arguments about the main argument, I felt assigning 
Alt+A 0 to the first post-argument would be a natural thing to have 
built-in in LyX.


Andrew

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

Re: LyX docs: cleaning up math options

[Scott Kostyshak]

On Thu, May 25, 2017 at 09:09:03PM +0200, Jean-Pierre wrote:
> 
> 
> 
>  Message d'origine 
> De : Scott Kostyshak 
> Envoyé : 25 mai 2017 16:59:17 GMT+02:00
> À : lyx-devel@lists.lyx.org
> Objet : Re: LyX docs: cleaning up math options
> 
> Jean-Pierre, what is the status on this? I have not followed closely all
> the discussions in this thread. Is anything blocking progress?
> 
> I posted a progress point on the list 3 weeks ago or so. As I did not  get an 
> answer, I opened a ticket to collect comments there (#10661).

Ah I forgot about that. I'll post there.

Thanks,

Scott


signature.asc
Description: PGP signature

Re: Visible version id

[Scott Kostyshak]

On Fri, May 26, 2017 at 10:38:21AM +1200, Andrew Parsloe wrote:

> After my initial request, I realised it was easy to make the version number
> visible. Initially I put a toolbar button on the View toolbar. Now I change
> the entry Submenu "Help|H" "help" in stdmenus.inc to Submenu "Help
> v.2.3.0a|H" "help". This has been useful during this alpha-testing phase.
> I'll add an item under Tips on the wiki.

That is a creative solution. Nice!

Scott


signature.asc
Description: PGP signature

Re: Visible version id

[Andrew Parsloe]

On 26/05/2017 2:46 a.m., Scott Kostyshak wrote:

On Tue, May 16, 2017 at 11:09:11AM +0200, Jean-Marc Lasgouttes wrote:

Le 16/05/2017 à 10:37, Andrew Parsloe a écrit :

The version is displayed in the main window when no document is open,
but if I understand correctly you would like for the version to be
displayed even if documents are open.

Scott


Yes. Particularly at an alpha or beta stage where one may want to check
how things worked in an earlier version.


I'd rather not add that in general, but it could be added when DEVEL_VERSION
is set.


Makes sense. Since two of our important pre-release testers want this, I
would be happy to have it. If anyone wants to implement it please go
ahead and push.

Scott

After my initial request, I realised it was easy to make the version 
number visible. Initially I put a toolbar button on the View toolbar. 
Now I change the entry Submenu "Help|H" "help" in stdmenus.inc to 
Submenu "Help v.2.3.0a|H" "help". This has been useful during this 
alpha-testing phase. I'll add an item under Tips on the wiki.


Andrew

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

Re: LyX docs: cleaning up math options

[Jean-Pierre]

 Message d'origine 
De : Scott Kostyshak 
Envoyé : 25 mai 2017 16:59:17 GMT+02:00
À : lyx-devel@lists.lyx.org
Objet : Re: LyX docs: cleaning up math options

Jean-Pierre, what is the status on this? I have not followed closely all
the discussions in this thread. Is anything blocking progress?

I posted a progress point on the list 3 weeks ago or so. As I did not  get an 
answer, I opened a ticket to collect comments there (#10661).

-- 
Jean-Pierre

\noun, \emph or any other text style change of a \href inset

[PhilipPirrip]

This used to work fine until LyX 2.3:

insert a hyperlink
select, toggle noun

you'll get
\noun{}\href{http://www.lyx.org}{lyx}

instead of
\noun{\href{http://www.lyx.org}{lyx}}


Is this intended behavior?


With \marginpar one gets
\noun{}\marginpar{\noun{bbb}}
which kind of makes more sense, but wouldn't work with \href.

Re: Gnuplot format & converter script

[Scott Kostyshak]

On Fri, May 05, 2017 at 08:03:02PM -0400, Scott Kostyshak wrote:

> Tommaso,
> 
> I found an old script from Koji for gnuplot. Is it useful now?

Tommaso,

No worries if you don't have time, but I just wanted to make sure you
saw this.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Fix bug #10263

[Enrico Forestieri]

On Thu, May 25, 2017 at 06:46:54PM +0200, Jean-Marc Lasgouttes wrote:
> Le 25/05/2017 à 17:34, Enrico Forestieri a écrit :
> > No, this is not related to language nesting but is due to the fact
> > that \textbf is not a robust command and the footnote contains
> > multiple paragraphs. Three possible solutions come to mind:
> > 1) Use \cprotect if the footnote contains a \par token
> > 2) Use \robustify, in the same case
> > 3) Revert this commit
> > 
> > See attached examples for the first two options.
> 
> The question is maybe to know why LyX tries to put the contents of the
> footnote in bold. Is it a consequence of the commit?

Yes, and it was the whole point of the commit. In this way the footnote
mark inherits the font change but the footnote text is left alone.

> In this case, it should probably be reverted.

Yes, also because I found that the workaround I suggested do not
work for color and language changes. I am going to revert it.

-- 
Enrico

Re: [LyX/master] Fix bug #10263

[Jean-Marc Lasgouttes]

Le 25/05/2017 à 17:34, Enrico Forestieri a écrit :

No, this is not related to language nesting but is due to the fact
that \textbf is not a robust command and the footnote contains
multiple paragraphs. Three possible solutions come to mind:
1) Use \cprotect if the footnote contains a \par token
2) Use \robustify, in the same case
3) Revert this commit

See attached examples for the first two options.


The question is maybe to know why LyX tries to put the contents of the 
footnote in bold. Is it a consequence of the commit? In this case, it 
should probably be reverted.


JMarc

Re: [LyX/master] Fix bug #10263

[Guillaume MM]

Le 25/05/2017 à 17:34, Enrico Forestieri a écrit :


No, this is not related to language nesting but is due to the fact
that \textbf is not a robust command and the footnote contains
multiple paragraphs. Three possible solutions come to mind:
1) Use \cprotect if the footnote contains a \par token
2) Use \robustify, in the same case
3) Revert this commit

See attached examples for the first two options.



Another solution here by calling separately \footnotemark and \footnotetext:
http://www.lyx.org/trac/ticket/10263#comment:19

For people wondering why doing this when there is no visible effect, one
should switch to KOMA-Script to see the effect on the footnote mark.

Re: [LyX/master] Fix bug #10263

[Kornel Benko]

Am Donnerstag, 25. Mai 2017 um 16:43:30, schrieb Jürgen Spitzmüller 

> Am Donnerstag, den 25.05.2017, 09:52 -0400 schrieb Scott Kostyshak:
> > On Wed, May 24, 2017 at 12:25:25AM +0200, Enrico Forestieri wrote:
> > > commit 3ceb5034905a4594fd100b8c29719699f3e87fb7
> > > Author: Enrico Forestieri 
> > > Date:   Wed May 24 00:24:54 2017 +0200
> > > 
> > > Fix bug #10263
> > 
> > git bisect suggests this commit broke the following test:
> > 
> > doc/ja/UserGuide_pdf3
> 
> Here is a simpler testcase. This is probably also related to the issue
> reported earlier today:
> http://marc.info/?l=lyx-devel=149564762120210=2
> 
> I think the above commit should be reverted.
> 
> Jürgen

The attached file should go to autotests/export IMO. But perhaps with a more 
understandable name?

Kornel

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

Re: [LyX/master] Fix bug #10263

[Enrico Forestieri]

On Thu, May 25, 2017 at 09:52:53AM -0400, Scott Kostyshak wrote:
> 
> git bisect suggests this commit broke the following test:
> 
> doc/ja/UserGuide_pdf3
> 
> This test corresponds to compiling the ja UserGuide to format
> PDF (dvipdfm), which is the default format.
> 
> Perhaps the commit triggered a bug in a different part of our code?
> The error I now get is:
> 
> {\footnote {\textbf {【訳註】}和文の場合に，実際にこのような索引項目を\ETC.
> ! Paragraph ended before \text@command was complete.
>  
>\par 
> l.3173 ...)}かじょうがき@箇条書き!れんばん@連番}}
>  ．
> I suspect you've forgotten a `}', causing me to apply this
> control sequence to too much text. How can we recover?
> My plan is to forget the whole thing and hope for the best.
> 
> ! Too many }'s.
> \textbf  ...\else \hmode@bgroup \text@command {#1}
>   \bfseries \check@icl 
> #1\ch...
> 
> This reminds me of the tricky language nesting issues we've had.

No, this is not related to language nesting but is due to the fact
that \textbf is not a robust command and the footnote contains
multiple paragraphs. Three possible solutions come to mind:
1) Use \cprotect if the footnote contains a \par token
2) Use \robustify, in the same case
3) Revert this commit

See attached examples for the first two options.

-- 
Enrico
#LyX 2.3 created this file. For more info see http://www.lyx.org/
\lyxformat 543
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass article
\begin_preamble
\usepackage{cprotect}
\end_preamble
\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
\use_microtype false
\use_dash_ligatures true
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\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
\is_math_indent 0
\math_numbering_side default
\quotes_style english
\dynamic_quotes 0
\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 ERT
status open

\begin_layout Plain Layout


\backslash
cprotect
\end_layout

\end_inset


\series bold
foo
\begin_inset Foot
status open

\begin_layout Plain Layout
bar
\end_layout

\begin_layout Plain Layout
baz
\end_layout

\end_inset


\end_layout

\end_body
\end_document
#LyX 2.3 created this file. For more info see http://www.lyx.org/
\lyxformat 543
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass article
\begin_preamble
\usepackage{etoolbox}
\end_preamble
\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
\use_microtype false
\use_dash_ligatures true
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\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
\is_math_indent 0
\math_numbering_side default
\quotes_style english

Re: templates handling

[Scott Kostyshak]

On Thu, Apr 20, 2017 at 05:02:41PM +, Guenter Milde wrote:
> Dear LyXers,
> 
> background reading for the "reorganize templates folder" ticket, I found an
> interesting statement in the Customization guide (5.2.4 Creating templates):
> 
> 
>   Templates are created just like usual documents: using LyX. The only
>   difference is that usual documents contain all possible settings,
>   including the font scheme and the paper size. Usually a user doesn't
>   want a template to overwrite his preferred settings for such
>   parameters. For that reason, the designer of a template should remove
>   the corresponding commands like \font_roman or \papersize from the
>   template LyX file. This can be done with any simple text-editor, for
>   example vi or notepad.
>   
> I fully agree with the idea to leave out settings that are not relevant for or
> fixed by the template's document class or purpose. 
> 
> This may also solve our problem with the default default fonts beeing ugly
> bitmaps: Choose LatinModern in the default template and leave out the font
> settings in all templates that would use bitmap default fonts.
> 
> However:
> 
> a) The templates that ship with LyX in lib/templates don't do so, they
>contain all possible settings (at least all font settings).
>
>This may be due to "just saving" after some edit or lyx2lyx inserting
>settings with format conversions -- with the developer doing the edit or
>conversion unaware of the above passage in Customization.lyx
>
> b) Documents using a template without settings are *not* filled with a
>user's preferred settings (as stored in templates/defaults.lyx) but with
>the global LyX defaults.
>
> Am I missing something? 
> Is this a bug?

I agree with what you wrote and I had not noticed this before. I took a
look at just \papersize, and only dinbrief.lyx has non-default. Is the
problem worse for other settings?

Note that this conversation is similar to the discussion on math
settings being "automatic".

Scott


signature.asc
Description: PGP signature

Re: LyX docs: cleaning up math options

[Scott Kostyshak]

Jean-Pierre, what is the status on this? I have not followed closely all
the discussions in this thread. Is anything blocking progress?

Scott


signature.asc
Description: PGP signature

Re: Update: polyglossia in 2.2.3

[Jürgen Spitzmüller]

Am Mittwoch, den 24.05.2017, 19:36 +0200 schrieb N. Andrew Walsh:
> in a \footnote block, if a block of text is both set to a different
> language (invoking a polyglossia language definition) and contained
> in a \quote block, the compiler will delete the last bracket of the
> footnote. This causes all subsequent \footnote invocations to fail,
> as they now appear as an attempt to insert a footnote within a
> footnote. Bigfoot returns an error for the same reason. 

See http://www.lyx.org/trac/ticket/10263#comment:18

Jürgen

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

Re: Visible version id

[Scott Kostyshak]

On Tue, May 16, 2017 at 11:09:11AM +0200, Jean-Marc Lasgouttes wrote:
> Le 16/05/2017 à 10:37, Andrew Parsloe a écrit :
> > > The version is displayed in the main window when no document is open,
> > > but if I understand correctly you would like for the version to be
> > > displayed even if documents are open.
> > > 
> > > Scott
> > > 
> > Yes. Particularly at an alpha or beta stage where one may want to check
> > how things worked in an earlier version.
> 
> I'd rather not add that in general, but it could be added when DEVEL_VERSION
> is set.

Makes sense. Since two of our important pre-release testers want this, I
would be happy to have it. If anyone wants to implement it please go
ahead and push.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Fix bug #10263

[Jürgen Spitzmüller]

Am Donnerstag, den 25.05.2017, 09:52 -0400 schrieb Scott Kostyshak:
> On Wed, May 24, 2017 at 12:25:25AM +0200, Enrico Forestieri wrote:
> > commit 3ceb5034905a4594fd100b8c29719699f3e87fb7
> > Author: Enrico Forestieri 
> > Date:   Wed May 24 00:24:54 2017 +0200
> > 
> > Fix bug #10263
> 
> git bisect suggests this commit broke the following test:
> 
> doc/ja/UserGuide_pdf3

Here is a simpler testcase. This is probably also related to the issue
reported earlier today:
http://marc.info/?l=lyx-devel=149564762120210=2

I think the above commit should be reverted.

Jürgen

fn.lyx
Description: application/lyx


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

closer interaction of -dbg options and trac components

[Scott Kostyshak]

Just a random thought that I don't expect anyone to respond to and I'm
not interested in working on myself:

It would be nice to have a larger (set) interaction of the -dbg options
and our trac components. I keep thinking "clipboard" is a trac component
but it's not. This would also make it easy to tell users what -dbg
option that set to give more information on a trac ticket.

Scott


signature.asc
Description: PGP signature

Re: Fix for vertical table border for added column

[Scott Kostyshak]

On Wed, May 24, 2017 at 08:07:52AM +0200, racoon wrote:

> Thanks. Yes, it is still not patched in latest master so I guess it is
> pending.
> 
> Feel free to take a look.

OK I'll put this on my list of things to look at.

Scott


signature.asc
Description: PGP signature

Re: [coverity again] missing move constructors

[Scott Kostyshak]

On Thu, May 25, 2017 at 01:08:20AM +0200, Guillaume MM wrote:

> Hi Scott, indeed there is no need for this in 2.3 and I meant to reply
> to Jean-Marc later. In addition gcc 4.6 might get in the way and I am
> hoping that 2.4 is the good time to unsupport it. So it's best not to
> have this in 2.3.

Makes sense.

Thanks,

Scott


signature.asc
Description: PGP signature

Re: Lyx 2.2 errors w/ miktex 2.9.6 (on win10)

[Scott Kostyshak]

On Wed, May 24, 2017 at 01:29:45PM -0400, Cris Fuhrman wrote:
> On Tue, May 23, 2017 at 10:38 PM, Scott Kostyshak  wrote:
> 
> > On Wed, Apr 19, 2017 at 11:29:12AM +0200, Jean-Marc Lasgouttes wrote:
> > > I understand that this gives minor debugging information (that can
> > probably
> > > be obtained via a debugging channel), but it is not the first time that
> > it
> > > triggers LaTeX file length limits.
> >
> > Chris, do you feel like writing up a bug/enhancement request at
> >
> > https://www.lyx.org/trac
> >
> > ? A reproducible example would indeed give us a push to look into an
> > improvement.
> >
> >
> I have 2 Win 10 machines (an older Win 7 that was upgraded and a newer
> Surface Pro 4). The newer machine seems not to have the problem today (I
> couldn't reproduce it). I'll try this at home on my upgraded PC, which is
> where I know I had it before. It could be system-dependent. As I recall, it
> was one of the file conversion routines that was failing, not producing the
> output it should, and the next step in the LyX processing was getting a
> file not found error.
> 
> On a related note, the MikTeX distribution servers were intentionally
> offline again yesterday. I got a couple more upvotes to my answer at
> https://tex.stackexchange.com/a/254393/17868. I posted this issue in the
> MikTeX tracker: https://sourceforge.net/p/miktex/bugs/2604/ -- it directly
> affects the LyX installations relying on MikTeX.

Thanks for the detailed update, Chris. Let us know if there's anything
you think we can do or should change to help prevent these issues.

Scott


signature.asc
Description: PGP signature

Re: Alt+A 0

[Scott Kostyshak]

On Thu, May 25, 2017 at 12:51:26PM +1200, Andrew Parsloe wrote:
> The shortcut keys Alt+A 1, ..., Alt+A 9 are assigned to argument-insert 1
> ... argument-insert 9. On all the keyboards I have used, the numbers run in
> a row 1234567890 from left to right.

+1

> On my system Alt+A 0 is unassigned. I
> suggest assigning it to argument-insert post:1. A post argument follows the
> main argument, so there is a natural sequence from the ordinary arguments to
> the left of the main argument, then the main argument, then post arguments.
> Given the arrangement of keys on a keyboard, there seems a certain
> naturalness to assigning Alt+A 0 to the first post argument.

What is an example of where 'argument-insert post:1' is useful (e.g.  a
specific inset where I can test)? I don't actually know what post:1
means and haven't used it before.

Scott


signature.asc
Description: PGP signature

Re: Update: polyglossia in 2.2.3

[Jürgen Spitzmüller]

Am Mittwoch, den 24.05.2017, 19:36 +0200 schrieb N. Andrew Walsh:
> Dear List:
> 
> In regards to the previous question about footnotes, I have isolated
> the issue I'm having to the following:
> 
> in a \footnote block, if a block of text is both set to a different
> language (invoking a polyglossia language definition) and contained
> in a \quote block, the compiler will delete the last bracket of the
> footnote. This causes all subsequent \footnote invocations to fail,
> as they now appear as an attempt to insert a footnote within a
> footnote. Bigfoot returns an error for the same reason. 

Could you post a minimal example file, please?

> Furthermore, Lyx codes ancient Greek in the .lyx file differently
> than the polyglossia definition does. The preamble has the following:
> 
> \setotherlanguage[variant=ancient]{greek}
> 
> but within the .lyx file itself the following is used:
> 
> \lang ancientgreek

No, the LyX language name does not necessarily be equal to the
polyglossia (or babel) language name. If only for the reason that
polyglossia and babel names often differ as well.

> Might this also cause problems with polyglossia? Should I submit
> this/these as a bug?

Please post a file for the former problem first. It might be easy to
fix.

Thanks,
Jürgen

> 
> Lastly, the problems I'm having here do not occur with 2.2.2, so
> downgrading provides me with a workaround at present.
> 
> Thanks in advance for your help.
> 
> Cheers,
> 
> Andrew Walsh

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