Re: Indentation and (un)commenting in local layout and preamble

On 2022-09-14 09:04, Daniel wrote: On 13/09/2022 18:27, Jean-Marc Lasgouttes wrote: Le 13/09/2022 à 16:12, Daniel a écrit : And I guess more importantly in license.rtf it says: "LyX. You can redistribute LyX and/or modify it under the terms of the GNU General Public License as published by

Patch to insert entries for Section boxes, Variable-width minipages, Fix Computer Modern Fonts, LaTeX Kernel Fixes, Minimalistic Insets and Title and Preamble Hacks into Chapter 4 Modules of Additiona

tle and Preamble Hacks into Chapter 4 Modules of Additional.lyx --- lib/doc/Additional.lyx | 311 + 1 file changed, 311 insertions(+) diff --git a/lib/doc/Additional.lyx b/lib/doc/Additional.lyx index 4af6e098fb..c06d1a83d7 100644 --- a/lib/doc/Additional.lyx +++ b/

Re: Is "Edit" button clearly labeled in local layout and LaTeX preamble?

On Fri, Dec 02, 2022 at 02:45:17PM -0500, Richard Kimberly Heck wrote: > On 12/2/22 14:33, Scott Kostyshak wrote: > > Would it make sense to change these to "Edit Externally" ? Or is that too > > verbose? > > I think that's fine, and makes sense. Thanks, done at 9f7bbead. Scott signature.asc

Re: Is "Edit" button clearly labeled in local layout and LaTeX preamble?

On 12/2/22 14:33, Scott Kostyshak wrote: Would it make sense to change these to "Edit Externally" ? Or is that too verbose? I think that's fine, and makes sense. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Is "Edit" button clearly labeled in local layout and LaTeX preamble?

Would it make sense to change these to "Edit Externally" ? Or is that too verbose? The reason I ask is that "Edit" is not so clear if you don't already know what it does. One might think that they need to click edit to change the current contents (in LyX's editor) and then be surprised when an

Re: Indentation and (un)commenting in local layout and preamble

On 13/09/2022 18:27, Jean-Marc Lasgouttes wrote: Le 13/09/2022 à 16:12, Daniel a écrit : And I guess more importantly in license.rtf it says: "LyX. You can redistribute LyX and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either

Re: Indentation and (un)commenting in local layout and preamble

Le 13/09/2022 à 16:12, Daniel a écrit : And I guess more importantly in license.rtf it says: "LyX. You can redistribute LyX and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any

Re: Indentation and (un)commenting in local layout and preamble

On Tue, 2022-09-13 at 16:12 +0200, Daniel wrote: > And I guess more importantly in license.rtf it says: > > "LyX. You can redistribute LyX and/or modify it under the terms of > the > GNU General Public License as published by the Free Software > Foundation; > either version 2 of the License, or

Re: Indentation and (un)commenting in local layout and preamble

On 13/09/2022 15:56, Daniel wrote: On 13/09/2022 12:56, Jean-Marc Lasgouttes wrote: Le 10/08/2022 à 04:15, Daniel a écrit : In the attached Qt project, I implemented those features. It probably needs some more cleaning up. But it seems to work and you could already try it out if you like. The

Re: Indentation and (un)commenting in local layout and preamble

On 13/09/2022 12:56, Jean-Marc Lasgouttes wrote: Le 10/08/2022 à 04:15, Daniel a écrit : In the attached Qt project, I implemented those features. It probably needs some more cleaning up. But it seems to work and you could already try it out if you like. The (un)commenting feature leans

Re: Indentation and (un)commenting in local layout and preamble

Le 10/08/2022 à 04:15, Daniel a écrit : In the attached Qt project, I implemented those features. It probably needs some more cleaning up. But it seems to work and you could already try it out if you like. The (un)commenting feature leans heavily on code from QtCreator. (I tried to improve a

Re: Indentation and (un)commenting in local layout and preamble

On 2022-08-14 20:20, Daniel wrote: On 2022-08-14 18:38, Kornel Benko wrote: Applies cleanly and compiles. Rudimentary test looks good. (At least writing local format feels better than what we have now). Kornel Thanks for testing. I realized that I changed the tab stop size before

Re: Indentation and (un)commenting in local layout and preamble

Widget * parent) // @ is letter in the LyX user preamble (void) new LaTeXHighlighter(preambleTE->document(), true); preambleTE->setFont(guiApp->typewriterSystemFont()); - preambleTE->setWordWrapMode(QTextOption::NoWrap); + preambleTE->setTabStop(4

