Re: Opening activated branch insets

2022-03-28 Thread Scott Kostyshak
On Mon, Mar 28, 2022 at 02:22:22PM +0200, Pavel Sanda wrote: > Hi, > in my memory when some branch was activated in document settings all its > insets got opened, which was handy. > But it does not seem to function that way anymore. I'm the one to blame: 742b39f4. See also discussion here: h

Re: Lots of duplicate code in docbook

2022-03-28 Thread Thibaut Cuvelier
On Mon, 21 Mar 2022 at 13:11, Lorenzo Bertini wrote: > Il 21/03/22 11:49, Daniel ha scritto: > > On 2022-03-21 10:55, Lorenzo Bertini wrote: > >> There is some degree of duplication between Docbook and LyXHTML code. > >> I think its because the latter is much older and Thibaut had to write > >> i

Opening activated branch insets

2022-03-28 Thread Pavel Sanda
Hi, in my memory when some branch was activated in document settings all its insets got opened, which was handy. But it does not seem to function that way anymore. Is this intended? How do I open all activated branch insets now? Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://list

Re: Bug#1008257: lyx: bash-completion not working

2022-03-28 Thread HernĂ¡n Gustavo Solari
I have extended the completion for lyx. This is not a bug fix, though. The uses I see for lyx on a terminal are: a. lyx my.lyx b. lyx -i latex|xetex|luatex my.tex c. lyx my.lyx -e pdflatex|tex|xetex|luatex|xhtml d. lyx my.lyx -E pdflatex|tex|xetex|luatex|xhtml my.pdf|my.tex|my.xhtml a. standard u