Am Mittwoch, dem 07.05.2025 um 10:11 +0900 schrieb Koji Yokota:
> I fixed potentially related setbacks in commit 22dffc7. Does this
> solve the problem?
Looks solved (on brief testing). Thanks.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/ly
> 2025/05/06 0:28、Jürgen Spitzmüller のメール:
> It might be relevant that I inserted numbers to the theorem. I think
> these might change the direction, as well.
Jurgen,
I fixed potentially related setbacks in commit 22dffc7. Does this solve the
problem?
Koji--
lyx-devel mailing list
lyx-devel@li
Am Montag, dem 05.05.2025 um 23:59 +0900 schrieb Koji Yokota:
> > 2025/05/05 0:46、Jürgen Spitzmüller
> > のメール:
> >
> > I get pretty reproducible assertions in master when
> >
> > * opening a new document with AMS book
> > * setting main language to Hebrew
> > * insert a theorem
> > * wait a bit/c
> 2025/05/05 0:46、Jürgen Spitzmüller
> のメール:
>
> I get pretty reproducible assertions in master when
>
> * opening a new document with AMS book
> * setting main language to Hebrew
> * insert a theorem
> * wait a bit/compile/do something
>
I tested on Mac 15.4.1 with Qt 5.15.18 but I couldn’t r
On Sun, Mar 02, 2025 at 05:00:43PM +0100, JP wrote:
> > This message looks like comming from wxWidgets so as if you have some GUI
> > application running?
>
> Poedit, among others. It creates a lot of traffic on the command line, like:
>
> (net.poedit.Poedit:686930): Gtk-CRITICAL **: 17:56:36.63
Le 25/02/2025 à 10:19, Pavel Sanda a écrit :
On Mon, Feb 24, 2025 at 05:37:00PM +0100, Jean-Pierre Chrétien wrote:
Dear devs
While running git pull, I see this:
./src/common/file.cpp(256): assert ""(wxFileOffset)length == Length()""
failed in ReadAll(): huge file not supported
How/where do y
On Mon, Feb 24, 2025 at 05:37:00PM +0100, Jean-Pierre Chrétien wrote:
> Dear devs
>
> While running git pull, I see this:
>
> ./src/common/file.cpp(256): assert ""(wxFileOffset)length == Length()""
> failed in ReadAll(): huge file not supported
How/where do you make the git pull? From command li
On Wed, Jul 03, 2024 at 06:35:03PM GMT, Scott Kostyshak wrote:
> On Wed, Jul 03, 2024 at 11:59:14PM GMT, Jean-Marc Lasgouttes wrote:
> > Le 03/07/2024 à 19:34, Scott Kostyshak a écrit :
> > > On Wed, Jul 03, 2024 at 05:48:23PM GMT, Jean-Marc Lasgouttes wrote:
> > > > Le 03/07/2024 à 06:17, Scott Ko
On Wed, Jul 03, 2024 at 11:59:14PM GMT, Jean-Marc Lasgouttes wrote:
> Le 03/07/2024 à 19:34, Scott Kostyshak a écrit :
> > On Wed, Jul 03, 2024 at 05:48:23PM GMT, Jean-Marc Lasgouttes wrote:
> > > Le 03/07/2024 à 06:17, Scott Kostyshak a écrit :
> > > > I still get an assertion while selecting the
Le 03/07/2024 à 19:34, Scott Kostyshak a écrit :
On Wed, Jul 03, 2024 at 05:48:23PM GMT, Jean-Marc Lasgouttes wrote:
Le 03/07/2024 à 06:17, Scott Kostyshak a écrit :
I still get an assertion while selecting the phone table.
Hmm, I was two quick in my testing.
I just pushed two patches which:
On Wed, Jul 03, 2024 at 05:48:23PM GMT, Jean-Marc Lasgouttes wrote:
> Le 03/07/2024 à 06:17, Scott Kostyshak a écrit :
> > I still get an assertion while selecting the phone table.
>
> Hmm, I was two quick in my testing.
>
> I just pushed two patches which:
> 1/ avoids setting Update::SinglePar i
Le 03/07/2024 à 06:17, Scott Kostyshak a écrit :
I still get an assertion while selecting the phone table.
Hmm, I was two quick in my testing.
I just pushed two patches which:
1/ avoids setting Update::SinglePar in a place where this does not make
sense
2/ make BufferView::singleParUpdate rob
Am Wed, 3 Jul 2024 00:17:29 -0400
schrieb Scott Kostyshak :
> On Wed, Jul 03, 2024 at 12:35:38AM GMT, Jean-Marc Lasgouttes wrote:
> > Le 02/07/2024 à 05:27, Scott Kostyshak a écrit :
> > > I no longer get the assertion in that place. But if I work a bit harder
> > > and drag the selection up and
On Wed, Jul 03, 2024 at 12:35:38AM GMT, Jean-Marc Lasgouttes wrote:
> Le 02/07/2024 à 05:27, Scott Kostyshak a écrit :
> > I no longer get the assertion in that place. But if I work a bit harder
> > and drag the selection up and down, eventually I get an assertion.
> > Backtrace attached (this was
Le 02/07/2024 à 05:27, Scott Kostyshak a écrit :
I no longer get the assertion in that place. But if I work a bit harder
and drag the selection up and down, eventually I get an assertion.
Backtrace attached (this was while testing the patch).
OK, I just pushed a different solution: instead of b
Le 02/07/2024 à 17:44, Scott Kostyshak a écrit :
Oops, sorry about that. Backtrace now attached.
The way I reproduce is just drag selection with my mouse up and down, up
and down in the User Guide. It usually just takes a few seconds.
I can reproduce too. The goodpart is that the assertion abo
On Mon, Jul 01, 2024 at 11:39:36PM GMT, Richard Kimberly Heck wrote:
> No backtrace!
>
> On 7/1/24 11:27 PM, Scott Kostyshak wrote:
> > On Tue, Jul 02, 2024 at 12:12:07AM GMT, Jean-Marc Lasgouttes wrote:
> > > Le 28/06/2024 à 18:15, Scott Kostyshak a écrit :
> > > > > Does this patch help?
> > > >
No backtrace!
On 7/1/24 11:27 PM, Scott Kostyshak wrote:
On Tue, Jul 02, 2024 at 12:12:07AM GMT, Jean-Marc Lasgouttes wrote:
Le 28/06/2024 à 18:15, Scott Kostyshak a écrit :
Does this patch help?
It does not seem to help. I still get the assertion.
This one should be better.
I no longer get
On Tue, Jul 02, 2024 at 12:12:07AM GMT, Jean-Marc Lasgouttes wrote:
> Le 28/06/2024 à 18:15, Scott Kostyshak a écrit :
> > > Does this patch help?
> >
> > It does not seem to help. I still get the assertion.
>
> This one should be better.
I no longer get the assertion in that place. But if I wor
Le 28/06/2024 à 18:15, Scott Kostyshak a écrit :
Does this patch help?
It does not seem to help. I still get the assertion.
This one should be better.
JMarc
From 59bac4712239505148b2fc8e3d9443373d138890 Mon Sep 17 00:00:00 2001
From: Jean-Marc Lasgouttes
Date: Mon, 1 Jul 2024 23:56:33 +02
On Fri, 2024-06-28 at 14:29 -0400, Scott Kostyshak wrote:
> The table is in the user guide. I open the user guide, I search for
> "phone" which takes me to the table. Then I double click on a word a
> couple of lines above the table, and hold and drag down.
>
> Scott
Scott's recipe works for me:
On Fri, Jun 28, 2024 at 07:57:43PM GMT, Jean-Marc Lasgouttes wrote:
> Le 28/06/2024 à 18:15, Scott Kostyshak a écrit :
> > On Fri, Jun 28, 2024 at 05:36:15PM GMT, Jean-Marc Lasgouttes wrote:
> > > Le 26/06/2024 à 06:25, Scott Kostyshak a écrit :
> > > > When I select the table with the mouse cursor
Le 28/06/2024 à 18:15, Scott Kostyshak a écrit :
On Fri, Jun 28, 2024 at 05:36:15PM GMT, Jean-Marc Lasgouttes wrote:
Le 26/06/2024 à 06:25, Scott Kostyshak a écrit :
When I select the table with the mouse cursor (see attachment for which
table), I get the following assertion:
support/lasse
On Fri, Jun 28, 2024 at 05:36:15PM GMT, Jean-Marc Lasgouttes wrote:
> Le 26/06/2024 à 06:25, Scott Kostyshak a écrit :
> > When I select the table with the mouse cursor (see attachment for which
> > table), I get the following assertion:
> >
> >support/lassert.cpp (52): ASSERTION hasPosition()
Le 26/06/2024 à 06:25, Scott Kostyshak a écrit :
When I select the table with the mouse cursor (see attachment for which
table), I get the following assertion:
support/lassert.cpp (52): ASSERTION hasPosition() VIOLATED IN
/home/scott/lyxbuilds/master-master/repo/src/ParagraphMetrics.cpp:71
On Fri, Mar 01, 2024 at 09:32:53AM +0100, Jean-Pierre Chrétien wrote:
> I will install this last version now and proceed with editing. I'll keep you
> posted if it happens again.
Might be difficult as it's triggered by painting, but reproducible example
would help a lot...
Pavel
--
lyx-devel mai
On Sun, 2022-12-04 at 22:14 +0100, Jean-Marc Lasgouttes wrote:
> > On the other hand I was concerned with encoding a text message in
> > integer number that in Python is infinite precision:
>
> You lost me here.
>
> JMarc
That is a way to pass a a light message (season's greetings) into a
seriou
Le 04/12/2022 à 22:13, José Matos a écrit :
On Sun, 2022-12-04 at 21:12 +0100, Jean-Marc Lasgouttes wrote:
I finally managed to convinced python to like me, and pushed the
result.
JMarc
Nice, I intended to look into this issue this weekend.
Let's say I believe you ;)
On the other hand I w
On Sun, 2022-12-04 at 21:12 +0100, Jean-Marc Lasgouttes wrote:
> I finally managed to convinced python to like me, and pushed the
> result.
>
> JMarc
Nice, I intended to look into this issue this weekend.
On the other hand I was concerned with encoding a text message in
integer number that in Py
On Sun, Dec 04, 2022 at 09:12:45PM +0100, Jean-Marc Lasgouttes wrote:
> Le 02/12/2022 à 18:11, Scott Kostyshak a écrit :
> > > Just as a reminder, the goal is to have char-delete-backwards without
> > > argument actually delete previous element, without consideration of
> > > confirmation that are
Le 02/12/2022 à 18:11, Scott Kostyshak a écrit :
Just as a reminder, the goal is to have char-delete-backwards without
argument actually delete previous element, without consideration of
confirmation that are only relevant to interactive use.
Sorry, I have no experience with this.
Once sorted
On Mon, Nov 28, 2022 at 05:40:44PM +0100, Jean-Marc Lasgouttes wrote:
> Le 21/02/2022 à 15:10, Jean-Marc Lasgouttes a écrit :
> > Le 21/02/2022 à 03:27, Scott Kostyshak a écrit :
> > > On Sun, Feb 20, 2022 at 07:20:24PM +0100, Jean-Marc Lasgouttes wrote:
> > > > I really wonder why this special beh
Le 21/02/2022 à 15:10, Jean-Marc Lasgouttes a écrit :
Le 21/02/2022 à 03:27, Scott Kostyshak a écrit :
On Sun, Feb 20, 2022 at 07:20:24PM +0100, Jean-Marc Lasgouttes wrote:
I really wonder why this special behavior is by default, since it is
only
useful for interactive edition.
I would prefer
On Mon, Feb 21, 2022 at 03:10:00PM +0100, Jean-Marc Lasgouttes wrote:
> Le 21/02/2022 à 03:27, Scott Kostyshak a écrit :
> > On Sun, Feb 20, 2022 at 07:20:24PM +0100, Jean-Marc Lasgouttes wrote:
> > > I really wonder why this special behavior is by default, since it is only
> > > useful for interac
Le 21/02/2022 à 03:27, Scott Kostyshak a écrit :
On Sun, Feb 20, 2022 at 07:20:24PM +0100, Jean-Marc Lasgouttes wrote:
I really wonder why this special behavior is by default, since it is only
useful for interactive edition.
I would prefer to have
char-delete-forward confirm
bound to the ke
On Sun, Feb 20, 2022 at 07:20:24PM +0100, Jean-Marc Lasgouttes wrote:
>
> Le 18/02/2022 à 17:12, Scott Kostyshak a écrit :
> > To reproduce, open the User Guide (make sure it is editable, i.e., not
> > read only). Then run the following command sequence:
> >
> > command-sequence inset-forall Capt
Le 18/02/2022 à 17:12, Scott Kostyshak a écrit :
To reproduce, open the User Guide (make sure it is editable, i.e., not
read only). Then run the following command sequence:
command-sequence inset-forall Caption char-delete-forward; statistics; undo
I get the following assertion:
Fixed in tru
On Thu, Nov 26, 2020 at 10:54:38AM +0100, Jean-Marc Lasgouttes wrote:
> Le 25/11/2020 à 15:40, Scott Kostyshak a écrit :
> > While experimenting with undo/redo after a "replace all" with Advanced
> > find, I received an assertion. I think the cursor was in the "Find" work
> > area. Unfortunately, I
Le 25/11/2020 à 15:40, Scott Kostyshak a écrit :
While experimenting with undo/redo after a "replace all" with Advanced
find, I received an assertion. I think the cursor was in the "Find" work
area. Unfortunately, I cannot reproduce. The assertion and terminal (not
GDB) backtrace is attached.
Sc
Am Thu, 26 Mar 2020 19:05:36 -0400
schrieb Scott Kostyshak :
> On Thu, Mar 26, 2020 at 08:08:50PM +0100, Jean-Marc Lasgouttes wrote:
> > Le 26/03/2020 à 19:35, Scott Kostyshak a écrit :
> > > Note that I made a recent change in a setCursor() call in outline-down
> > > so that is a good candidate
On Thu, Mar 26, 2020 at 08:08:50PM +0100, Jean-Marc Lasgouttes wrote:
> Le 26/03/2020 à 19:35, Scott Kostyshak a écrit :
> > Note that I made a recent change in a setCursor() call in outline-down
> > so that is a good candidate.
>
> Indeed :)
Attached is an example file. To reproduce, put the cur
Le 26/03/2020 à 19:35, Scott Kostyshak a écrit :
Note that I made a recent change in a setCursor() call in outline-down
so that is a good candidate.
Indeed :)
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Thu, Mar 26, 2020 at 06:55:19PM +0100, Jean-Marc Lasgouttes wrote:
> Le 26/03/2020 à 18:33, Kornel Benko a écrit :
> >
> > The command:
> > /BUILD/BUILDMint18/BuildLyxGitQt5.9.5local-gcc8.3.0/bin/lyx2.4 '-userdir'
> > '/BUILD/BUILDMint18/BuildLyxGitQt5.9.5local-gcc8.3.0/Testing/.lyxbatch'
Le 26/03/2020 à 18:33, Kornel Benko a écrit :
The command:
/BUILD/BUILDMint18/BuildLyxGitQt5.9.5local-gcc8.3.0/bin/lyx2.4 '-userdir'
'/BUILD/BUILDMint18/BuildLyxGitQt5.9.5local-gcc8.3.0/Testing/.lyxbatch'
'-platform'
'offscreen' '-x' 'command-sequence file-open
beamer_test.lyx;buffer-beg
Le 26/03/2020 à 18:33, Kornel Benko a écrit :
Attached the commands to provoke the assert.
Looks like Jean-Marc would be happy to fix :)
I am happy to put it on my to-do fifo stack :)
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On 2020-02-22 07:19, Stephan Witt wrote:
Am 21.02.2020 um 19:54 schrieb Daniel :
On 2020-02-21 19:41, Daniel wrote:
On 2020-02-19 21:29, Richard Kimberly Heck wrote:
On 2/19/20 11:38 AM, Daniel wrote:
I just navigated between child documents using the outliner's Table of
Contents as a dial
> Am 21.02.2020 um 19:54 schrieb Daniel :
>
> On 2020-02-21 19:41, Daniel wrote:
>> On 2020-02-19 21:29, Richard Kimberly Heck wrote:
>>> On 2/19/20 11:38 AM, Daniel wrote:
I just navigated between child documents using the outliner's Table of
Contents as a dialog appeared (attached).
On 2020-02-21 19:41, Daniel wrote:
On 2020-02-19 21:29, Richard Kimberly Heck wrote:
On 2/19/20 11:38 AM, Daniel wrote:
I just navigated between child documents using the outliner's Table of
Contents as a dialog appeared (attached). Any idea what this might be
about?
No, that's an obscure one
On 2020-02-19 21:29, Richard Kimberly Heck wrote:
On 2/19/20 11:38 AM, Daniel wrote:
I just navigated between child documents using the outliner's Table of
Contents as a dialog appeared (attached). Any idea what this might be
about?
No, that's an obscure one. The DocIterator is invalid, but wh
On 2/19/20 11:38 AM, Daniel wrote:
> I just navigated between child documents using the outliner's Table of
> Contents as a dialog appeared (attached). Any idea what this might be
> about?
No, that's an obscure one. The DocIterator is invalid, but why? No clue
without a backtrace or a way to repro
On Sat, Dec 03, 2016 at 10:55:37AM +0100, racoon wrote:
> On 03.12.2016 10:35, Andrew Parsloe wrote:
> > I would need to download bleeding-edge lyx to test this and it's not
> > clear to me that this is being maintained now -- there's a reference to
> > master and 2.1.x on the website, no mention
On 03.12.2016 10:35, Andrew Parsloe wrote:
On 2/12/2016 7:11 p.m., Scott Kostyshak wrote:
On Wed, Nov 02, 2016 at 09:56:39AM +1300, Andrew Parsloe wrote:
The assertion message references Paragraph.cpp, line 1723.
Andrew can you reproduce this on current master?
Scott
I would need to downl
On 2/12/2016 7:11 p.m., Scott Kostyshak wrote:
On Wed, Nov 02, 2016 at 09:56:39AM +1300, Andrew Parsloe wrote:
The assertion message references Paragraph.cpp, line 1723.
Andrew can you reproduce this on current master?
Scott
I would need to download bleeding-edge lyx to test this and it's n
On Wed, Nov 02, 2016 at 09:56:39AM +1300, Andrew Parsloe wrote:
> The assertion message references Paragraph.cpp, line 1723.
Andrew can you reproduce this on current master?
Scott
signature.asc
Description: PGP signature
On Mon, Jul 18, 2016 at 08:43:09PM +0200, Jean-Marc Lasgouttes wrote:
> I would propose this.
For archival purposes, note that the patch was committed at e35110ea.
Scott
signature.asc
Description: PGP signature
On 11/01/2016 09:56 PM, Andrew Parsloe wrote:
I tried out Insert>Special Character>Symbols in response to an email
to the list from Michael Berger and triggered an assertion. (LyX 2.2.2
on Windows 7)
Recipe: in a new document
Insert>Special Character>Symbols>Mathematical Alphanumeric Symbols
On Wed, Nov 02, 2016 at 09:56:39AM +1300, Andrew Parsloe wrote:
> I tried out Insert>Special Character>Symbols in response to an email to the
> list from Michael Berger and triggered an assertion. (LyX 2.2.2 on Windows
> 7)
>
> Recipe: in a new document
> Insert>Special Character>Symbols>Mathemati
Le 18/07/2016 à 23:54, Richard Heck a écrit :
I would propose this.
Seems reasonable.
So shall I commit? What did your earlier patch do?
I do have some general questions about the way labelfont_ is set in
InsetArgument. It seems to get reset (along with a lot of other
private variables) eve
On 07/18/2016 02:43 PM, Jean-Marc Lasgouttes wrote:
> Le 18/07/2016 18:53, Richard Heck a écrit :
>> On 07/18/2016 06:26 AM, Andrew Parsloe wrote:
>>> I've attached a MWE in which a flex inset is defined in a local layout
>>> (and validates). However, as soon as I try to insert the argument LyX
>>>
Le 18/07/2016 18:53, Richard Heck a écrit :
On 07/18/2016 06:26 AM, Andrew Parsloe wrote:
I've attached a MWE in which a flex inset is defined in a local layout
(and validates). However, as soon as I try to insert the argument LyX
generates the assertion in the attached png. It seems to be the u
On 07/18/2016 06:26 AM, Andrew Parsloe wrote:
> I've attached a MWE in which a flex inset is defined in a local layout
> (and validates). However, as soon as I try to insert the argument LyX
> generates the assertion in the attached png. It seems to be the use of
> Color in the LabelFont specificat
On Sat, Jun 06, 2015 at 07:03:08PM +0200, Kornel Benko wrote:
> Am Freitag, 5. Juni 2015 um 17:26:12, schrieb Scott Kostyshak
>
> > To reproduce, on master open mwe.lyx, place the cursor inside of the
> > empty chunk, and press Backspace.
> >
> > Can others reproduce?
> >
> > Note also that whe
Am Freitag, 5. Juni 2015 um 17:26:12, schrieb Scott Kostyshak
> To reproduce, on master open mwe.lyx, place the cursor inside of the
> empty chunk, and press Backspace.
>
> Can others reproduce?
>
> Note also that when I export mwe.lyx to 2.1.x format, the separator is
> gone and there is an ERT
On Sat, Sep 7, 2013 at 3:33 AM, Kornel Benko wrote:
> Am Samstag, 7. September 2013 um 01:01:06, schrieb Scott Kostyshak
>
>
>> Several LyX math parser warnings are fixed at 1a96a9cf
>
>>
>
>> Two warnings remain that might be serious. Attached is an MWE that can
>
>> be used to reproduce an asse
Am Samstag, 7. September 2013 um 01:01:06, schrieb Scott Kostyshak
> Several LyX math parser warnings are fixed at 1a96a9cf
>
> Two warnings remain that might be serious. Attached is an MWE that can
> be used to reproduce an assertion. I can reproduce on Ubuntu 13.04 on
> both branch and trunk i
Am Samstag, 27. April 2013 um 20:16:12, schrieb Jean-Marc Lasgouttes
> Le 27/04/2013 20:00, Kornel Benko a écrit :
> > Yes. Removal of one lassert leads to crash on the next. This time on:
> >
> > support/lassert.cpp (72): ASSERTION pos < size() VIOLATED IN
> > /usr/src/lyx/lyx-git/src/mathed/Mat
Le 27/04/2013 20:00, Kornel Benko a écrit :
Yes. Removal of one lassert leads to crash on the next. This time on:
support/lassert.cpp (72): ASSERTION pos < size() VIOLATED IN
/usr/src/lyx/lyx-git/src/mathed/MathData.cpp:77
Assertion triggered in void lyx::doBufErr(const char*, const docstring&,
Am Samstag, 27. April 2013 um 19:51:58, schrieb Jean-Marc Lasgouttes
> Le 27/04/2013 19:29, Kornel Benko a écrit :
> > LyX-versions created since Apr 26 are no longer runnable.
> >
> > ...
> >
> > support/lassert.cpp (43): ASSERTION false VIOLATED IN
> > /usr/src/lyx/lyx-git/src/Cursor.cpp:1146
>
Le 27/04/2013 19:29, Kornel Benko a écrit :
LyX-versions created since Apr 26 are no longer runnable.
...
support/lassert.cpp (43): ASSERTION false VIOLATED IN
/usr/src/lyx/lyx-git/src/Cursor.cpp:1146
Assertion triggered in void lyx::doAssert(const char*, const char*, long
int) by failing chec
Am Samstag, 27. April 2013 um 19:29:26, schrieb Kornel Benko
> LyX-versions created since Apr 26 are no longer runnable.
> ...
> support/lassert.cpp (43): ASSERTION false VIOLATED IN
> /usr/src/lyx/lyx-git/src/Cursor.cpp:1146
> Assertion triggered in void lyx::doAssert(const char*, const char*, l
On 04/07/2013 03:24 AM, Abdelrazak Younes wrote:
On 06/04/2013 20:04, Scott Kostyshak wrote:
On Sat, Apr 6, 2013 at 11:28 AM, Richard Heck wrote:
On 04/05/2013 11:31 PM, Scott Kostyshak wrote:
Should LyX exit more gracefully here?
$ lyx -e pdf2 Intro.lyx
Missing user LyX directory
--
On 06/04/2013 20:04, Scott Kostyshak wrote:
On Sat, Apr 6, 2013 at 11:28 AM, Richard Heck wrote:
On 04/05/2013 11:31 PM, Scott Kostyshak wrote:
Should LyX exit more gracefully here?
$ lyx -e pdf2 Intro.lyx
Missing user LyX directory
You have specified
On Sat, Apr 6, 2013 at 11:28 AM, Richard Heck wrote:
> On 04/05/2013 11:31 PM, Scott Kostyshak wrote:
>>
>> Should LyX exit more gracefully here?
>>
>> $ lyx -e pdf2 Intro.lyx
>> Missing user LyX directory
>>
>> You have specified a non-existent user LyX di
On 04/05/2013 11:31 PM, Scott Kostyshak wrote:
Should LyX exit more gracefully here?
$ lyx -e pdf2 Intro.lyx
Missing user LyX directory
You have specified a non-existent user LyX directory,
/home/scott/lyxbuilds/master/user-dir.
It is needed to keep your
On Thu, Jun 2, 2011 at 1:22 PM, Richard Heck wrote:
> On 06/02/2011 12:47 PM, BH wrote:
>> I'm noticing many of these assertions showing up in the console
>> whenever I type a non-space character:
>>
>> lyx-devel/src/support/lassert.cpp(35): ASSERTION it != d->words_.end()
>> VIOLATED IN lyx-devel
On 06/02/2011 12:47 PM, BH wrote:
> I'm noticing many of these assertions showing up in the console
> whenever I type a non-space character:
>
> lyx-devel/src/support/lassert.cpp(35): ASSERTION it != d->words_.end()
> VIOLATED IN lyx-devel/src/WordList.cpp:76
>
I don't see this right now under Linu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/03/11 09:25, Rainer M Krug wrote:
> On 31/03/11 09:20, Rainer M Krug wrote:
>> On 31/03/11 09:18, Rainer M Krug wrote:
>>> On 30/03/11 19:45, Peter Kümmel wrote:
On 30.03.2011 11:46, Rainer M Krug wrote:
>>> I downloaded rc2, configured
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/03/11 09:20, Rainer M Krug wrote:
> On 31/03/11 09:18, Rainer M Krug wrote:
>> On 30/03/11 19:45, Peter Kümmel wrote:
>>> On 30.03.2011 11:46, Rainer M Krug wrote:
>> I downloaded rc2, configured it and compiled and installed it without
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/03/11 09:18, Rainer M Krug wrote:
> On 30/03/11 19:45, Peter Kümmel wrote:
>> On 30.03.2011 11:46, Rainer M Krug wrote:
> I downloaded rc2, configured it and compiled and installed it without
> problems or error messages.
if you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/03/11 19:45, Peter Kümmel wrote:
> On 30.03.2011 11:46, Rainer M Krug wrote:
I downloaded rc2, configured it and compiled and installed it without
problems or error messages.
>>>
>>> if you install lyx and run it for the first time, lyx
On 30.03.2011 11:46, Rainer M Krug wrote:
I downloaded rc2, configured it and compiled and installed it without
problems or error messages.
if you install lyx and run it for the first time, lyx should reconfigure.
can you post the log from this reconfiguration?
Here it is - but keep in mind,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/03/11 11:33, Pavel Sanda wrote:
> Rainer M Krug wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi
>>
>> I downloaded rc2, configured it and compiled and installed it without
>> problems or error messages.
>
> if you install lyx
Rainer M Krug wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi
>
> I downloaded rc2, configured it and compiled and installed it without
> problems or error messages.
if you install lyx and run it for the first time, lyx should reconfigure.
can you post the log from this reconfigu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know it is bad to reply to ones own post, but I tried it under gdb,
and there it is working.
Tried without gdb, same error.
Rainer
On 30/03/11 10:44, Rainer M Krug wrote:
> Hi
>
> I downloaded rc2, configured it and compiled and installed it wit
On 02/15/2011 06:54 PM, Pavel Sanda wrote:
Tommaso Cucinotta wrote:
What was recently changed ?
perhaps file format change which went in today.
Missing space. Fixed.
rh
Tommaso Cucinotta wrote:
> What was recently changed ?
perhaps file format change which went in today.
pavel
On 16.02.2011 00:11, Tommaso Cucinotta wrote:
# New file
KK: \Cn
# Find Advanced
KK: \CF
and assertion at FindAndReplace.cpp:58
51 /// Apply to buf the parameters supplied through bp
52 static void ApplyParams(Buffer&buf, BufferParams const& bp) {
53ss<< "\\end_header\n";
54is
> My small files still give wrong output, though (duplicated first line)
This was a last-minute clean-up, but I forgot to update the rp. This happens
before the algorithm really starts.
Fixed at r33184.
Now we have immediately a check whether the files are the same. If so, the
algorithm shoul
Jürgen Spitzmüller wrote:
> I think you need to set a GridLayout to the GroupBox (also, the two Radio
> buttons need accelerators, and the two Browse buttons need different
> accelerators)
As in the attached patch.
Jürgen
Index: src/frontends/qt4/ui/CompareUi.ui
>>
>> If you click Compare, a thread is started and the Close button
changes
>> to Cancel: to stop the thread.
>>
>> After pressing it, it will stop the thread and the button text
changes
>> back to Close: to close the window.
>
>Why not close the window right away?
>
I don't know.. Maybe becaus
"Vincent van Ravesteijn - TNW" writes:
>>BTW, when I click on Cancel, the button just turns to
>>'Close'. What does that mean?
>
> If you click Compare, a thread is started and the Close button changes
> to Cancel: to stop the thread.
>
> After pressing it, it will stop the thread and the button
Jürgen Spitzmüller wrote:
> and the two Browse buttons need different
> accelerators)
Sorry, this is only in the German localization.
Jürgen
Vincent van Ravesteijn - TNW wrote:
> >- with my qt 4.2.x the frame "Options" appears empty
>
> I don't really have a clue how to solve it. Isn't it the problem of the
> "Expanding" sizepolicy that is not understood by qt4.2 ?
I think you need to set a GridLayout to the GroupBox (also, the two Ra
>I do not like much this business of loading buffers without
>showing them, actually... And with this browse button, I feel
>the feature feels more like an additional utility than a part
>of the program.
That's why it is in the Tools menu ;).
>BTW, when I click on Cancel, the button just turns to
>Other remarks in no particular order:
>
>- with my qt 4.2.x the frame "Options" appears empty
>
I don't really have a clue how to solve it. Isn't it the problem of the
"Expanding" sizepolicy that is not understood by qt4.2 ?
>- Could we have nice names displayed instead of full names?
I don'
Jean-Marc Lasgouttes wrote:
> Pavel Sanda writes:
>
> > Abdelrazak Younes wrote:
> >> Maybe keep a Browse button in order to load another document in the
> >> background. And the combo box displaying the list of open buffers would be
> >> automatically updated; and maybe a coffee when you are a
Pavel Sanda writes:
> Abdelrazak Younes wrote:
>> Maybe keep a Browse button in order to load another document in the
>> background. And the combo box displaying the list of open buffers would be
>> automatically updated; and maybe a coffee when you are at it...
>
> i would also let the browse
Abdelrazak Younes writes:
> Maybe keep a Browse button in order to load another document in the
> background. And the combo box displaying the list of open buffers
> would be automatically updated; and maybe a coffee when you are at
> it...
I do not like much this business of loading buffers with
Abdelrazak Younes wrote:
> Maybe keep a Browse button in order to load another document in the
> background. And the combo box displaying the list of open buffers would be
> automatically updated; and maybe a coffee when you are at it...
i would also let the browse button live. and instead of ba
On 01/22/2010 04:48 PM, Jean-Marc Lasgouttes wrote:
Jean-Marc Lasgouttes writes:
Vincent van Ravesteijn writes:
Is it fixed at r33137 ?
Yes, and valgrind does not complain anymore. My small files still give
wrong output, though (duplicated first line)
Other remarks
1 - 100 of 214 matches
Mail list logo