Re: Indentation and (un)commenting in local layout and preamble

Am Sun, 14 Aug 2022 09:27:40 +0200 schrieb Daniel : > On 2022-08-10 04:15, Daniel wrote: > > It would be nice if LyX's source editors (for Local Layout and LaTeX > > Preamble) would have proper indentation and (un)commenting support. > > > > I know that the extern

Re: Indentation and (un)commenting in local layout and preamble

On 2022-08-10 04:15, Daniel wrote: It would be nice if LyX's source editors (for Local Layout and LaTeX Preamble) would have proper indentation and (un)commenting support. I know that the external editing is supported now, but I consider this more of a pro feature since it presupposes already

Indentation and (un)commenting in local layout and preamble

It would be nice if LyX's source editors (for Local Layout and LaTeX Preamble) would have proper indentation and (un)commenting support. I know that the external editing is supported now, but I consider this more of a pro feature since it presupposes already having set up an editor (other

Re: Cannot put new counter inset in list preamble

On 5/5/21 16:57, Scott Kostyshak wrote: I'm trying to answer a question here: https://tex.stackexchange.com/questions/595781/enumerate-numbering-without-enumitem-package/595813#595813 I just realized that one cannot insert a counter inside the List Preamble. To work around that, I had to first

Re: Cannot put new counter inset in list preamble

rt such an inset five chapters earlier? I still think fixing the workarea counter for list preamble is the way to go. This is what list preamble has been designed for. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.or

Re: Cannot put new counter inset in list preamble

Le 08/05/2021 à 20:02, Scott Kostyshak a écrit : I don't think so. Counter is always local to the list environment. Outside, the counter could be stepped for other purposes, such as (constructed example) \setcounter{enumi}{2} Hello \theenumii \begin{enumerate} \item I expect this to be 1!

Re: Cannot put new counter inset in list preamble

\theenumii > > \begin{enumerate} > \item I expect this to be 1! > \end{enumerate} Good point. > > From a user point of view, at least one who does not know anything > > about LaTeX (I'm a good proxy for such a user), it's not intuitive > > that we have to set

Re: Cannot put new counter inset in list preamble

example) \setcounter{enumi}{2} Hello \theenumii \begin{enumerate} \item I expect this to be 1! \end{enumerate} > From a user point of view, at least one who does not know anything > about LaTeX (I'm a good proxy for such a user), it's not intuitive > that we have to set the counter in the List

Re: Cannot put new counter inset in list preamble

st > > (Level 1) counter outside of an enum. Can LyX realize that the intent > > is for the counter to be modified at the beginning of the next list? > > No, as this doesn't step the counter in LaTeX either. We need to do > that retrospectively if a counter inset is in a list p

Re: Cannot put new counter inset in list preamble

he intent > is for the counter to be modified at the beginning of the next list? No, as this doesn't step the counter in LaTeX either. We need to do that retrospectively if a counter inset is in a list preamble. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing li

Re: Cannot put new counter inset in list preamble

nge is only reflected as of > the item that follows the inset, whereas it actually applies to the > whole list when the inset is in the list preamble. > > This should be fixable, though. Good point, I noticed that too. The only alternative I can think of would be for the counter manager

Re: Cannot put new counter inset in list preamble

On Fri, May 07, 2021 at 03:51:57PM +0200, Jürgen Spitzmüller wrote: > Am Freitag, dem 07.05.2021 um 15:30 +0200 schrieb Jean-Marc Lasgouttes: > > And using the inset is better because the change is reflected in the > > UI. > > What if the argument was normal text? Then one could decide to insert

Re: Cannot put new counter inset in list preamble

whole list when the inset is in the list preamble. This should be fixable, though. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Cannot put new counter inset in list preamble

Am Freitag, dem 07.05.2021 um 15:30 +0200 schrieb Jean-Marc Lasgouttes: > And using the inset is better because the change is reflected in the > UI. > What if the argument was normal text? Then one could decide to insert > an > ERT inset in there. What are the typical values that go there?

Re: Cannot put new counter inset in list preamble

Le 07/05/2021 à 14:58, Jürgen Spitzmüller a écrit : Am Freitag, dem 07.05.2021 um 14:56 +0200 schrieb Jean-Marc Lasgouttes: It would be strange that ERT is not the same as list argument. The same holds for passthru flex insets (for preamble). I think Scott's request here is based

Re: Cannot put new counter inset in list preamble

Am Freitag, dem 07.05.2021 um 14:49 +0200 schrieb Jürgen Spitzmüller: > I have not tested chunks. It can be inserted in chunks. We could limit the permission to InsetArgument. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list

Re: Cannot put new counter inset in list preamble

Am Freitag, dem 07.05.2021 um 14:56 +0200 schrieb Jean-Marc Lasgouttes: > It would be strange that ERT is not the same as list argument. The > same holds for passthru flex insets (for preamble). I think Scott's request here is based on the observation that setting counter is something that

Re: Cannot put new counter inset in list preamble

). I have not tested chunks. It would be strange that ERT is not the same as list argument. The same holds for passthru flex insets (for preamble). We should have a notion of what an ERT inset is supposed to contain and whether this change is needed now, actually. Agreed. JMarc -- lyx

