On Mon, Dec 02, 2024 at 04:05:26PM +0100, Jean-Marc Lasgouttes wrote:
> Le 01/12/2024 à 11:12, Scott Kostyshak a écrit :
> > A bisect led me here. I was trying to reproduce an issue that Andrew
> > reported, but I think it is actually a different issue. I attach
> > Andrew's example file.
> >
> >
Le 02/12/2024 à 18:22, Scott Kostyshak a écrit :
I can reproduce, but not necessarily understand what happens. Can you create
a ticket please?
Opened here:
https://www.lyx.org/trac/ticket/13128
Thanks Scott!
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/ma
Le 01/12/2024 à 11:12, Scott Kostyshak a écrit :
A bisect led me here. I was trying to reproduce an issue that Andrew
reported, but I think it is actually a different issue. I attach
Andrew's example file.
Recipe:
1. Enable preview in preferences.
2. Click on the math equation row 1.
3. Click s
On Fri, Apr 05, 2024 at 01:58:16PM +, Jean-Marc Lasgouttes wrote:
> commit 5e8578837fea0321998eac04222102986261666d
> Author: Jean-Marc Lasgouttes
> Date: Mon Nov 27 15:13:56 2023 +0100
>
> Avoid some full metrics computations related to math previews
>
>
Am Thu, 10 Oct 2024 16:00:24 +0200
schrieb "Jürgen Spitzmüller" :
> Am Donnerstag, dem 10.10.2024 um 16:06 +0200 schrieb Kornel Benko:
> > https://www.brailleauthority.org/sizespacingofbraille/index.html
>
> https://www.brailleauthority.org/size-and-spacing-braille-characters
>
commit 1c10af9
Am Donnerstag, dem 10.10.2024 um 16:06 +0200 schrieb Kornel Benko:
> http://www.xmarks.com/site/shelob.ce.ttu.edu/daves/lpfaq/faq.html
Maybe
http://literateprogramming.com/lpfaq.pdf
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-deve
Am Donnerstag, dem 10.10.2024 um 16:06 +0200 schrieb Kornel Benko:
> http://public.lanl.gov/kmh/spie/
If I access this site, I am forwarded to
https://kmh-lanl.hansonhub.com/spie/
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@
Am Donnerstag, dem 10.10.2024 um 16:06 +0200 schrieb Kornel Benko:
> https://www.brailleauthority.org/sizespacingofbraille/index.html
https://www.brailleauthority.org/size-and-spacing-braille-characters
--
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel
> > Date: Mon Oct 7 12:19:28 2024 +0200
> > >
> > > Corrected some used URL's in our lyx files
> >
> > I assume this is also needed in stable? If so, please go ahead.
> >
> > Riki
> >
> >
>
> Done at 9cfa
Am Mon, 7 Oct 2024 10:39:20 -0400
schrieb Richard Kimberly Heck :
> On 10/7/24 6:13 AM, Kornel Benko wrote:
> > commit c0ee28a7c9d4b47b68f02d6cdb4205a29fbb6742
> > Author: Kornel Benko
> > Date: Mon Oct 7 12:19:28 2024 +0200
> >
> > Corrected some use
On 10/7/24 6:13 AM, Kornel Benko wrote:
commit c0ee28a7c9d4b47b68f02d6cdb4205a29fbb6742
Author: Kornel Benko
Date: Mon Oct 7 12:19:28 2024 +0200
Corrected some used URL's in our lyx files
I assume this is also needed in stable? If so, please go ahead.
Riki
--
lyx-devel mailing
Le 10/07/2024 à 17:17, Richard Kimberly Heck a écrit :
Riki, would that be OK?
Yes. Should get plenty of testing before release.
Thanks, I did that.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On 7/10/24 9:19 AM, Jean-Marc Lasgouttes wrote:
Hello,
The following patches are a backport of the recent patch series which
added the possibility of knowing which paragraph metrics have a
computed position and then fixed situations where the assertion added
in this first patch was triggered.
Lasgouttes
Date: Fri, 17 May 2024 15:42:08 +0200
Subject: [PATCH 1/4] Handle metrics of not visible paragraphs
The code is not ready for situations where some paragraphs that are
not visible have metrics available.
In PararagraphMetrics, some methods are added to be able to handle the
fact that
On Mon, Apr 08, 2024 at 10:41:43AM GMT, Jean-Marc Lasgouttes wrote:
> Le 08/04/2024 à 10:20, pdv a écrit :
> > Tor Arne Vestbø posted a qt-patch solving this issue.
> > See: https://bugreports.qt.io/browse/QTBUG-123848
>
> Great job Patrick! Now we just have to wait for it to be available.
+1 tha
Le 08/04/2024 à 10:20, pdv a écrit :
Tor Arne Vestbø posted a qt-patch solving this issue.
See: https://bugreports.qt.io/browse/QTBUG-123848
Great job Patrick! Now we just have to wait for it to be available.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman
On 29/03/2024 22:40, pdv wrote:
On 29/03/2024 11:31, Jean-Marc Lasgouttes wrote:
Le 28/03/2024 à 23:04, pdv a écrit :
I submitted the following bug report
https://bugreports.qt.io/browse/QTBUG-123848
pdv
Hi Patrick,
Thanks for doing that!
Frankly I don't use shortcuts very often and I neve
On 29/03/2024 11:31, Jean-Marc Lasgouttes wrote:
Le 28/03/2024 à 23:04, pdv a écrit :
I submitted the following bug report
https://bugreports.qt.io/browse/QTBUG-123848
pdv
Hi Patrick,
Thanks for doing that!
Frankly I don't use shortcuts very often and I never use asian
languages, but I can
Le 28/03/2024 à 23:04, pdv a écrit :
I submitted the following bug report
https://bugreports.qt.io/browse/QTBUG-123848
pdv
Hi Patrick,
Thanks for doing that! An alternative idea I had was be to install a
global event filter at GuiApplication level that would detect and handle
shortcut. Doe
I submitted the following bug report
https://bugreports.qt.io/browse/QTBUG-123848
pdv
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
levant
> qt-forum.
>
> pdv
Hi Patrick,
I’d be more than happy if you’ll do this.
Thank you.
Stephan
>
>
> Since qt commit https://github.com/qt/qtbase/commit/9e1875483ceaf90 the
> handling of some short cuts by LyX (https://www.lyx.org/) on macos doe
tbase/commit/9e1875483ceaf90 the
handling of some short cuts by LyX (https://www.lyx.org/) on macos
doesn't work anymore.
In that commit the default handling of key events was reversed. Before
this commit key events were send for all key presses unless they were
handled by the "in
> I sent new login privately. P
It worked, thanks!
I'm going to report the bugs there so you got them thrice :)
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Wed, Mar 13, 2024 at 09:19:45PM -0300, Carlos Pita wrote:
> I've been trying to report a couple of bugs to your Trac (which I
> haven't used for ages) but to no avail. I've a password although it
> doesn't seem to be the right one, so I tried to reset my password many
> times but the email never
Hi guys,
I've been trying to report a couple of bugs to your Trac (which I
haven't used for ages) but to no avail. I've a password although it
doesn't seem to be the right one, so I tried to reset my password many
times but the email never arrived to my inbox (nor spam folder). And
registration is
Thanks for looking at my patch!
I'm happy to add a simple "Refresh" button to the "Document Settings -> Module"
window if you think this would be a good idea?
— Isaac Oscar Gariano
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
something for sure.
> >
> > Let's stick with point 4.
> >
> > By *needed* you mean that we have e.g. some specific feature requiring it
> > for
> > proper typesetting (I agree with that) or that we actively use the
> > information
> > gathered by con
On Wed, 11 Oct 2023 at 11:03, Pavel Sanda wrote:
> On Tue, Oct 10, 2023 at 02:38:01PM +0200, Jürgen Spitzmüller wrote:
> >> 4) *lot* of latex packages
> > All we query is needed for something for sure.
>
> Let's stick with point 4.
>
> By *needed* you mean that
On Tue, Oct 10, 2023 at 02:38:01PM +0200, Jürgen Spitzmüller wrote:
>> 4) *lot* of latex packages
> All we query is needed for something for sure.
Let's stick with point 4.
By *needed* you mean that we have e.g. some specific feature requiring it for
proper typesetting (I agree
Am Dienstag, dem 10.10.2023 um 14:27 +0200 schrieb Pavel Sanda:
> As I see we do:
> 2) Indexing cls/sty/bst/bib/bbx/cbx (do we need those for something?)
Yes, (bib)latex settings for bst/bib/bbx/cbx. Package/class
availability for the others.
> 6) checking fonts (do we actually use those for sett
27;t getting
rid of some of these calls get us some speed up?
As I see we do:
1) program checks (we need those for enabling proper convertors etc.)
2) Indexing cls/sty/bst/bib/bbx/cbx (do we need those for something?)
3) Modules/citeengines/templates (we need those for setting UI)
4) *lot* of latex
Am Dienstag, dem 10.10.2023 um 10:31 +0100 schrieb José Matos:
> The use of these options inside LyX should depend on the actual
> context. That would mean that in your particular case the option to
> only rebuild the modules part should be in the modules related
> interface.
Yes, and ideally it s
he modules part should be in the modules related
interface.
In this case this will take time and it should be done in a incremental
way (and so it will take some time).
So I support the inclusion of this change that initially it is only
accessible through the command line.
That was the principle that I
Hey,
So it was annoying me that I every time I added a new module or layout file, I
have to reconfigure lyx, but this is quite slow. On my (admittedly slow) system
it takes about 40 seconds. I noticed the configure.py script itself has some
command line options to make it faster, so when I run
On 6/12/23 00:55, Daniel wrote:
On 2023-06-11 23:28, R. H. van der Gaag wrote:
On 11 Jun 2023, at 18:57, Richard Kimberly Heck
wrote:
On 6/11/23 10:15, R. H. van der Gaag wrote:
* find the word under the cursor (i.e. show other occurrences of
the same word, by highlighting them simult
Le 10/06/2023 à 19:06, Daniel a écrit :
On 2023-06-07 16:16, Jean-Marc Lasgouttes wrote:
Personally, I add the space before the branch. But I can see that it
is mildly annoying.
I am probably missing something here but I don't see how that is
possible at the end of the sentence as in Scott's
w easy is it to define "where it makes a difference"? Will people
guess by themselves why it works here and not there?
I mean, I can understand why inserting spaces at the beginning of some
insets does not make sense, e.g. footnotes, because leading spaces are
just swallowed there. But &
On 2023-06-11 23:28, R. H. van der Gaag wrote:
On 11 Jun 2023, at 18:57, Richard Kimberly Heck wrote:
On 6/11/23 10:15, R. H. van der Gaag wrote:
[…] I would love to see the following text editing commands implemented:
* select around a word (cursor is on a word; the command selects
th
ce "before the branch" is working.
As to the possibilities you mention: wouldn't it nice if LyX allowed to
insert a space at the beginning in those insets where it makes a
difference without going all the way to allow free spacing?
I mean, I can understand why inserting spaces at the
select around a sentence (a grammatical sentence, not a line)
>> jump/select to the beginning of this sentence
>> jump/select to the end of this sentence
> Not trivial in a language-neutral way. (Some languages do not use punctuation
> the way English, say, does.) How does vim h
.)
* select around a paragraph
Same for paragraph-select. (Triple click does this.)
* select around a sentence (a grammatical sentence, not a line)
* jump/select to the beginning of this sentence
* jump/select to the end of this sentence
Not trivial in a language-neutral way. (Some languages
On 6/10/23 13:06, Daniel wrote:
On 2023-06-07 16:16, Jean-Marc Lasgouttes wrote:
Le 01/06/2023 à 17:42, Scott Kostyshak a écrit :
I come across the example in the attachment often in various forms.
It would be nice if I could insert a space at the beginning of an
inset.
Personally, I add the
Dear developers,
I muttered something about this before, but that thread petered out somehow. I
find myself greatly enjoying writing my dissertation in LyX, most of the time…
except when I am confronted with the limitations of text manipulation in LyX,
compared to what I could do in Vim. Specifi
On 2023-06-07 16:16, Jean-Marc Lasgouttes wrote:
Le 01/06/2023 à 17:42, Scott Kostyshak a écrit :
I come across the example in the attachment often in various forms. It
would be nice if I could insert a space at the beginning of an inset.
Personally, I add the space before the branch. But I ca
Le 01/06/2023 à 17:42, Scott Kostyshak a écrit :
I come across the example in the attachment often in various forms. It would be
nice if I could insert a space at the beginning of an inset.
Personally, I add the space before the branch. But I can see that it is
mildly annoying.
JMarc
--
lyx
On Thu, Jun 01, 2023 at 11:54:14AM -0400, Paul A. Rubin wrote:
>
> On 6/1/23 11:42, Scott Kostyshak wrote:
> > I come across the example in the attachment often in various forms. It
> > would be nice if I could insert a space at the beginning of an inset.
> >
> > Am I missing a more natural work
On 6/1/23 11:42, Scott Kostyshak wrote:
I come across the example in the attachment often in various forms. It would be
nice if I could insert a space at the beginning of an inset.
Am I missing a more natural workaround than the ones shown in the example?
Scott
Would Insert > Formatting > Int
I come across the example in the attachment often in various forms. It would be
nice if I could insert a space at the beginning of an inset.
Am I missing a more natural workaround than the ones shown in the example?
Scott
example.lyx
Description: application/lyx
signature.asc
Description: PG
Le 28/01/2023 à 19:53, Jean-Marc Lasgouttes a écrit :
Le 22/01/2023 à 03:36, Stefano Simonucci a écrit :
Do you use HiDPI on your system?
I don't know. How I can know it?
HiDPI is used for monitors with really high resolution, where text and
UI would be too small.
On plain Ubuntu, I can chan
Le 22/01/2023 à 03:36, Stefano Simonucci a écrit :
What is your environment (Wayland/X11, Gnome/KDE/...)?
X11 Mate
Thanks, this was supposed to work, although I do not have any experience
in Mate.
What is the Qt version?
stefano@debsim:~/prova/lyx$ dpkg --get-selections | grep -e qt
M
On Sat, Jan 21, 2023 at 08:27:05PM +0100, Jean-Marc Lasgouttes wrote:
> Le 21/01/2023 ?? 19:29, Pavel Sanda a écrit :
> >Hi all,
> >
> >citing debian bug in #1029234:
> >
> >"After the last upgrade of the package, the lyx editor is broken. The lyx
> >window seems normal, but when I enter the menus,
Le 21/01/2023 à 19:29, Pavel Sanda a écrit :
Hi all,
citing debian bug in #1029234:
"After the last upgrade of the package, the lyx editor is broken. The lyx
window seems normal, but when I enter the menus, the writing disappears or
moves and it is not possible to understand where the cursor is
i handling
JMarc, any other clue than to allow users disabling this improvement?
Stefano is not on devel list, so please keep him CC-ed.
(He is capable to test patches if we have some idea how to address it.)
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/li
From 80b7399a0c5b854f897c97329c8288181a7c62d2 Mon Sep 17 00:00:00 2001
From: John R Hudson
Date: Tue, 3 Jan 2023 11:04:16 +
Subject: [PATCH] Update entries for Foils, Slides and Reports in Chapter 3
Document classes and do final tidying up of Additional.lyx
---
lib/doc/Additional.lyx | 450
On Sat, Nov 05, 2022 at 06:42:15PM +0100, Scott Kostyshak wrote:
> commit 378c19bfc234e42e983b45254f668e21b932bc3b
> Author: Scott Kostyshak
> Date: Sat Nov 5 14:26:43 2022 -0400
>
> Guard some debug code
>
> Amend f352a375 and 3bf1b97a.
> ---
Thibaut, can
I really appreciate your help! LyX has become a very important tool for me. If
something goes wrong, it is a nightmare ;-)
Chris
> Am 09.12.2021 um 20:42 schrieb Jean-Marc Lasgouttes :
>
> Le 09/12/2021 à 19:53, Christoph Schmitz a écrit :
>> Jean-Marc,
>> Fantastic! Problem solved! :-)
>
> T
Le 09/12/2021 à 19:53, Christoph Schmitz a écrit :
Jean-Marc,
Fantastic! Problem solved! :-)
Thanks for confirming. The issue was in the borderless table at the top
of the document. There are still things that I do not understand in your
file, I will try to return to it.
JMarc
--
lyx-devel
Jean-Marc,
Fantastic! Problem solved! :-)
Chris
> Am 09.12.2021 um 19:47 schrieb Jean-Marc Lasgouttes :
>
> Le 09/12/2021 à 18:56, Christoph Schmitz a écrit :
>> Hi Jean-Marc,
>> No, it still does not work.
>> But I do not see any committed updates. The last commit is "ctests: log a
>> fixed
Le 09/12/2021 à 18:56, Christoph Schmitz a écrit :
Hi Jean-Marc,
No, it still does not work.
But I do not see any committed updates. The last commit is "ctests: log a fixed
issue (fr Linguistics.lyx)", 13 hours ago.
You are right, I forgot the most important part. That's what happens
when d
Hi Jean-Marc,
No, it still does not work.
But I do not see any committed updates. The last commit is "ctests: log a fixed
issue (fr Linguistics.lyx)", 13 hours ago.
Chris
> Am 09.12.2021 um 17:21 schrieb Jean-Marc Lasgouttes :
>
> Le 08/12/2021 à 23:34, Christoph Schmitz a écrit :
>> No, alw
Le 08/12/2021 à 23:34, Christoph Schmitz a écrit :
No, always¥s the same, whether no windows is open, whether it has the standard
size or any other size...
Hi Christoph,
Can you confirm that it works now?
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/l
Le 09/12/2021 à 12:23, Kornel Benko a écrit :
Am Wed, 8 Dec 2021 23:54:03 +0100
schrieb Jean-Marc Lasgouttes :
Le 08/12/2021 à 23:34, Christoph Schmitz a écrit :
No, always¥s the same, whether no windows is open, whether it has the standard
size
or any other size...
Believe it or not, this
Am Wed, 8 Dec 2021 23:54:03 +0100
schrieb Jean-Marc Lasgouttes :
> Le 08/12/2021 à 23:34, Christoph Schmitz a écrit :
> > No, always¥s the same, whether no windows is open, whether it has the
> > standard size
> > or any other size...
>
> Believe it or not, this is good news. Hopefully I will
I spotted the problem!
I first exported the document to LyX 2.3 format with the older LyX 2.4 version
that could still open the file, and opened it then with the problematic LyX 2.4
version. Then I saved the file again, created a diff and replaced each
difference in the faulty LyX document one
No, always¥s the same, whether no windows is open, whether it has the standard
size or any other size...
Chris
> Am 08.12.2021 um 22:32 schrieb Jean-Marc Lasgouttes :
>
> Le 08/12/2021 à 20:06, Christoph Schmitz a écrit :
>> I am attaching one of the documents that can no longer be opened. Do
Le 08/12/2021 à 23:34, Christoph Schmitz a écrit :
No, always¥s the same, whether no windows is open, whether it has the standard
size or any other size...
Believe it or not, this is good news. Hopefully I will be able to reproduce.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http
Le 08/12/2021 à 20:06, Christoph Schmitz a écrit :
I am attaching one of the documents that can no longer be opened. Do you have
any idea what could be the cause of the problem?
Unfortunately, I have an idea :( I pushed big changes in document
display. I will try to see if I can reproduce tom
I compile LyX for macOS myself. Since yesterday my compiled versions of LyX do
not open several files anymore (on both Intel and M1 Macs). I see the macOS
beachball forever, but LyX does not crash. Luckily I found a copy of a previous
LyX version, which still works(compiled on Dec 6).
This
Both look good.
Jürgen
Thanks for reviewing, committed.
Yuriy
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Donnerstag, dem 18.02.2021 um 15:49 +0200 schrieb Yuriy Skalko:
> Please review two attached patches:
>
> 1. Now setting of math matrix size by dragging mouse is imprecise due
> to
> Qt limit on min cell size. The patch fixes this.
>
> 2. Now Beamer columns have fixed margin size determined b
Hello,
Please review two attached patches:
1. Now setting of math matrix size by dragging mouse is imprecise due to
Qt limit on min cell size. The patch fixes this.
2. Now Beamer columns have fixed margin size determined by
untranslatable English string. The patch changes it to dynamic.
Y
Le 20/12/2020 à 17:42, Jean-Marc Lasgouttes a écrit :
commit 37e759bc763e5ac0b7541f081ed4eacecafe
Author: Jean-Marc Lasgouttes
Date: Sun Dec 20 18:05:55 2020 +0100
some other stuff that should have been removed from boost
Now we are down to 1.8MB from 2.4MB for 3rdparty/boost
Le 10 novembre 2020 00:45:04 GMT+01:00, Richard Kimberly Heck
a écrit :
>Thanks for the reminder. At the moment, I'm just trying to understand
>how this thing works and cleaning up some stuff that seems...hard to
>understand.
This code is terrifying indeed. I am glad you are d
On 11/9/20 4:22 PM, Jean-Marc Lasgouttes wrote:
Le 09/11/2020 à 21:26, Richard Kimberly Heck a écrit :
commit 4a6d50251a59f6f817ecbbbdb0d3295ee6a3bf5b
Author: Richard Kimberly Heck
Date: Mon Nov 9 15:56:01 2020 -0500
Some comments and some minor re-organization
+ // FIXME This is
Le 09/11/2020 à 21:26, Richard Kimberly Heck a écrit :
commit 4a6d50251a59f6f817ecbbbdb0d3295ee6a3bf5b
Author: Richard Kimberly Heck
Date: Mon Nov 9 15:56:01 2020 -0500
Some comments and some minor re-organization
+ // FIXME This is probably a large part of why updateMacros is
On Sun, Sep 20, 2020 at 08:47:26AM +0200, Jürgen Spitzmüller wrote:
> Am Samstag, den 19.09.2020, 20:14 -0400 schrieb Scott Kostyshak:
> > Starting with this commit, the attached document loads the cprotect
> > package but cprotect command is never used.
>
> Seems this test can be removed without
Am Samstag, den 19.09.2020, 20:14 -0400 schrieb Scott Kostyshak:
> Starting with this commit, the attached document loads the cprotect
> package but cprotect command is never used.
Seems this test can be removed without side-effect. Done.
Jürgen
signature.asc
Description: This is a digitally si
On Sun, Apr 21, 2019 at 04:38:20PM +0200, Juergen Spitzmueller wrote:
> commit c9432ccbbc2ec0029d9ac59ed8da126f4a02a910
> Author: Juergen Spitzmueller
> Date: Sun Apr 21 16:44:29 2019 +0200
>
> \cprotect some content in captions
>
> Fixes: #6243
>
Am Mo., 7. Sept. 2020 um 21:09 Uhr schrieb Kornel Benko :
> Am Mon, 7 Sep 2020 20:51:52 +0200
> schrieb Yu Jin :
>
> > Can I commit the attached patch? It is used here (dtl.h):
> >
> > #if (defined(__cplusplus) || defined(__STDC__) || defined(c_plusplus))
> > #define STDC 1
> > #else
> > #define S
Am Mon, 7 Sep 2020 20:51:52 +0200
schrieb Yu Jin :
> Can I commit the attached patch? It is used here (dtl.h):
>
> #if (defined(__cplusplus) || defined(__STDC__) || defined(c_plusplus))
> #define STDC 1
> #else
> #define STDC 0
> #endif
>
> /* Version (Traditional or ANSI) of C affects prototype
Can I commit the attached patch? It is used here (dtl.h):
#if (defined(__cplusplus) || defined(__STDC__) || defined(c_plusplus))
#define STDC 1
#else
#define STDC 0
#endif
/* Version (Traditional or ANSI) of C affects prototype and type
definitions */
#if STDC
#define ARGS(parenthesized_list) par
Am Sat, 1 Aug 2020 01:54:15 -0400
schrieb Richard Kimberly Heck :
> > I came with another 'solution', unfortunately META_INSET is defined in
> > Paragraph.cpp,
> > and not available in any header file.
>
> It is probably defined in Paragraph.cpp now only because it is not
> needed anywhere els
EST)
> > > schrieb Thibaut Cuvelier <mailto:tcuvel...@lyx.org>>:
> > >
> > > > commit 85946aae2b94fedf5ce9bd35e91ba500986b5121
> > > > Author: Thibaut Cuvelier <mailto:tcuvel...@lyx.org>>
> > > &
On 7/31/20 12:56 PM, Kornel Benko wrote:
> Am Fri, 31 Jul 2020 17:36:35 +0200
> schrieb Thibaut Cuvelier :
>
>> On Fri, 31 Jul 2020 at 15:12, Kornel Benko wrote:
>>
>>> The relevant chars are inside a comment, so probably not handled yet
>>>
>>> ...
>>> Wählen Sie hierfür >> role='sans'>Dokument⇒E
gt; > > Am Fri, 31 Jul 2020 23:37:33 +0200 (CEST)
>> > > schrieb Thibaut Cuvelier :
>> > >
>> > > > commit 85946aae2b94fedf5ce9bd35e91ba500986b5121
>> > > > Author: Thibaut Cuvelier
>> > > > Date: Sat A
Thibaut Cuvelier :
> > >
> > > > commit 85946aae2b94fedf5ce9bd35e91ba500986b5121
> > > > Author: Thibaut Cuvelier
> > > > Date: Sat Aug 1 00:02:36 2020 +0200
> > > >
> > > > DocBook: fix XML in comments (-- forbidden for some historical
>
> Author: Thibaut Cuvelier
> > > Date: Sat Aug 1 00:02:36 2020 +0200
> > >
> > > DocBook: fix XML in comments (-- forbidden for some historical
> > reason).
> > > ---
> > > autotests/export/docbook/deutsches_ert.lyx | 14
; > DocBook: fix XML in comments (-- forbidden for some historical
> reason).
> > ---
> > autotests/export/docbook/deutsches_ert.lyx | 14 +-
> > autotests/export/docbook/deutsches_ert.xml |2 +-
> > src/insets/InsetERT.cpp|
Am Fri, 31 Jul 2020 23:37:33 +0200 (CEST)
schrieb Thibaut Cuvelier :
> commit 85946aae2b94fedf5ce9bd35e91ba500986b5121
> Author: Thibaut Cuvelier
> Date: Sat Aug 1 00:02:36 2020 +0200
>
> DocBook: fix XML in comments (-- forbidden for some historical reason).
> ---
&
Am Fri, 31 Jul 2020 20:18:17 +0200
schrieb Thibaut Cuvelier :
> On Fri, 31 Jul 2020 at 18:59, Kornel Benko wrote:
>
> > Am Fri, 31 Jul 2020 17:36:35 +0200
> > schrieb Thibaut Cuvelier :
> >
> > > On Fri, 31 Jul 2020 at 15:12, Kornel Benko wrote:
> > >
> > > >
> > > > The relevant chars are insi
Am Fri, 31 Jul 2020 18:56:40 +0200
schrieb Kornel Benko :
> >
> >
> > Is this OK? I already pushed the corresponding code,
Not in repository yet.
> as it's quite a bit of
> > cleaning in many places with respect to the current situation. (The test
> > case is not valid yet, but the issue for t
On Fri, 31 Jul 2020 at 18:59, Kornel Benko wrote:
> Am Fri, 31 Jul 2020 17:36:35 +0200
> schrieb Thibaut Cuvelier :
>
> > On Fri, 31 Jul 2020 at 15:12, Kornel Benko wrote:
> >
> > >
> > > The relevant chars are inside a comment, so probably not handled yet
> > >
> > > ...
> > > Wählen Sie hierfü
Am Fri, 31 Jul 2020 17:36:35 +0200
schrieb Thibaut Cuvelier :
> On Fri, 31 Jul 2020 at 15:12, Kornel Benko wrote:
>
> >
> > The relevant chars are inside a comment, so probably not handled yet
> >
> > ...
> > Wählen Sie hierfür > role='sans'>Dokument⇒Einstellungen⇒LaTeX-Vorspann. Dies
> > öffne
Am Fri, 31 Jul 2020 17:36:35 +0200
schrieb Thibaut Cuvelier :
> On Fri, 31 Jul 2020 at 15:12, Kornel Benko wrote:
>
> >
> > The relevant chars are inside a comment, so probably not handled yet
> >
> > ...
> > Wählen Sie hierfür > role='sans'>Dokument⇒Einstellungen⇒LaTeX-Vorspann. Dies
> > öffne
On Fri, 31 Jul 2020 at 15:12, Kornel Benko wrote:
>
> The relevant chars are inside a comment, so probably not handled yet
>
> ...
> Wählen Sie hierfür role='sans'>Dokument⇒Einstellungen⇒LaTeX-Vorspann. Dies
> öffnet ein
> Editierfenster, in das Sie Ihre bevorzugten Befehle schreiben
> können.Da
The relevant chars are inside a comment, so probably not handled yet
...
Wählen Sie hierfür Dokument⇒Einstellungen⇒LaTeX-Vorspann. Dies öffnet ein
Editierfenster, in das Sie Ihre bevorzugten Befehle schreiben
können.Das
Editierverhalten in diesem Fenster ist spezifisch, also erwarten Sie nicht,
Am Dienstag, den 23.06.2020, 23:54 +0200 schrieb Jean-Marc Lasgouttes:
> This is the actual commit I intended to push today. It uses the
> rowFLags() infrastructure that I introduced yesterday and allows for
> line breaking after some special characters and some spaces.
>
> PS:
Am Samstag, den 02.05.2020, 13:28 +0200 schrieb Kornel Benko:
> Sorry, too late for this mail. Already pushed. Should I move?
I see you did. Thanks!
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/
Am Sat, 02 May 2020 13:22:39 +0200
schrieb Jürgen Spitzmüller :
> Am Samstag, den 02.05.2020, 13:13 +0200 schrieb Jürgen Spitzmüller:
> > Am Samstag, den 02.05.2020, 11:47 +0200 schrieb Kornel Benko:
> > > Is that an OK to commit?
> >
> > No objections from me.
>
> However, I think develop
Am Samstag, den 02.05.2020, 13:13 +0200 schrieb Jürgen Spitzmüller:
> Am Samstag, den 02.05.2020, 11:47 +0200 schrieb Kornel Benko:
> > Is that an OK to commit?
>
> No objections from me.
However, I think development/tools is more appropriate than lib/scripts
(the former has scripts for developme
1 - 100 of 2357 matches
Mail list logo
