On Sun, May 04, 2025 at 01:31:22PM +0200, Scott Kostyshak wrote:
> On Sun, May 04, 2025 at 01:08:02PM +0200, Kornel Benko wrote:
> > Am Sun, 4 May 2025 12:55:46 +0200
> > schrieb Scott Kostyshak :
> >
> > > On Sun, May 04, 2025 at 12:35:01PM +0200, Kornel Benko wrote:
> > > > Am Sun, 04 May 2025 1
On Sun, May 04, 2025 at 01:08:02PM +0200, Kornel Benko wrote:
> Am Sun, 4 May 2025 12:55:46 +0200
> schrieb Scott Kostyshak :
>
> > On Sun, May 04, 2025 at 12:35:01PM +0200, Kornel Benko wrote:
> > > Am Sun, 04 May 2025 12:14:48 +0200
> > > schrieb "Jürgen Spitzmüller" :
> > >
> > > > Am Sonnta
Am Sun, 4 May 2025 12:55:46 +0200
schrieb Scott Kostyshak :
> On Sun, May 04, 2025 at 12:35:01PM +0200, Kornel Benko wrote:
> > Am Sun, 04 May 2025 12:14:48 +0200
> > schrieb "Jürgen Spitzmüller" :
> >
> > > Am Sonntag, dem 04.05.2025 um 11:42 +0200 schrieb Jürgen Spitzmüller:
> > > > We migh
On Sun, May 04, 2025 at 12:35:01PM +0200, Kornel Benko wrote:
> Am Sun, 04 May 2025 12:14:48 +0200
> schrieb "Jürgen Spitzmüller" :
>
> > Am Sonntag, dem 04.05.2025 um 11:42 +0200 schrieb Jürgen Spitzmüller:
> > > We might want to do something to fix the problem this file documents,
> > > though.
Am Sun, 04 May 2025 12:14:48 +0200
schrieb "Jürgen Spitzmüller" :
> Am Sonntag, dem 04.05.2025 um 11:42 +0200 schrieb Jürgen Spitzmüller:
> > We might want to do something to fix the problem this file documents,
> > though.
>
> This is done now. This file is now imported properly (so it does no
Am Sonntag, dem 04.05.2025 um 11:58 +0200 schrieb Kornel Benko:
> The new imported pdf starts numbering inside a section (1.1., 1.2.,
> 1.3.) while the previous shows (1., 2., 3.)
Which is correct! Cf. the tex file.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
-
Am Sonntag, dem 04.05.2025 um 11:42 +0200 schrieb Jürgen Spitzmüller:
> We might want to do something to fix the problem this file documents,
> though.
This is done now. This file is now imported properly (so it does no
longer create a LaTeX error).
Now of course the test result differs. The PDF
On Sun, May 04, 2025 at 11:58:48AM +0200, Kornel Benko wrote:
> Am Sun, 04 May 2025 11:42:00 +0200
> schrieb "Jürgen Spitzmüller" :
>
> > Am Samstag, dem 03.05.2025 um 21:24 +0200 schrieb Scott Kostyshak:
> > > Starting with this commit, the following ctest fails:
> > >
> > > BATCH_AMS-import
>
Am Sun, 04 May 2025 11:42:00 +0200
schrieb "Jürgen Spitzmüller" :
> Am Samstag, dem 03.05.2025 um 21:24 +0200 schrieb Scott Kostyshak:
> > Starting with this commit, the following ctest fails:
> >
> > BATCH_AMS-import
> >
> > I don't know much about these BATCH tests, but from what I
> > under
Am Samstag, dem 03.05.2025 um 21:24 +0200 schrieb Scott Kostyshak:
> Starting with this commit, the following ctest fails:
>
> BATCH_AMS-import
>
> I don't know much about these BATCH tests, but from what I
> understand, it has to do with the file development/batchtests/ams-
> import.tex. If yo
On Fri, Apr 25, 2025 at 02:28:38PM +, Juergen Spitzmueller wrote:
> commit 7d5952201dfdcc464bf86a5b2d8a4f189e11bdf6
> Author: Juergen Spitzmueller
> Date: Fri Apr 25 16:23:50 2025 +0200
>
> Integrate theorem definition in layout
>
> Rather than using
Am Freitag, dem 25.04.2025 um 15:04 -0400 schrieb Richard Kimberly
Heck:
> This is just to encourage those of us who use theorems and the like
> to
> test this. I've looked through the code, and (no surprise here) it
> looks
> right, but this is probably delicate. I'll test it myself this
> weeke
e:
commit 7d5952201dfdcc464bf86a5b2d8a4f189e11bdf6
Author: Juergen Spitzmueller
Date: Fri Apr 25 16:23:50 2025 +0200
Integrate theorem definition in layout
Rather than using verbatim \newtheorem definitions in the Preamble
tag, introduce dedicated layout tags from which the
Am Donnerstag, dem 07.11.2024 um 12:05 +0100 schrieb Kornel Benko:
> I see only 'Qt::TextFormat::PlainText' in
> src/frontends/qt/ui/AboutUi.ui.
Thanks, I'll fix those.
(the others have been fixed earlier, but of course they might
reappear).
--
Jürgen
signature.asc
Description: This is a digi
Am Donnerstag, dem 07.11.2024 um 14:20 +0100 schrieb Kornel Benko:
> Added test "check_Qt_ui_Constants" at 695b2f48 to check for such
> suspected values.
Great, thanks.
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.o
Am Thu, 07 Nov 2024 12:36:35 +0100
schrieb "Jürgen Spitzmüller" :
> Am Donnerstag, dem 07.11.2024 um 12:05 +0100 schrieb Kornel Benko:
> > I see only 'Qt::TextFormat::PlainText' in
> > src/frontends/qt/ui/AboutUi.ui.
>
> Thanks, I'll fix those.
>
> (the others have been fixed earlier, but of c
Am Mon, 04 Nov 2024 12:15:25 +0100
schrieb "Jürgen Spitzmüller" :
> Am Montag, dem 04.11.2024 um 12:04 +0100 schrieb Pavel Sanda:
> > We could easily automatize check for this in our tests.
> >
> > I can add it if you write some list of string we should
> > grep for in .ui files...
>
> For now
This fits perfectly for any script returning an exit value. KornelAm 05.11.2024 16:12 schrieb Pavel Sanda :On Mon, Nov 04, 2024 at 12:15:25PM +0100, Jürgen Spitzmüller wrote:
> Am Montag, dem 04.11.2024 um 12:04 +0100 schrieb Pavel Sanda:
> > We could easily automatize check for this in our te
On Mon, Nov 04, 2024 at 12:15:25PM +0100, Jürgen Spitzmüller wrote:
> Am Montag, dem 04.11.2024 um 12:04 +0100 schrieb Pavel Sanda:
> > We could easily automatize check for this in our tests.
> >
> > I can add it if you write some list of string we should
> > grep for in .ui files...
>
> For now
Am Montag, dem 04.11.2024 um 12:04 +0100 schrieb Pavel Sanda:
> We could easily automatize check for this in our tests.
>
> I can add it if you write some list of string we should
> grep for in .ui files...
For now I saw:
Qt::Orientation:: => Qt::
QSizePolicy::Policy:: => QSizePolicy::
QLayout::
On Mon, Nov 04, 2024 at 07:54:50AM +0100, Jürgen Spitzmüller wrote:
> Am Sonntag, dem 03.11.2024 um 20:03 +0100 schrieb Pavel Sanda:
> > I see this, but it seems to compile just fine on old system (Qt
> > 5.15.8).
>
> Yes it does, but it does not work (neither on old nor on new systems)
> as it is
Am Sonntag, dem 03.11.2024 um 20:03 +0100 schrieb Pavel Sanda:
> I see this, but it seems to compile just fine on old system (Qt
> 5.15.8).
Yes it does, but it does not work (neither on old nor on new systems)
as it is invalid. Spacers using this, for instance, are simply ignored.
--
Jürgen
--
On Sun, Nov 03, 2024 at 05:48:12AM +0100, Jürgen Spitzmüller wrote:
> You can see how it inserts wrong namespaces such as
> Qt::Orientation::Vertical instead of Qt::Vertical (which is then not
> recognized).
I see this, but it seems to compile just fine on old system (Qt 5.15.8).
Pavel
--
lyx-de
Am Sonntag, dem 03.11.2024 um 05:48 +0100 schrieb Jürgen Spitzmüller:
> I currently correct the UI files manually in an editor after having
> used designer. Strangely enough, I also did not find any report about
> it.
I grep'ed the remaining cases in master and stable and fixed them.
--
Jürgen
-
Am Samstag, dem 02.11.2024 um 19:22 +0100 schrieb Pavel Sanda:
> What versions are safe in this regard?
I don't know when it started. It certainly is a problem in recent
versions.
You can see how it inserts wrong namespaces such as
Qt::Orientation::Vertical instead of Qt::Vertical (which is then
>
> > Fix AboutLyX layout
> >
> > * remove wrong (sub)namespaces. This are inserted by newer
> > versions of
> > designer, although they are wrong
> > * add vertical spacer
> > * make horizontal spacer expand
>
> Should
On 11/2/24 9:44 AM, Jürgen Spitzmüller wrote:
Am Samstag, dem 02.11.2024 um 13:40 + schrieb Juergen Spitzmueller:
commit 11cbc3c4a765f93268a662846d7082b089b3782b
Author: Juergen Spitzmueller
Date: Sat Nov 2 14:33:28 2024 +0100
Fix AboutLyX layout
* remove wrong (sub
Am Samstag, dem 02.11.2024 um 13:40 + schrieb Juergen Spitzmueller:
> commit 11cbc3c4a765f93268a662846d7082b089b3782b
> Author: Juergen Spitzmueller
> Date: Sat Nov 2 14:33:28 2024 +0100
>
> Fix AboutLyX layout
>
> * remove wrong (sub)namespaces. This
Le 16/10/2024 à 15:19, Jean-Marc Lasgouttes a écrit :
commit f4a3f4f29b2dbf32043d3fafdaad1394cc9e8ed3
Author: Jean-Marc Lasgouttes
Date: Mon Sep 23 19:15:20 2024 +0200
Give a layout name to math HulInset
This makes it accessible to inset-forall.
Hi Riki,
This is candidate
.inc ~/tmp/inbox/lyx/dbg.out | wc -l
435
It does not make any sense that this layout file is converted 435 times
in the same session. Once it is enough, and all the other times that it
is called it could be using the cached values.
--
José Abílio
--
lyx-devel mailing list
lyx-deve
Le 02/06/2024 à 19:37, Richard Kimberly Heck a écrit :
Right. I think -dbg any loads absolutely every layout file it can find.
If the layout formats are not up to date, that is going to take even
longer than it otherwise would.
I don't think caching previous loads is possible. Some of
.
It seems that there is no caching of the previous conversions and so
for each class all included files are converted over and over again.
Right. I think -dbg any loads absolutely every layout file it can find.
If the layout formats are not up to date, that is going to take even
longer th
On Sun, 2024-06-02 at 12:56 -0400, Richard Kimberly Heck wrote:
> I do not see it here. There's a lot of debug output, as you would
> expect, but it eventually stops.
The resulting file is 1.7 MB and layout2layout is called 2176 before we
finally had window.
It seems that there is no caching of
On Sun, 2024-06-02 at 12:56 -0400, Richard Kimberly Heck wrote:
> I do not see it here. There's a lot of debug output, as you would
> expect, but it eventually stops.
$ src/lyx -dbg tclass > /dev/null 2>&1
I had to wait for more than a minute.
I will redirect the output to see what is going on.
On 6/2/24 12:45, José Matos wrote:
On Sun, 2024-06-02 at 17:49 +0200, Jürgen Spitzmüller wrote:
The following is causing this:
if (lyxerr.debugging(Debug::TCLASS)) {
// only system layout files are loaded here so no
// buffer path is needed.
tmpl->l
On Sun, 2024-06-02 at 17:49 +0200, Jürgen Spitzmüller wrote:
> The following is causing this:
>
> if (lyxerr.debugging(Debug::TCLASS)) {
> // only system layout files are loaded here so no
> // buffer path is needed.
> tmpl->load();
> }
>
> Layou
> > Did we forget to update layout format number with some recent
> > feature?
>
> I stepped the format number at 2a7ec054be00f, but I don't see
> anything missing there.
The following is causing this:
if (lyxerr.debugging(Debug::TCLASS)) {
// only system layout
Am Sonntag, dem 02.06.2024 um 16:28 +0200 schrieb Pavel Sanda:
> ./lyx -dbg any
> ends up in infinite layout2layout conversion loop (strangely it does
> not when running without -dbg).
> Did we forget to update layout format number with some recent
> feature?
I stepped the f
Hi,
./lyx -dbg any
ends up in infinite layout2layout conversion loop (strangely it does not when
running without -dbg).
Did we forget to update layout format number with some recent feature?
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Sonntag, dem 12.05.2024 um 19:04 +0200 schrieb Jürgen Spitzmüller:
> the documentation part manually later.
Done now. I have pasted the new English paragraph in a note to those
translated docs that already had the old version translated.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.l
Am Sonntag, dem 12.05.2024 um 12:39 -0400 schrieb Richard Kimberly
Heck:
> Since it's a regression, I think you should go ahead.
Thanks, I pulled the two code commits and do the documentation part
manually later.
> I assume it is otherwise safe?
Yes.
--
Jürgen
--
lyx-devel mailing list
lyx-d
On 5/12/24 02:11, Jürgen Spitzmüller wrote:
Am Sonntag, dem 12.05.2024 um 05:53 + schrieb Juergen Spitzmueller:
commit 207eaeee9071cb828a2ab7f4680f8ff92e379af8
Author: Juergen Spitzmueller
Date: Sun May 12 07:52:16 2024 +0200
Introduce NeedCProtect -1 layout option
It
Am Sonntag, dem 12.05.2024 um 05:53 + schrieb Juergen Spitzmueller:
> commit 207eaeee9071cb828a2ab7f4680f8ff92e379af8
> Author: Juergen Spitzmueller
> Date: Sun May 12 07:52:16 2024 +0200
>
> Introduce NeedCProtect -1 layout option
>
> It turns out beamer
On 4/8/24 18:57, Scott Kostyshak wrote:
If we have a UTF8 character in the user preamble, LyX gives a very
user-friendly warning if the document encoding is not UTF8.
However, if the same situation happens for the local layout (or in a
module), I get a SIGSEGV when compiling.
To reproduce
If we have a UTF8 character in the user preamble, LyX gives a very
user-friendly warning if the document encoding is not UTF8.
However, if the same situation happens for the local layout (or in a
module), I get a SIGSEGV when compiling.
To reproduce, open the attached document and compile to PDF
On 4/7/24 08:39, Lorenzo Bertini wrote:
Just out of curiosity I've tried converting a LyX document to YAML and
XML to see how they would look.
I spent some time once working on an XML file format, thinking I could
use some of the machinery developed for XHTML output, which is now even
more ro
e
placement document
alignment document
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\begin_inset Graphics
filename empty.png
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
Example image
\end_layout
\end_
On Thu, 2024-03-28 at 13:00 +0100, Thibaut Cuvelier wrote:
> All of these formats are rather well supported and far from shiny new
> things (I think all of them have at least a decade of existence).
>
> Regarding validation: XML Schema has many offsprings, such as JSON
> Schema (https://json-sche
On Thu, Mar 28, 2024 at 12:49:14PM +0100, Lorenzo Bertini wrote:
> I am proposing this because I've had people tell me layouts
> are "advanced", and one of the roadblocks to using LyX. Having easy
> tools to edit them would help.
Another thing to consider is how to support home-written modules
whi
On Thu, Mar 28, 2024 at 12:40:10PM +0100, Lorenzo Bertini wrote:
> - TOML:
> . pros: very easy to read and write, even for humans
> . cons: not widespread, distant from .layout
> - YAML:
> . pros: very easy to read and write, very close to .layout
> . cons: indentation
take user effort too, to adapt to the new format
> (this can be greatly mitigated by which format is chosen)
>
> * The transition plan:
> The new format is introduced *alongside* the old format. The LyX
> version that brings the format will have all layouts converted, but
> wil
the new format that maps a file to a
> LyX's params
> - write a converter from the old format to the new one
> - convert all the files to the new formats and test them
>
> Here is some info I dug up regarding configuration formats. For pros
> and cons I tried to limit
o I dug up regarding configuration formats. For pros
and cons I tried to limit them to one single aspect where they excel
or fail
- JSON:
. pros: most widely supported
. cons: not concise or readable, very distant from .layout
- TOML:
. pros: very easy to read and write, even for humans
. cons
On Wed, 2024-03-27 at 11:02 -0400, Scott Kostyshak wrote:
> Cool idea, Lorenzo! There have been some discussions in the past on
> using standard formats, even for the .lyx file itself. I can see the
> advantages of that but I don't know what the cost of converting to
> them
> is.
>
> Scott
Typica
On Wed, Mar 20, 2024 at 09:59:04AM +0100, Lorenzo Bertini wrote:
> Dear devs,
> I don't know if this has been discussed before. Lyx uses it's own
> format .layout (or .module), with it's own parser. However, the same
> information can be easily saved stored in another
Dear devs,
I don't know if this has been discussed before. Lyx uses it's own
format .layout (or .module), with it's own parser. However, the same
information can be easily saved stored in another format. I asked a
chatbot to convert "amsbook.layout" to an hypothetical &qu
Am Freitag, dem 15.09.2023 um 16:23 +0200 schrieb Jürgen Spitzmüller:
> Am Freitag, dem 15.09.2023 um 15:41 +0200 schrieb Thibaut Cuvelier:
> > Your patch looks fine to me.
> >
> > It looks cumbersome, especially if we need to do that several
> > times;
> > maybe we could have a method at the inse
Le 15/09/2023 à 16:23, Jürgen Spitzmüller a écrit :
(Wasn't this bug caught at some point by a static analyser? It seems
to be a too common error in C++ for it to slip through.)
Apparently not.
Coverity scan only tags this if in some other places of the code there
is a test for a null pointe
Am Freitag, dem 15.09.2023 um 15:41 +0200 schrieb Thibaut Cuvelier:
> Your patch looks fine to me.
>
> It looks cumbersome, especially if we need to do that several times;
> maybe we could have a method at the inset level, say
> getLocalFontOrDefault(const OutputParams&), to return either
> Output
On Fri, 15 Sept 2023 at 11:36, Jürgen Spitzmüller wrote:
> Am Freitag, dem 15.09.2023 um 10:45 +0200 schrieb Léo de Souza:
> > 1. Create new document: File > New
> > 2. Insert label: Insert > Label...
> > 3. On a new line, switch layout to "Labeling"
Am Freitag, dem 15.09.2023 um 10:45 +0200 schrieb Léo de Souza:
> 1. Create new document: File > New
> 2. Insert label: Insert > Label...
> 3. On a new line, switch layout to "Labeling" or "Description"
> 4. Insert cross-reference: Insert > Cross-Reference
Can repeat on Mac Ventura 13.5.2.
/Anders
> On 15 Sep 2023, at 10:45, Léo de Souza wrote:
>
> Hello,
>
> I would like to report that LyX crashes with SIGSEGV when copying a cross
> reference from a "labeled list" or "description" layout on LyX 2.4.0 bet
Hello,
I would like to report that LyX crashes with SIGSEGV when copying a cross
reference from a "labeled list" or "description" layout on LyX 2.4.0 beta 5.
Environment:
I compiled LyX 2.4.0 beta 5 on Ubuntu 22.04 with Qt6 enabled and my Tex Live
install is up to date.
Am Freitag, dem 12.05.2023 um 18:57 +0200 schrieb Pavel Sanda:
> Please go ahead, you are better UI designer anyway.
I solved it differently and kept the two rows.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Fri, May 12, 2023 at 06:07:53PM +0200, Jürgen Spitzmüller wrote:
> Am Freitag, dem 12.05.2023 um 12:23 +0200 schrieb Pavel Sanda:
> > I am open to try it. It's just the designer which frustrated me to
> > the extent
> > that I abandoned further experiments and approached it with vim :)
>
> I c
Am Freitag, dem 12.05.2023 um 12:23 +0200 schrieb Pavel Sanda:
> I am open to try it. It's just the designer which frustrated me to
> the extent
> that I abandoned further experiments and approached it with vim :)
I can try if I have more luck, if you wish.
--
Jürgen
--
lyx-devel mailing list
> > file correctly and it's impossible to move unicodeEncodingCO.
> > When breaking layout this CO is mysteriously deleted.
> >
> > Finally I gave up and simply edited file in vim to get COs to the
> > new row.
>
> Is it too long also if we put the com
This patch moves them to separate line.
>
> Beware, touching this panel is headache.
> Qt Designer (5.15.2) does not know even how to load this ui
> file correctly and it's impossible to move unicodeEncodingCO.
> When breaking layout this CO is mysteriou
On 03/01/23 18:50, Richard Kimberly Heck wrote:
On 1/3/23 11:49, Lorenzo Bertini wrote:
Hi,
I hope you all had wonderful holidays. I'm doing some tests with local
layouts, and I was wondering what is the modality with which a local
layout overrides the default: does it completely eras
On 1/3/23 11:49, Lorenzo Bertini wrote:
Hi,
I hope you all had wonderful holidays. I'm doing some tests with local
layouts, and I was wondering what is the modality with which a local
layout overrides the default: does it completely erase the latter and
uses your edits, or does it ove
Hi,
I hope you all had wonderful holidays. I'm doing some tests with local
layouts, and I was wondering what is the modality with which a local
layout overrides the default: does it completely erase the latter and
uses your edits, or does it override only the attributes you've modif
From 366f8159fe6b496f2ac39f5e745d5be9435a6609 Mon Sep 17 00:00:00 2001
From: John R Hudson
Date: Fri, 30 Dec 2022 20:01:21 +
Subject: [PATCH] Insert more detail about page layout, Custom Class options
KOMA-Script options and using the book document class in the KOMA-Script
section of
Committed.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
From 78dc01329b438cda63d0dc61a71e102b2f4e4e9f Mon Sep 17 00:00:00 2001
From: John R Hudson
Date: Wed, 28 Dec 2022 14:11:07 +
Subject: [PATCH] Insert entries for Custom Footer/Header Text and Landscape
Document Mode and update the existing entry for Multiple Columns to match the
new layout
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 th
;> So if you think this is really done, go ahead. If you're not sure, then
>> let's wait.
>>
> I don't know what I could add or remove. The tests pass and I manually
> checked that the new behaviour is the expected one.
>
>> I'm attaching a new ve
ove. The tests pass and I manually
checked that the new behaviour is the expected one.
I'm attaching a new version of the patch with the updated
layout2layout script (including a change for layout version 98
that was skipped, if I understand correctly). There is also a
nd I manually
checked that the new behaviour is the expected one.
> I'm attaching a new version of the patch with the updated layout2layout
> script (including a change for layout version 98 that was skipped, if I
> understand correctly). There is also a second patch that updates the
them being mature yet.
So if you think this is really done, go ahead. If you're not sure, then
let's wait.
I'm attaching a new version of the patch with the updated
layout2layout script (including a change for layout version 98 that
was skipped, if I understand correctly). The
On 12/26/22 16:57, Scott Kostyshak wrote:
I'm fine with whatever Riki prefers since they're handling the beta 2.
I am planning to do the tarball tomorrow, so I guess the question is
whether these changes can be *completed* by then. Since they don't
affect really core code, I'm not too worried
On Mon, Dec 26, 2022 at 01:51:11AM +0100, Thibaut Cuvelier wrote:
> On Sat, 24 Dec 2022 at 03:45, Scott Kostyshak wrote:
>
> > On Thu, Dec 22, 2022 at 04:45:52AM +0100, Thibaut Cuvelier wrote:
> > > Dear list,
> > >
> > > To solve https://www.lyx.org/t
Am Mon, 26 Dec 2022 01:51:11 +0100
schrieb Thibaut Cuvelier :
> On Sat, 24 Dec 2022 at 03:45, Scott Kostyshak wrote:
>
> > On Thu, Dec 22, 2022 at 04:45:52AM +0100, Thibaut Cuvelier wrote:
> > > Dear list,
> > >
> > > To solve https://www.lyx.org/t
Le 22/12/2022 à 04:45, Thibaut Cuvelier a écrit :
Dear list,
To solve https://www.lyx.org/trac/ticket/12612
<https://www.lyx.org/trac/ticket/12612>, I needed a new layout parameter
for DocBook to generate some content based on paragraph labels. It draws
heavily from LyXHTM
On Thu, Dec 22, 2022 at 04:45:52AM +0100, Thibaut Cuvelier wrote:
> Dear list,
>
> To solve https://www.lyx.org/trac/ticket/12612, I needed a new layout
> parameter for DocBook to generate some content based on paragraph labels.
> It draws heavily from LyXHTML code: mak
Dear list,
To solve https://www.lyx.org/trac/ticket/12612, I needed a new layout
parameter for DocBook to generate some content based on paragraph labels.
It draws heavily from LyXHTML code: makeEnvironment in output_xhtml.cpp,
case on environments, label generation (currently, lines 499 to 511
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
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
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 ed
On Wed, Nov 23, 2022 at 03:20:59PM -0500, Richard Kimberly Heck wrote:
> On 11/23/22 12:57, Scott Kostyshak wrote:
> > In my Beamer document, if I want to insert a Block layout, I type
> > Alt + p, space, and then type "Block". This gives three results:
> > "Blo
On 11/23/22 12:57, Scott Kostyshak wrote:
In my Beamer document, if I want to insert a Block layout, I type
Alt + p, space, and then type "Block". This gives three results:
"Block", "ExampleBlock", and "AlertBlock". "AlertBlock" is highlighted,
In my Beamer document, if I want to insert a Block layout, I type
Alt + p, space, and then type "Block". This gives three results:
"Block", "ExampleBlock", and "AlertBlock". "AlertBlock" is highlighted,
so I press to get to "Block
also every time I come across something like this, I wonder
> > > > if we
> > > > can generalize the process of converting a new layout to ERT for
> > > > older formats. i.e., I just want to put a one-liner with
> > > > "alertenv",
> > >
> > can generalize the process of converting a new layout to ERT for
> > > older formats. i.e., I just want to put a one-liner with
> > > "alertenv",
> > > and I want lyx2lyx to talk to LyX and say "hey you're good at
> > > outputting
On Sun, Nov 06, 2022 at 03:46:50PM +, José Matos wrote:
> On Sun, 2022-11-06 at 10:20 -0500, Scott Kostyshak wrote:
> > And also every time I come across something like this, I wonder if we
> > can generalize the process of converting a new layout to ERT for
> > older
On Sun, 2022-11-06 at 10:20 -0500, Scott Kostyshak wrote:
> And also every time I come across something like this, I wonder if we
> can generalize the process of converting a new layout to ERT for
> older formats. i.e., I just want to put a one-liner with "alertenv",
> and
to reversion, right?
> The conversion code should be empty.
Yes, the only issue is that I make file format changes rarely enough
that I completely forget the process :)
And also every time I come across something like this, I wonder if we
can generalize the process of converting a new layout to
On Sat, 2022-11-05 at 12:49 -0400, Scott Kostyshak wrote:
> Thanks, I'll try to do the lyx2lyx stuff and fileformat for this when
> I can.
>
> Scott
Essentially this is only relevant to reversion, right?
The conversion code should be empty.
Best regards,
--
José Abílio
--
lyx-devel mailing lis
On Wed, Oct 26, 2022 at 07:13:30AM +0200, Jürgen Spitzmüller wrote:
> Am Dienstag, dem 25.10.2022 um 21:15 -0400 schrieb Scott Kostyshak:
> > Is this something you think I can do for 2.4.0 or should I hold off?
> > I forget what the current status is.
>
> The problem is nobody knows that. Personal
Am Dienstag, dem 25.10.2022 um 21:15 -0400 schrieb Scott Kostyshak:
> Is this something you think I can do for 2.4.0 or should I hold off?
> I forget what the current status is.
The problem is nobody knows that. Personally I am trying to hold back
all new features. I do not find adding a few style
On Tue, Oct 25, 2022 at 08:16:15AM +0200, Jürgen Spitzmüller wrote:
> Am Sonntag, dem 23.10.2022 um 12:03 -0400 schrieb Scott Kostyshak:
> > Can I add a layout for alertenv? And similarly, for other envs (I
> > haven't checked yet which other ones we don't cover yet)
1 - 100 of 2976 matches
Mail list logo