Re: Cannot put new counter inset in list preamble

Am Freitag, dem 07.05.2021 um 14:26 +0200 schrieb Jean-Marc Lasgouttes: > Thanks. It is still possible to insert these insets in literate > Chunks (e.g. R Code) or listings, right? Not in Listings and ERT (since these reimplement insetAllowed). I have not tested chunks. > We should have a notion

Re: Cannot put new counter inset in list preamble

Le 07/05/2021 à 13:39, Jürgen Spitzmüller a écrit : Am Freitag, dem 07.05.2021 um 12:49 +0200 schrieb Jürgen Spitzmüller: Insertion to verbatim layout is possible independent of my change and needs to be prohibited elsewhere. Counter was not handled in Text::getStatus() Fixed at

Re: Cannot put new counter inset in list preamble

Am Freitag, dem 07.05.2021 um 12:49 +0200 schrieb Jürgen Spitzmüller: > Insertion to verbatim layout is possible independent of my change and > needs to be prohibited elsewhere. Counter was not handled in Text::getStatus() Fixed at 70bcffca9c7fc. Jürgen signature.asc Description: This is a

Re: Cannot put new counter inset in list preamble

Am Freitag, dem 07.05.2021 um 12:18 +0200 schrieb Jean-Marc Lasgouttes: > It does not seem to do what one expects. The permission to insert this into verbatim layout is not determinate to my change. This only applies to pass thru text insets. Insertion to verbatim layout is possible independent

Re: Cannot put new counter inset in list preamble

Le 06/05/2021 à 17:44, Jürgen Spitzmüller a écrit : Am Donnerstag, dem 06.05.2021 um 17:37 +0200 schrieb Jean-Marc Lasgouttes: So it can be inserted in a Verbatim layout? Looks like a weird idea. Why? It does not seem to do what one expects. JMarc verbatim.lyx Description:

Re: Cannot put new counter inset in list preamble

Am Donnerstag, dem 06.05.2021 um 17:37 +0200 schrieb Jean-Marc Lasgouttes: > So it can be inserted in a Verbatim layout? Looks like a weird idea. Why? Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org

Re: Cannot put new counter inset in list preamble

Le 06/05/2021 à 14:45, Jürgen Spitzmüller a écrit : Am Mittwoch, dem 05.05.2021 um 10:57 -0400 schrieb Scott Kostyshak: I just realized that one cannot insert a counter inside the List Preamble. To work around that, I had to first create the counter, and then select it, and then go to Insert

