P.S. Stefan, just to make sure I really do understand: what I
hadn't understood until now is "so how does just setting the
boundary, without changing the position, make the cursor move?". I
think now I get it: when the cursor drawing is done, it looks at
the boundary: if the boundary is
Angus Leeming <[EMAIL PROTECTED]> writes:
| +#ifdef DEBUG
| +bool bound = cur.boundary();
| +int rowpos = cur.textRow().pos();
| +int pos = cur.pos();
| +bool sep = cur.paragraph().isSeparator(cur.pos() - 1);
| +bool newline =
Start a new article, choose beamer layout, write a, select, edit->text
style -> alert, move cursor before it, delete, lyx crashes with the
following backtrace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 182907542720 (LWP 9472)]
0x in ?? ()
(gdb)
Herbert Voss wrote:
> \newcommand*\DEL{{\fontencoding{U}\fontfamily{ascii}\selectfont\char127}}
perhaps \providecommand (in case the ascii package is already loaded).
Jürgen
Stefan Schimanski wrote:
Here it is. As I wrote already, the screen was redrawn every time the
cursor was moved up or down. But this is only needed if
bv().checkDepm(...) does some work. Now the behavior is as in beta 3 again.
Stefan
I don't really experience the problem (slowness) in the
Bo Peng schrieb:
Start a new article, choose beamer layout, write a, select, edit->text
style -> alert, move cursor before it, delete, lyx crashes with the
following backtrace:
I cannot reproduce this in (current) rev18579.
Bernhard
Andre Poenitz wrote:
> On Wed, May 30, 2007 at 03:26:04PM +0200, Alfredo Braunstein wrote:
>> Just a though... why do we need the invalidation signals at all?
>> ...couldn't we go in fixIfBroken from the top to the tip of the
>> DocIterator checking that there is an inset an the given position in
I cannot reproduce this in (current) rev18579.
I find that removal of every collapsable inset leads to crash. Must be
something that is introduced recently.
E.g. insert ERT, enter a, move cursor to the right, backspace, lyx crashes.
I am using r18579, under linux.
Bo
As i posted in bugzilla there is no crash anymore in current svn. One remaining issue is that undo
does not work as it should. The attached patch addresses this, but it surely affects other parts of
the code (everything that uses grabAndEraseSelection()), so can someone tell if it is safe to
The subject says everything. The old implementation had zero support
for RTL.
http://bugzilla.lyx.org/show_bug.cgi?id=3550
Stefan
Index: src/Text.cpp
===
--- src/Text.cpp(Revision 18579)
+++ src/Text.cpp
Juergen Spitzmueller wrote:
> Herbert Voss wrote:
>
>> \newcommand*\DEL{{\fontencoding{U}\fontfamily{ascii}\selectfont\char127}}
>
> perhaps \providecommand (in case the ascii package is already loaded).
but only in this case, the other way round works ... :-)
Herbert
Bo Peng schrieb:
I cannot reproduce this in (current) rev18579.
I find that removal of every collapsable inset leads to crash. Must be
something that is introduced recently.
E.g. insert ERT, enter a, move cursor to the right, backspace, lyx crashes.
As for the other problem: no crash here
Stefan Schimanski wrote:
So moving forward (pos+1) but setting the boundary to true will not
register a movement; and staying at the same position, but changing
the boundary back to false, *will* appear to move. Is this correct?
The other way round: boundary=true => behind the char pos-1.
As for the other problem: no crash here (WinXP)
I can also confirm that lyx/win works fine. Can any linux people
confirm this? Note that I am using a 64bit machine.
Cheers,
Bo
Bo Peng wrote:
>> I cannot reproduce this in (current) rev18579.
> I find that removal of every collapsable inset leads to crash. Must be
> something that is introduced recently.
>
> E.g. insert ERT, enter a, move cursor to the right, backspace, lyx
> crashes.
>
> I am using r18579, under linux.
Richard Heck wrote:
> Bo Peng wrote:
>
>>> I cannot reproduce this in (current) rev18579.
>>>
>> I find that removal of every collapsable inset leads to crash. Must be
>> something that is introduced recently.
>>
>> E.g. insert ERT, enter a, move cursor to the right, backspace, lyx
>>
>> I find that removal of every collapsable inset leads to crash. Must be
>> something that is introduced recently.
I randomly revert to r18530, crash, r18500 no crash. I roughly
remember that we upgraded boost at that time...
Bo
The attached patch addresses these bugs
http://bugzilla.lyx.org/show_bug.cgi?id=3741
http://bugzilla.lyx.org/show_bug.cgi?id=3756
in a way that is compatible with earlier discussion with Abdel. Here's
what it does:
* In the "Available" list, double clicking or hitting Enter adds the
On Wed, May 30, 2007 at 08:55:34PM +0200, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | +#ifdef DEBUG
> | +bool bound = cur.boundary();
> | +int rowpos = cur.textRow().pos();
> | +int pos = cur.pos();
> | +bool sep =
Extended it a bit:
Index: src/DocIterator.h
===
--- src/DocIterator.h (Revision 18580)
+++ src/DocIterator.h (Arbeitskopie)
@@ -233,19 +233,42 @@
private:
/**
-* When the cursor position is i, is the cursor after
Hi!
Attached find a patch to fix the following:
Type a long line with no spaces (aa) until the line breaks
because it's too wide, and continue a bit. Then type a space, and then
b... until the moves to a new line.
Recall, there is no space in the middle of the , but
Type a long line with no spaces (aa) until the line breaks
because it's too wide, and continue a bit. Then type a space, and
then b... until the moves to a new line.
Recall, there is no space in the middle of the , but there is a
space between and .
So,
Stefan Schimanski wrote:
Extended it a bit:
Index: src/DocIterator.h
===
--- src/DocIterator.h(Revision 18580)
+++ src/DocIterator.h(Arbeitskopie)
@@ -233,19 +233,42 @@
private:
/**
- * When the cursor position is
> yes, that's right, but is save to use
>
> \newcommand*\oline{\ensuremath{\overline{\phantom{A
But then the line is a bit too long when I compare:
_
\ensuremath{\underline{\overline{\phantom{A
>> 2302 HOUSE: ⌂
>
Stefan Schimanski wrote:
Type a long line with no spaces (aa) until the line breaks
because it's too wide, and continue a bit. Then type a space, and then
b... until the moves to a new line.
Recall, there is no space in the middle of the , but there is a
space between
Martin,
could you please check this beamer layout?
# Theorems and such section
Style Corollary
LatexName corollary}%{
LabelString "Corollary_"
End
Is this "_" a typo? Should it be dropped or replaced by a space?
Michael
Dov Feldstern wrote:
Stefan Schimanski wrote:
There's also a separate case, but it doesn't manifest itself in cursor
movement (in terms of affecting the number of keystrokes between
positions):
if I'm between emph and normal text, and type a character, should it be
emph or not? Well, if I'm
Dov Feldstern wrote:
Dov Feldstern wrote:
Stefan Schimanski wrote:
There's also a separate case, but it doesn't manifest itself in cursor
movement (in terms of affecting the number of keystrokes between
positions):
if I'm between emph and normal text, and type a character, should it
be emph
Dov Feldstern wrote:
Why should that correct? The condition will never be true because no
character is newline and separator at the same time.
Hmm... right... maybe some of those should be "or"s. But obviously
they're not really necessary at all... That's what I tried saying a few
days
> "Richard" == Richard Heck <[EMAIL PROTECTED]> writes:
Richard> In particular, do we presume Qt 4.1?
Yes, 4.1 or greater.
JMarc
On Wed, May 30, 2007 at 09:27:18PM +0200, Alfredo Braunstein wrote:
> Andre Poenitz wrote:
>
> > On Wed, May 30, 2007 at 03:26:04PM +0200, Alfredo Braunstein wrote:
> >> Just a though... why do we need the invalidation signals at all?
> >> ...couldn't we go in fixIfBroken from the top to the tip
Am 30.05.2007 um 22:53 schrieb Dov Feldstern:
Dov Feldstern wrote:
Why should that correct? The condition will never be true because
no character is newline and separator at the same time.
Hmm... right... maybe some of those should be "or"s. But obviously
they're not really necessary at
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> In this specific case I am a lot happier with the "ifdef DEBUG"
Lars> case.
Or with LYXERR, like the rest of the code does.
JMarc
[EMAIL PROTECTED] schrieb:
Author: schmitt
Date: Wed May 30 22:57:17 2007
New Revision: 18581
Modified: lyx-devel/trunk/src/insets/InsetListingsParams.cpp
URL:
http://www.lyx.org/trac/file/lyx-devel/trunk/src/insets/InsetListingsParams.cpp?rev=18581
I've just installed beta3 on debian lenny and everything works perfectly on
new documents. However, when I open an old document then math preview fails
with:
pplatex: Process input file 4lyxpreview.dvi
pplatex: Copy data to 4lyxpreview.dvi
This is dvips(k) 5.95b Copyright 2005 Radical Eye
On Wed, May 30, 2007 at 03:59:15PM -0400, Richard Heck wrote:
> + if (obj == availableLV) {
> + if (event->type() != QEvent::KeyPress)
> + return QObject::eventFilter(obj, event);
> + QKeyEvent * keyEvent = static_cast(event);
> + int
Stefan Schimanski wrote:
Am 30.05.2007 um 22:53 schrieb Dov Feldstern:
Dov Feldstern wrote:
Why should that correct? The condition will never be true because no
character is newline and separator at the same time.
Hmm... right... maybe some of those should be "or"s. But obviously
they're
Bo Peng wrote:
Actually, most of my frames are just a big itermize. So you choose begin
frame, put a title, switch to itemize, add items. Now if you choose
'begin
frame', guess what you've got? begin frame inside an item. blahh.
You only need to insert 'endframe' environment at the end
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
>
> Bo Peng wrote:
>
> >> while translating the listing dialog messages, I found a few minor
> >> problems:
> >
> > I am not familiar with either qt or gettext so I will leave these to
> > others.
>
> It might be because those strings are
On Wed, May 30, 2007 at 11:12:32PM +0300, Dov Feldstern wrote:
> Index: lyx-devel/src/Text2.cpp
> ===
> --- lyx-devel.orig/src/Text2.cpp 2007-05-30 22:49:48.0 +0300
> +++ lyx-devel/src/Text2.cpp 2007-05-30
Rainer Dorsch wrote:
Hello,
I am not often working with tables in LyX, but I noticed two usability issues
when inserting rows or columns:
1) I searched first in table settings (opened on right click on table), then
used google to find it in the edit menu.
2) I inserted a row a time,
Andre Poenitz wrote:
I am also uncertain whether
cur.paragraph().isNewline(cur.pos() + 1) &&
cur.paragraph().isLineSeparator(cur.pos() + 1) &&
cur.paragraph().isSeparator(cur.pos() + 1))
makes much sense.
Right, we're past that stage
Dov Feldstern wrote:
Stefan Schimanski wrote:
Am 30.05.2007 um 22:53 schrieb Dov Feldstern:
Dov Feldstern wrote:
Why should that correct? The condition will never be true because
no character is newline and separator at the same time.
Hmm... right... maybe some of those should be "or"s.
Richard Heck <[EMAIL PROTECTED]> writes:
> > What is best? We have "No documents open!" now, the principle of least
> > effort would advise to keep it like that...
> >
> I guess I prefer the singular. The plural suggests that documentS should
> have been open---that this was the expected
On Thu, May 31, 2007 at 12:14:25AM +0300, Dov Feldstern wrote:
> Andre Poenitz wrote:
> >
> >I am also uncertain whether
> >
> > cur.paragraph().isNewline(cur.pos() + 1) &&
> > cur.paragraph().isLineSeparator(cur.pos() + 1) &&
> >
Andre Poenitz wrote:
On Wed, May 30, 2007 at 05:46:46PM +0200, Abdelrazak Younes wrote:
Jean-Marc Lasgouttes wrote:
These problems do not mean that you implemented badly, just that it is
a bigger task than you thought.
An by the way, the additional work required to properly handling these
> "Dov" == Dov Feldstern <[EMAIL PROTECTED]> writes:
Dov> Please, could someone respond regarding this patch from Elazar?
Dov> It fixes issue (3) of
Dov> http://bugzilla.lyx.org/show_bug.cgi?id=3551, which is a
Dov> regression.
Dov> It works. The concept makes sense. The implementation --
Andre Poenitz wrote:
On Wed, May 30, 2007 at 05:44:39PM +0200, Abdelrazak Younes wrote:
Jean-Marc Lasgouttes wrote:
Abdelrazak> I won't say random because as you found out you can
Abdelrazak> predict the behaviour.
After I have edited during 10 minutes in one part of the document, the
> I think ",," is o.k. (i.e., will be transformed into a double quotation
> mark).
But \quotedblbase would be safe for every case and document language, so I put
this in.
>> Could you please fix these two entries for me (0x201e and 0x201a)?
I did this now and added two more symbols.
>> We
[EMAIL PROTECTED] writes:
| Author: sts
| Date: Wed May 30 21:38:22 2007
| New Revision: 18580
|
| URL: http://www.lyx.org/trac/changeset/18580
| Log:
| * avoid redraw if possible (OK by Abdel and Dov)
|
| Modified:
| lyx-devel/trunk/src/Cursor.cpp
| lyx-devel/trunk/src/Cursor.h
|
On Wednesday 30 May 2007 22:29:12 Jean-Marc Lasgouttes wrote:
> Dov> So please, can we have it okayed and committed?
>
> José?
>
> JMarc
OK.
--
José Abílio
Am 30.05.2007 um 23:29 schrieb Jean-Marc Lasgouttes:
"Dov" == Dov Feldstern <[EMAIL PROTECTED]> writes:
Dov> Please, could someone respond regarding this patch from Elazar?
Dov> It fixes issue (3) of
Dov> http://bugzilla.lyx.org/show_bug.cgi?id=3551, which is a
Dov> regression.
Dov> It
Andre Poenitz wrote:
On Wed, May 30, 2007 at 02:30:37PM +0200, Abdelrazak Younes wrote:
Alfredo Braunstein wrote:
Abdelrazak Younes wrote:
I am not sure that registering every single DocIterator would be any
more efficient that my signal/slot solution. At the end you will have to
go through
Am 30.05.2007 um 23:32 schrieb Lars Gullik Bjønnes:
[EMAIL PROTECTED] writes:
| Author: sts
| Date: Wed May 30 21:38:22 2007
| New Revision: 18580
|
| URL: http://www.lyx.org/trac/changeset/18580
| Log:
| * avoid redraw if possible (OK by Abdel and Dov)
|
| Modified:
|
Am 30.05.2007 um 23:32 schrieb José Matos:
On Wednesday 30 May 2007 22:29:12 Jean-Marc Lasgouttes wrote:
Dov> So please, can we have it okayed and committed?
José?
JMarc
OK.
See my comment please. I think I have a case where the proposed
solution is wrong. But I cannot implement it
On Wednesday 30 May 2007 18:59:24 Richard Heck wrote:
> This patch was discussed a bit here. Angus suggested the problem was
> with signals from the QComboBox causing changes in the ButtonController,
> but I've investigated that and that does not seem to be the issue. In
> any event, this fixes
Andre Poenitz wrote:
On Wed, May 30, 2007 at 08:37:09AM +0200, Abdelrazak Younes wrote:
Andre Poenitz wrote:
On Tue, May 29, 2007 at 10:11:16PM +0200, Stefan Schimanski wrote:
I enabled stdlib-debug and then were surprised about the slowness.
Some profiling was full of signal/slot stuff in
On 5/30/07, Bo Peng <[EMAIL PROTECTED]> wrote:
> >> I find that removal of every collapsable inset leads to crash. Must be
> >> something that is introduced recently.
Abdel,
It is suspected that your destroyed() signal crashes lyx in this case,
maybe a problem with my gcc 3.4.6. I remember
Otherwise, '?something ' will not match anything.
I guess, a trim is already applied. I updated the code for the situations '? something' and attached the patch. However, It does not cover the situations '?some thing'.
I used trim (), but since the string is already trimmed, rtrim() is
Angus Leeming wrote:
> Have I given you a clue,
yes, thanks. Only thing is that _() is a docstring nowadays (that's why I
used N_() which is still a const * char).
Jürgen
Andre Poenitz wrote:
> On Wed, May 30, 2007 at 03:59:15PM -0400, Richard Heck wrote:
>
>> +if (obj == availableLV) {
>> +if (event->type() != QEvent::KeyPress)
>> +return QObject::eventFilter(obj, event);
>> +QKeyEvent * keyEvent =
It is suspected that your destroyed() signal crashes lyx in this case,
maybe a problem with my gcc 3.4.6. I remember that a similar crash
that is only reproducible on gcc 3.4 was fixed by adding disconnect()
somewhere a while ago. Maybe this is the case again.
FYI, lyx compiled with gcc4 does
Stefan Schimanski wrote:
The subject says everything. The old implementation had zero support for
RTL.
http://bugzilla.lyx.org/show_bug.cgi?id=3550
Stefan
Works correctly! Thanks again, Stefan!
Jean-Marc Lasgouttes
Wed, 30 May 2007 13:59:11 -0700
> "Richard" == Richard Heck <[EMAIL PROTECTED]> writes:
Richard> In particular, do we presume Qt 4.1?
Yes, 4.1 or greater.
JMarc
On Mac I would recommend QT4.3 (released yesterday I think) to avoid
the nasty bug 3307.
Anders
Stefan Schimanski wrote:
Am 30.05.2007 um 23:32 schrieb José Matos:
On Wednesday 30 May 2007 22:29:12 Jean-Marc Lasgouttes wrote:
Dov> So please, can we have it okayed and committed?
José?
JMarc
OK.
See my comment please. I think I have a case where the proposed solution
is wrong. But
On Wed, May 30, 2007 at 06:07:50PM -0400, Richard Heck wrote:
> Andre Poenitz wrote:
> > On Wed, May 30, 2007 at 03:59:15PM -0400, Richard Heck wrote:
> >
> >> + if (obj == availableLV) {
> >> + if (event->type() != QEvent::KeyPress)
> >> + return
Dov Feldstern wrote:
Dov Feldstern wrote:
Dov Feldstern wrote:
Stefan Schimanski wrote:
There's also a separate case, but it doesn't manifest itself in
cursor movement (in terms of affecting the number of keystrokes
between positions):
if I'm between emph and normal text, and type a
Bernhard Roider wrote:
As i posted in bugzilla there is no crash anymore in current svn.
This is perhaps due to my fix of the Cursor::fixIfBroken() method. You
know the horrible commit I've done to support my pet feature...
Abdel.
Bo Peng wrote:
On 5/30/07, Bo Peng <[EMAIL PROTECTED]>
wrote:
> >> I find that removal of every collapsable inset leads to crash.
Must be
> >> something that is introduced recently.
Abdel,
It is suspected that your destroyed() signal crashes lyx in this case,
maybe a problem with my gcc
Uwe Stöhr wrote:
>> yes, that's right, but is save to use
>>
>> \newcommand*\oline{\ensuremath{\overline{\phantom{A
>
> But then the line is a bit too long when I compare:
>
> _
> \ensuremath{\underline{\overline{\phantom{A
replace the A bei I
>
>
>>> 2302 HOUSE:
On Wed, May 30, 2007 at 11:39:16PM +0200, Abdelrazak Younes wrote:
> I proposed the patch last week and it was available for comment for a
> few days. I even had some help from Angus so I don't think this thread
> went unoticed. Look for something with [FULLY WORKING PATCH] in the subject.
Andre Poenitz wrote:
The variables are not only unused, they are pointless as well.
The problem was that MSVC allegedly did not compile the code in the
#ifdef branch as long as the variable was not used.
I am pretty sure that MSVC does not misbehave that way although I have no
way to check
Dov Feldstern wrote:
Stefan Schimanski wrote:
The subject says everything. The old implementation had zero support
for RTL.
http://bugzilla.lyx.org/show_bug.cgi?id=3550
Stefan
Works correctly! Thanks again, Stefan!
Ummm, see bugzilla for a problem which still exists...
[This should be applied after the patch in
http://permalink.gmane.org/gmane.editors.lyx.devel/86074, which fixes
bug 3754.]
Okay, you guys (Stefan and Andre') are correct, as always ;) .
We really don't need the boundary almost anywhere. The comment on
boundary_ in DocIterator.h is (almost)
Uwe Stöhr schrieb:
>> 2302 HOUSE: ⌂
>
\newcommand*\DEL{{\fontencoding{U}\fontfamily{ascii}\selectfont\char127}}
This and all other commands you sent lead to completely different
characters here on my MiKTeX-system.
Now I get it:
I have to use \usepackage{ascii} and then
{\ascii\DEL}
I
Oops, I realized I sent this only to Andre instead of to the entire list.
-- Forwarded message --
From: Stephen Hartke
Date: May 29, 2007 3:14 PM
Subject: Re: Effect of Certain Keys in Math Mode
To: Andre Poenitz
On 5/29/07, Stephen Hartke <[EMAIL PROTECTED]> wrote:
>
Hello,
I have made several failed attempt to submit a Korean translation of menus and
messages, etc.
Not knowing why, I can now only guess the file is too big to attach in the mail
and thus I've uploaded the file at the following ftp site,
ftp://cellular.phys.pusan.ac.kr/CJK-LyX/ko.po
I hope
Bo Peng wrote:
It is suspected that your destroyed() signal crashes lyx in this case,
maybe a problem with my gcc 3.4.6. I remember that a similar crash
that is only reproducible on gcc 3.4 was fixed by adding disconnect()
somewhere a while ago. Maybe this is the case again.
FYI, lyx compiled
On May 30, 2007, at 6:33 PM, Anders Ekberg wrote:
Jean-Marc Lasgouttes
Wed, 30 May 2007 13:59:11 -0700
> "Richard" == Richard Heck <[EMAIL PROTECTED]> writes:
Richard> In particular, do we presume Qt 4.1?
Yes, 4.1 or greater.
JMarc
On Mac I would recommend QT4.3 (released yesterday I
Anders Ekberg wrote:
Jean-Marc Lasgouttes
Wed, 30 May 2007 13:59:11 -0700
> "Richard" == Richard Heck <[EMAIL PROTECTED]> writes:
Richard> In particular, do we presume Qt 4.1?
Yes, 4.1 or greater.
On Mac I would recommend QT4.3 (released yesterday I think) to avoid
the nasty bug 3307.
On Wed, May 30, 2007 at 11:47:12PM +0200, Abdelrazak Younes wrote:
> Andre Poenitz wrote:
> >>The variables are not only unused, they are pointless as well.
> >
> >The problem was that MSVC allegedly did not compile the code in the
> >#ifdef branch as long as the variable was not used.
> >
> >I am
On Thu, May 31, 2007 at 02:29:38AM +0300, Dov Feldstern wrote:
> At least cursorLeft and cursorRight are much simpler now...
I have no idea whether the patch is sound, but I certainly like the
structure...
Andre'
If I start a new document with text "asdf asdf asdf adfs", and execute
the command buffer:
command-sequence bookmark-save before-spellcheck; buffer-begin;
dialog-show spellchecker;
Then the spellchecker will ignore the first "asdf". The spell checker
will pick it up if manually move the
On 31 maj 2007, at 03.20, RGH wrote:
Anders Ekberg wrote:
Jean-Marc Lasgouttes
Wed, 30 May 2007 13:59:11 -0700
> "Richard" == Richard Heck <[EMAIL PROTECTED]> writes:
Richard> In particular, do we presume Qt 4.1?
Yes, 4.1 or greater.
On Mac I would recommend QT4.3 (released yesterday I
301 - 384 of 384 matches
Mail list logo