Re: Cannot put new counter inset in list preamble

On Thu, May 06, 2021 at 02:45:16PM +0200, Jürgen Spitzmüller wrote: > Am Mittwoch, dem 05.05.2021 um 10:57 -0400 schrieb Scott Kostyshak: > > I just realized that one cannot insert a counter inside the List > > Preamble. To work around that, I had to first create the counter, and

Re: Cannot put new counter inset in list preamble

Am Mittwoch, dem 05.05.2021 um 10:57 -0400 schrieb Scott Kostyshak: > I just realized that one cannot insert a counter inside the List > Preamble. To work around that, I had to first create the counter, and > then select it, and then go to Insert > List Preamble. > > Sho

Cannot put new counter inset in list preamble

I'm trying to answer a question here: https://tex.stackexchange.com/questions/595781/enumerate-numbering-without-enumitem-package/595813#595813 I just realized that one cannot insert a counter inside the List Preamble. To work around that, I had to first create the counter, and then select

Re: [LyX/master] Avoid \@ifundefined after user preamble

Am Sonntag, dem 10.01.2021 um 11:58 -0500 schrieb Richard Kimberly Heck: > There are other uses of \@ifundefined in lib/layouts/. I'm happy to > fix them,  The special case here was that this is output after the user preamble. Only in this case we have problems if users set \makeatlett

Re: [LyX/master] Avoid \@ifundefined after user preamble

On 1/10/21 3:57 AM, Juergen Spitzmueller wrote: > commit c77ab339c121ba95cb25b6853545eba2780c025c > Author: Juergen Spitzmueller > Date: Sun Jan 10 09:55:45 2021 +0100 > > Avoid \@ifundefined after user preamble > > Users might have used

Re: Preamble section patch

On 9/30/20 7:07 AM, Lorenzo Bertini wrote: > Il 28/09/20 22:57, Richard Kimberly Heck ha scritto: >> So can you create a file with the new preamble that might cause a problem so >> we can see exactly what it is? >> >> Riki > My problem is with the following

Re: List Preamble Arguments

Am Montag, dem 26.10.2020 um 12:30 +0100 schrieb Daniel: > There is the list preamble inset > (https://www.lyx.org/trac/changeset/b124adbd3837/lyxgit). However, if > I > see it correctly, there is no interface currently to add arguments to > the list preamble directly (via cod

Re: List Preamble Arguments

), There have been two cases recently where people have asked about using the new counter insets to set the value of e.g., the enumi counter. The problem here is the old 'list preamble' one that is solved by the new 'list preamble' arguments. However, because those have PassThru set, you can't actually

Re: List Preamble Arguments

asked about using the new counter insets to set the value of e.g., the enumi counter. The problem here is the old 'list preamble' one that is solved by the new 'list preamble' arguments. However, because those have PassThru set, you can't actually insert the counter inset, and I think that's

Re: List Preamble Arguments

insets to set the value of e.g., the enumi counter. The problem here is the old 'list preamble' one that is solved by the new 'list preamble' arguments. However, because those have PassThru set, you can't actually insert the counter inset, and I think that's usually true with PassThru, right

Re: List Preamble Arguments

., the enumi counter. The problem here is the old 'list preamble' one that is solved by the new 'list preamble' arguments. However, because those have PassThru set, you can't actually insert the counter inset, and I think that's usually true with PassThru, right? Should we disable PassThru here (people can

Re: List Preamble Arguments

is the old 'list preamble' one that is solved by the new 'list preamble' arguments. However, because those have PassThru set, you can't actually insert the counter inset, and I think that's usually true with PassThru, right? Should we disable PassThru here (people can use ERT if that's what they want

Re: List Preamble Arguments

On 10/13/20 5:15 PM, Richard Kimberly Heck wrote: > Hi, all (but especially Jürgen), > > There have been two cases recently where people have asked about using > the new counter insets to set the value of e.g., the enumi counter. The > problem here is the old 'list preamble' one

List Preamble Arguments

Hi, all (but especially Jürgen), There have been two cases recently where people have asked about using the new counter insets to set the value of e.g., the enumi counter. The problem here is the old 'list preamble' one that is solved by the new 'list preamble' arguments. However, because those

Re: Preamble section patch

Il 28/09/20 22:57, Richard Kimberly Heck ha scritto: > So can you create a file with the new preamble that might cause a problem so > we can see exactly what it is? > > Riki My problem is with the following (pseudo)code, that is present in writeLatex, but not in my code: > // Ch

Re: Preamble section patch

On 9/27/20 12:40 PM, Lorenzo Bertini wrote: >> Can you give more details on what you mean by "far from perfect"? > Yes, sorry! The thing I'm not happy with is that patch makes it so the > HTML preamble gets stored in a new bufferParams docstring, but it > doesn't get check

Re: Preamble section patch

On Sun, Sep 27, 2020 at 06:40:06PM +0200, Lorenzo Bertini wrote: > > Can you give more details on what you mean by "far from perfect"? > Yes, sorry! The thing I'm not happy with is that patch makes it so the HTML > preamble gets stored in a new bufferParams docstring, but it

Re: Preamble section patch

Can you give more details on what you mean by "far from perfect"? Yes, sorry! The thing I'm not happy with is that patch makes it so the HTML preamble gets stored in a new bufferParams docstring, but it doesn't get checked for illegal characters and it's "brutally" printed

Re: Preamble section patch

On Sun, Sep 27, 2020 at 12:40:25PM +0200, Lorenzo Bertini wrote: > Hello list, > sorry for the long delay, I have attached the patch I made to have a > general preamble section. It's short and far from perfect but works. I > followed the git guide on lyx.org scrupulously (i'

Preamble section patch

Hello list, sorry for the long delay, I have attached the patch I made to have a general preamble section. It's short and far from perfect but works. I followed the git guide on lyx.org scrupulously (i'm new to vcs), but let me know if something's amiss. Best regards, Lo From

Re: [Request/idea] Preamble generalization

On 9/21/20 2:22 PM, Lorenzo Bertini wrote: > I managed to get the thing to work through your guidance and shameless > copy-paste: I would have done it the same way: Find all the preambleTE stuff and duplicate it! > let me know if you find any problems. I generalized the > findText method

Re: [Request/idea] Preamble generalization

ole outputting is done. Is there any documentation? Lo From 9914af1583355687e93662ac1019880799228e17 Mon Sep 17 00:00:00 2001 From: Lorenzo Bertini Date: Mon, 21 Sep 2020 20:08:32 +0200 Subject: [PATCH] Preamble section generalization --- src/Buffer.cpp| 7 src/BufferParams.

Re: [Request/idea] Preamble generalization

On 9/19/20 6:36 PM, Lorenzo Bertini wrote: > Sorry for the old bump, but I managed to make a tabbed menu with > "LaTeX" and "HTML" as tabs for the "Preamble" section: > > What I managed to do: > 1) Buffer params received a new variable that can be >

Re: [Request/idea] Preamble generalization

Sorry for the old bump, but I managed to make a tabbed menu with "LaTeX" and "HTML" as tabs for the "Preamble" section: What I managed to do: 1) Buffer params received a new variable that can be written to and read from a LyX file just as old ; 2) "Pream

Re: [Request/idea] Preamble generalization

cut for in ? In this case I think putting them at the same level is confusing, and prevented me from ever needing to look deeper in ; I understand not all users would want to learn this but it's three lines to get a LaTeX or HTML preamble. Ideally there would be a way to keep the generality of the sect

Re: [Request/idea] Preamble generalization

oblems for me. However now I'm > questioning whether the section in document->settings > isn't just a shortcut for in layout>? In this case I think putting them at the same level is > confusing, and prevented me from ever needing to look deeper in layout>; I understand not

Re: [Request/idea] Preamble generalization

ng > copy and paste errors!). Let me know if you have any problems. I'll be > happy to have a look. > > Riki I am probably over thinking, that happens a lot :-), but I think that the preamble should be made generic. There are several file formats that allow a preamble not just l

Re: [Request/idea] Preamble generalization

in ? In this case I think putting them at the same level is confusing, and prevented me from ever needing to look deeper in ; I understand not all users would want to learn this but it's three lines to get a LaTeX or HTML preamble. Ideally there would be a way to keep the generality of the section that howev

Re: [Request/idea] Preamble generalization

and impossible to find by user. If we >>> don't have time to implement this, we could at least give hint >>> into additional manual (I volunteer to copy paste your example unless >>> someone feels itching to implement one of the suggestions mentioned). >>> >

Re: [Request/idea] Preamble generalization

done for the LaTeX preamble. But first I have to fix my compilation and IDE issues. Otherwise it takes too much time. -- Daniel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [Request/idea] Preamble generalization

On 2020-08-14 19:10, Pavel Sanda wrote: On Fri, Aug 14, 2020 at 10:50:55AM -0400, Richard Kimberly Heck wrote: UI-wise, this would probably be better than what we have, but you can already do this with Local Layout. Like this: Format 61 AddToHTMLPreamble h2.section { font-size: 150%;

Re: [Request/idea] Preamble generalization

On Fri, Aug 14, 2020 at 10:50:55AM -0400, Richard Kimberly Heck wrote: > UI-wise, this would probably be better than what we have, but you can > already do this with Local Layout. Like this: > > Format 61 > > AddToHTMLPreamble > > > h2.section { font-size: 150%; font-weight: bold; } > > >

Re: [Request/idea] Preamble generalization

contain the LaTeX preamble, CSS > etc. The main advantages would be: > 1) less "special treatment" given to LaTeX; > 2) more customizability for HTML and XHTML output, which is a > substantial perk of this output that is otherwise lost; > I'm thinki

Re: [Request/idea] Preamble generalization

On 14/8/20 13:06, Lorenzo Bertini wrote: Hello devs, the recent discussion about Lyx being not LaTeX centric and my need to manually edit the CSS in LyXHTML output has got me thinking that the section in the document->settings could be generalized to just and contain the LaTeX preamble,

[Request/idea] Preamble generalization

Hello devs, the recent discussion about Lyx being not LaTeX centric and my need to manually edit the CSS in LyXHTML output has got me thinking that the section in the document->settings could be generalized to just and contain the LaTeX preamble, CSS etc. The main advantages would be: 1) l

Bug in external preamble edit

FYI, I just filed a ticket (#11640 <https://www.lyx.org/trac/ticket/11640>) on a bug in the new preamble external edit feature. For some odd reason, the file path is (tmp/lyx_tmpdir...) is passed correctly to one editor (xed), but the "t" in "tmp" is lopped off

Re: [LyX/master] lyx2lyx: Support conversion of fonts from preamble with extra opts

Am Montag, 15. Juli 2019, 12:23:46 CEST schrieb Jürgen Spitzmüller: > Am Montag, den 15.07.2019, 12:07 +0200 schrieb Kornel Benko: > > Save attached as 2.3.x and reimport. > > Works here! > > Jürgen > OK, don't know what went wrong ... works here too. Thanks, Kornel signature.asc

Re: [LyX/master] lyx2lyx: Support conversion of fonts from preamble with extra opts

Am Montag, den 15.07.2019, 12:07 +0200 schrieb Kornel Benko: > Save attached as 2.3.x and reimport. Works here! Jürgen signature.asc Description: This is a digitally signed message part

Re: [LyX/master] lyx2lyx: Support conversion of fonts from preamble with extra opts

Am Montag, 15. Juli 2019, 12:05:00 CEST schrieb Kornel Benko: > Am Montag, 15. Juli 2019, 11:56:05 CEST schrieb Jürgen Spitzmüller: > > Am Montag, den 15.07.2019, 11:39 +0200 schrieb Kornel Benko: > > > Ouch, you beat me! > > > > Sorry. > > > > Jürgen > > BTW, your commit does not work with

Re: [LyX/master] lyx2lyx: Support conversion of fonts from preamble with extra opts

Am Montag, 15. Juli 2019, 11:56:05 CEST schrieb Jürgen Spitzmüller: > Am Montag, den 15.07.2019, 11:39 +0200 schrieb Kornel Benko: > > Ouch, you beat me! > > Sorry. > > Jürgen BTW, your commit does not work with Cantarell and extra options. Should I investigate? Kornel signature.asc

Re: [LyX/master] lyx2lyx: Support conversion of fonts from preamble with extra opts

Am Montag, den 15.07.2019, 11:39 +0200 schrieb Kornel Benko: > Ouch, you beat me! Sorry. Jürgen signature.asc Description: This is a digitally signed message part

Re: [LyX/master] lyx2lyx: Support conversion of fonts from preamble with extra opts

Am Montag, 15. Juli 2019, 10:24:43 CEST schrieb Juergen Spitzmueller: > commit 989b5b9c9b2d40e7609ab083df06d8d37546c5dd > Author: Juergen Spitzmueller > Date: Mon Jul 15 10:34:19 2019 +0200 > > lyx2lyx: Support conversion of fonts from preamble with extra opts > --- >

Re: Tab stop width in Preamble

On 02.04.2018 21:31, Richard Kimberly Heck wrote: On 04/02/2018 06:08 AM, racoon wrote: On 27.03.2018 11:16, racoon wrote: On 27.03.2018 11:11, racoon wrote: Hi, Could it be that the tab stop width in the preamble is 12 spaces wide? That seems an awful lot to me. Is there a way to change

Re: Tab stop width in Preamble

On 02.04.2018 21:31, Richard Kimberly Heck wrote: On 04/02/2018 06:08 AM, racoon wrote: On 27.03.2018 11:16, racoon wrote: On 27.03.2018 11:11, racoon wrote: Hi, Could it be that the tab stop width in the preamble is 12 spaces wide? That seems an awful lot to me. Is there a way to change

Re: Tab stop width in Preamble

On 04/02/2018 06:08 AM, racoon wrote: > On 27.03.2018 11:16, racoon wrote: >> On 27.03.2018 11:11, racoon wrote: >>> Hi, >>> >>> Could it be that the tab stop width in the preamble is 12 spaces >>> wide? That seems an awful lot to me. Is there a wa

Re: Tab stop width in Preamble

On 27.03.2018 11:16, racoon wrote: On 27.03.2018 11:11, racoon wrote: Hi, Could it be that the tab stop width in the preamble is 12 spaces wide? That seems an awful lot to me. Is there a way to change it something narrower, like 2 spaces? The same applies to ERTs. They have a tab stop of 4

Re: Tab stop width in Preamble

On 27.03.2018 11:11, racoon wrote: Hi, Could it be that the tab stop width in the preamble is 12 spaces wide? That seems an awful lot to me. Is there a way to change it something narrower, like 2 spaces? The same applies to ERTs. They have a tab stop of 4 spaces. Can that be changed to 2

Tab stop width in Preamble

Hi, Could it be that the tab stop width in the preamble is 12 spaces wide? That seems an awful lot to me. Is there a way to change it something narrower, like 2 spaces? Daniel

Re: [LyX/master] Remove unappropriate French style command from preamble

Am Mittwoch, 31. Januar 2018 21:32:57 CET schrieb Jean-Pierre : > Le 31 janvier 2018 6:49:21 PM Jürgen Spitzmüller a écrit : > > Am Mittwoch, den 31.01.2018, 17:52 +0100 schrieb jpc: > >> lib/doc/fr/#EmbeddedObjects.lyx# |48248 > >>

Re: [LyX/master] Remove unappropriate French style command from preamble

Le 31 janvier 2018 6:49:21 PM Jürgen Spitzmüller a écrit : Am Mittwoch, den 31.01.2018, 17:52 +0100 schrieb jpc: lib/doc/fr/#EmbeddedObjects.lyx# |48248 ++ I suppose this was not intended. Of course :-( Sorry, I'm still a bit akward with

Re: [LyX/master] Remove unappropriate French style command from preamble

Am Mittwoch, den 31.01.2018, 17:52 +0100 schrieb jpc: > lib/doc/fr/#EmbeddedObjects.lyx# |48248 > ++ I suppose this was not intended. Jürgen signature.asc Description: This is a digitally signed message part

Re: Suggestion: fixed preamble element for logical markup

On 12/14/2017 01:30 AM, Scott Kostyshak wrote: > On Wed, Dec 13, 2017 at 03:39:38PM +, Paul Johnson wrote: >> Dear LyX-developers. >> >> Happy Holidays to you from Kansas! >> >> Would you consider making the preamble created by LyX more >> "predic

Re: Suggestion: fixed preamble element for logical markup

On Wed, Dec 13, 2017 at 03:39:38PM +, Paul Johnson wrote: > Dear LyX-developers. > > Happy Holidays to you from Kansas! > > Would you consider making the preamble created by LyX more > "predictable" from the settings, and less dependent on the actual > conte

Suggestion: fixed preamble element for logical markup

Dear LyX-developers. Happy Holidays to you from Kansas! Would you consider making the preamble created by LyX more "predictable" from the settings, and less dependent on the actual content in the document? Recently I wished, while using Logical Markup module, that it would insert pre

Re: [LyX/master] natbibapa.module: Do not overwrite preamble.

On 07/02/2017 05:00 AM, Juergen Spitzmueller wrote: > commit 1506d762d6f48973340defa746691f9aa30714b0 > Author: Juergen Spitzmueller <sp...@lyx.org> > Date: Sun Jul 2 10:54:39 2017 +0200 > > natbibapa.module: Do not overwrite preamble. > >

Re: "early preamble"

On 04/15/2017 05:58 AM, Guenter Milde wrote: I would suggest 2 tabs in Document>Settings>User preamble, where the "normal" preamble is the default and the "early" preamble gets a documentation line telling about the specifics. We should think about the right place, tho

"early preamble" (was: [patch] support for fontspec options)

On 2017-04-12, Richard Heck wrote: > On 04/12/2017 06:10 AM, Guenter Milde wrote: ... >>>> ... if there is no added value in a LyX-specific interface, it's >>>> better to keep the "advanced" and "exotic" settings for the user >>>> p

Re: [LyX/master] Docstringify getLongString in general and preamble snippets in particular

Le 18/10/2016 à 19:59, Guillaume Munch a écrit : From what I got from Georg's explanations, there's already a policy which is quite clear: std::string must only contain ASCII. Therefore any code using std::string in UTF-8 must be converted to use docstring instead. That makes much sense, but I

Re: [LyX/master] Docstringify getLongString in general and preamble snippets in particular

Le 18/10/2016 à 09:44, Jean-Marc Lasgouttes a écrit : I agree though that it is always annoying to have to guess what kind of string is needed. I do not think that we implement a clear policy on that. It would be nice to have one, so that we agree on what should be what. From what I got from

Re: [LyX/master] Docstringify getLongString in general and preamble snippets in particular

Le 18/10/2016 à 01:08, Guillaume Munch a écrit : Le 17/10/2016 à 00:35, Guillaume Munch a écrit : commit 1f945177b9628b213c60872df88f2d155c3d6c54 Author: Guillaume Munch <g...@lyx.org> Date: Sun Sep 25 12:37:40 2016 +0200 Docstringify getLongString in general and preamble sn

Re: [LyX/master] Docstringify getLongString in general and preamble snippets in particular

Le 17/10/2016 à 00:35, Guillaume Munch a écrit : commit 1f945177b9628b213c60872df88f2d155c3d6c54 Author: Guillaume Munch <g...@lyx.org> Date: Sun Sep 25 12:37:40 2016 +0200 Docstringify getLongString in general and preamble snippets in particular Prepare ground for TexRow InPr

Re: ukrainean splash has preamble code loading russian babel

On Wed, Sep 07, 2016 at 07:31:43AM +0300, Yuri Chornoivan wrote: > Sure, it can be removed now. > > There was a time when \usepackage[russian,ukrainian]{babel} was necessary due > to some definition duplication in old LaTeX (babel) versions. Now it is not. I would say go ahead then, Günter. >

  1   2   3   4   5   6   7   8   9   >