On 4/17/07, Richard Heck <[EMAIL PROTECTED]> wrote:
I don't know exactly what's going on here, but I think I can solve the
problem. I also think it's a QT bug, not ours.
OK, my qt4 is 4.2.3:
% rpm -qa | grep qt4
qt4-4.2.3-3.fc6.1
qt4-devel-4.2.3-3.fc6.1
qt4-x11-4.2.3-3.fc6.1
-
Richard Heck wrote:
> Leaving the slider enabled is harmless: It doesn't do anything if
> there's nothing in the TOC, anyway.
Sure? It used to crash LyX (that' why we disabled it).
> Try the patch below, then.
Unfortunately, it does not work for me.
Jürgen
On 4/16/07, Uwe Stöhr <[EMAIL PROTECTED]> wrote:
> I just notice that if I open or close a collapsable inset, the file is
> not marked dirty. Is this intentional?
This is bug 2993:
http://bugzilla.lyx.org/show_bug.cgi?id=2993
The patch is simple enough. If there is no objection, it will go i
Ich schrieb:
>>OK, I'll provide an improved version of my patch that also shows
the code for \big etc.
>
> Hum... then why not just take my patch?
because you display LFUNS ;-).
Just joking. Your patch is good as it cleans up the whole code. I take it and built in what I like
to have
Paul A. Rubin schrieb:
- fix bug that configure-script was not run after the installer told
you that the configuration will now start
Don't know about this, since the installer for the previous snapshot ran
the configuration script just fine for me.
The bug opnly occured when you had Pyth
> I just notice that if I open or close a collapsable inset, the file is
> not marked dirty. Is this intentional?
This is bug 2993:
http://bugzilla.lyx.org/show_bug.cgi?id=2993
regards Uwe
Cleaned up the patch and changed some details: non-brace arguments
are shifted now as well into macros.
Schimmi
dynamicmacros.patch
Description: Binary data
PGP.sig
Description: Signierter Teil der Nachricht
Am Samstag, 14. April 2007 15:23 schrieb Abdelrazak Younes:
> Georg Baum wrote:
> > Am Freitag, 13. April 2007 21:38 schrieb Abdelrazak Younes:
> >> Georg Baum wrote:
> >>
> I don't share your pessimism, especially
> if we are to compare current SVN with the state of 1.4.0 when it was
>
On Mon, Apr 16, 2007 at 10:10:15PM +0200, Stefan Schimanski wrote:
> Am 16.04.2007 um 20:35 schrieb Andre Poenitz:
> >>>arises: How would that schem cope with 'unknown'
>
> An unknown macro is a macro of arity zero.
>
> >>>\a 12
> >>>
> >>>unless you know whether \a is defined as \def\a#1#2{#1+#2
The patch will be submitted tomorrow if there is no objection.
Sorry, the patch is in. I have to apply this patch to debug another one.
I will revert the patch if needed.
Bo
moveToPosition would fail to move to a closed inset
To reproduce this:
1. open a new doc
2. inset a note
3. save bookmark 1
4. close inset
5. move to bookmark 1, crash.
Attached patch examines DocIterator obtained from top_id in
moveToPosition. If an inset is not HIGHLY_EDITABLE, the cursor wi
Hello LyXers,
I don't want to bother you every week with a new snapshot but this time I need some testers for the
improved installer:
Version LyX 1.5svn-15-04-2007
- LyX 1.5svn from 15-04-2007
- reworked paragraph dialog
- more cleanups of the math delimiter and the document settings dial
Richard Heck wrote:
> I don't know exactly what's going on here, but I think I can solve the
> problem. I also think it's a QT bug, not ours.
>
> At first I thought there must be some kind of event loop. But adding
> some lyxerr's to GuiApplication::notify() showed me that it wasn't:
> You'd get a
I don't know exactly what's going on here, but I think I can solve the
problem. I also think it's a QT bug, not ours.
At first I thought there must be some kind of event loop. But adding
some lyxerr's to GuiApplication::notify() showed me that it wasn't:
You'd get a paint event for the slider, bu
Am 16.04.2007 um 20:35 schrieb Andre Poenitz:
arises: How would that schem cope with 'unknown'
An unknown macro is a macro of arity zero.
\a 12
unless you know whether \a is defined as \def\a#1#2{#1+#2} or \def\a
{x}?
Well, my assumption is that every argument is a brace, like in
\newcomma
I just notice that if I open or close a collapsable inset, the file is
not marked dirty. Is this intentional?
Cheers,
Bo
On 4/14/07, Bo Peng <[EMAIL PROTECTED]> wrote:
I just submitted the following patch.
It is wrong not to save the whole cursor stack as lastFilePos, and it
is more wrong to save top (innermost) level pit and pos. As a result,
if you quit lyx with cursor in an inset, lastFilePos will save pit/pos
Am Sonntag, 15. April 2007 23:46 schrieb Dov Feldstern:
> Dov Feldstern wrote:
>
> > Also --- and
> > this would be much easier --- the whitespace should be marked as
> > belonging to the foreign language (with the blue underline) --- just
> > that would already go a long way towards making it
On Mon, Apr 16, 2007 at 08:00:57PM +0200, Stefan Schimanski wrote:
> >I haven't looked at the patch, just at this description here. A
> >question
> >arises: How would that schem cope with 'unknown'
> >
> >\a 12
> >
> >unless you know whether \a is defined as \def\a#1#2{#1+#2} or \def\a
> >{x}?
>
> Well, The fact that not many users do not know about LFUNs does not mean that
they should not
> know. I at least am glad to know what LyX is really doing. For example, all
the LFUN lanched via
> the menu are displayed in the status bar. And you know that we have a
mini-buffer that is useful
>
>>You don't need to install the fonts. On Windows, just add the fonts from
the SVN folder
>> /lib/fonts to LyX install folder under ~\Resources\fonts and then
reconfigure.
> But we shouldn't have to do that. In-build-tree LyX knows about lib/ and uses
that as a resource
> for ui files etc.
Am Dienstag, 10. April 2007 14:04 schrieb Jean-Marc Lasgouttes:
> > "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
>
> >> I think that perhaps \inputencoding commands are not allowed inside
> >> a \section? and I vaguely recall having been through this same
> >> issue once before, and your
I haven't looked at the patch, just at this description here. A
question
arises: How would that schem cope with 'unknown'
\a 12
unless you know whether \a is defined as \def\a#1#2{#1+#2} or \def\a
{x}?
Well, my assumption is that every argument is a brace, like in
\newcommand{\foo}[n]{...
On Mon, Apr 16, 2007 at 12:42:26PM -0500, Bo Peng wrote:
> >It can be converted to a DocIterator by using
> >StableDocIterator::asDocIterator(...).
>
> My concern is the usability of this restored dociterator. For example,
> How well this restored dociterator handles removed or closed (in the
> ca
On Mon, Apr 16, 2007 at 04:59:40PM +0200, Stefan Schimanski wrote:
> I was thinking about tracking the dependency graph of used macros in
> a macro definition and look for loops. Then return a harmless
> MathMacro with some error string in that case. But that would
> probably be much more com
On Mon, Apr 16, 2007 at 04:53:44PM +0200, Abdelrazak Younes wrote:
> Stefan Schimanski wrote:
> >Hi!
> >
> >Here is a proposal to fix the crash when you try to define macros with
> >self references, i.e. by using \foo inside of the definition of \foo
> >itself (or by any other definitional loop):
It can be converted to a DocIterator by using
StableDocIterator::asDocIterator(...).
My concern is the usability of this restored dociterator. For example,
How well this restored dociterator handles removed or closed (in the
case of collapsable insets) insets?
Cheers,
Bo
On Mon, Apr 16, 2007 at 04:32:59PM +0200, Abdelrazak Younes wrote:
> Stefan Schimanski wrote:
> >>OK, got it from bugzilla.
> >
> >Sorry, forgot to attach it to the mail as well.
> >
> >>Good detective work! I feel stupid for not seeing that at the first
> >>glance :-(
> >>Do you have SVN access?
dim_.wid = 0;
- Dimension d;
- //BufferView & bv = *mi.base.bv;
- //Buffer const & buf = *bv.buffer();
- for (size_t i = 0, n = size(); i != n; ++i) {
+ Dimension d;
+ for (size_t i = 0; i != size(); ++i) {
What's wrong with the 'n'?
+
On Mon, Apr 16, 2007 at 11:17:18AM +0200, Stefan Schimanski wrote:
> Hi!
>
> I was investigating the macro system for the last days to find a way
> to implement it in a cleaner way than it is at the moment. The main
> well known problems with the current approach:
>
> 1. Macro definitions are
Am 16.04.2007 um 16:53 schrieb Abdelrazak Younes:
Stefan Schimanski wrote:
Hi!
Here is a proposal to fix the crash when you try to define macros
with self references, i.e. by using \foo inside of the definition
of \foo itself (or by any other definitional loop):
http://bugzilla.lyx.org/
Stefan Schimanski wrote:
Hi!
Here is a proposal to fix the crash when you try to define macros with
self references, i.e. by using \foo inside of the definition of \foo
itself (or by any other definitional loop):
http://bugzilla.lyx.org/attachment.cgi?id=1548&action=view
It basically impl
Stefan Schimanski wrote:
OK, got it from bugzilla.
Sorry, forgot to attach it to the mail as well.
Good detective work! I feel stupid for not seeing that at the first
glance :-(
Do you have SVN access?
No, no write access.
OK, I'll commit the patch for you. Please consider asking for it.
Lyx lets us mark words/sentences with another language - very useful for
spellchecking of multi-lingual documents.
This works well for words in "standard text", and cause problems
otherwise. The typical symptom is that view->PDF fails with an
"Undefined control sequence"
Using foregin langu
OK, got it from bugzilla.
Sorry, forgot to attach it to the mail as well.
Good detective work! I feel stupid for not seeing that at the first
glance :-(
Do you have SVN access?
No, no write access.
There's still some drawing problem though but I think this is
orthogonal to this patch: t
Stefan Schimanski wrote:
Hi!
Another macro bug fixed: http://bugzilla.lyx.org/show_bug.cgi?id=3449
OK, got it from bugzilla. Good detective work! I feel stupid for not
seeing that at the first glance :-(
Do you have SVN access?
There's still some drawing problem though but I think this is
Stefan Schimanski wrote:
Hi!
Another macro bug fixed: http://bugzilla.lyx.org/show_bug.cgi?id=3449
The problem was no metric calculation was done for insets on cursor
movement. Of course scrolling or entering character caused the missing
metric calls, hence the described behavior in the bug re
Stefan Schimanski wrote:
Hi!
Another macro bug fixed: http://bugzilla.lyx.org/show_bug.cgi?id=3449
What do you mean fixed? Do you have a patch?
If yes, please it to the list.
Abdel.
Hi!
Another macro bug fixed: http://bugzilla.lyx.org/show_bug.cgi?id=3449
The problem was no metric calculation was done for insets on cursor
movement. Of course scrolling or entering character caused the
missing metric calls, hence the described behavior in the bug report.
I had first trie
Uwe Stöhr wrote:
>>> I guess Peter is missing some fonts. Uwe just added the font
to SVN but
>>> maybe those are not loaded correctly because of path problems
when
>>> running "in build tree" (which is the only option with CMake).
>>>
>>> I have the Bokoma fonts ins
Uwe Stöhr wrote:
> Note that my patch shows the LFUN argument not the LateX code, so it
won't show the \left and
> \right. For example it will show:
>
> { }
> { Vert
> bigl \{ bigr \Vert
>
> I think it is useful to teach the user about the LFUNs. So it is not
strictly about LateX; I
>
>>> I guess Peter is missing some fonts. Uwe just added the font to SVN
but
>>> maybe those are not loaded correctly because of path problems when
>>> running "in build tree" (which is the only option with CMake).
>>>
>>> I have the Bokoma fonts installed system wide so I
> Note that my patch shows the LFUN argument not the LateX code, so it won't
show the \left and
> \right. For example it will show:
>
> { }
> { Vert
> bigl \{ bigr \Vert
>
> I think it is useful to teach the user about the LFUNs. So it is not strictly
about LateX; I
> should probably rename the
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Leuven, E. wrote:
> Attached your patched patch. I've only
> added includes to iconpalette.C/.h.
thanks i've added them here as well
> But some symbols are missing, I only see
> the latex command, see png.
i don't see this, perhaps something w
Uwe Stöhr wrote:
>>3. 3-4 weeks after beta 2 we discuss the release again to have a
definite release date.
> I think we should set the release date now, independently from the
remaining bugs. I propose
> approximatively one month after beta 2, say May 15.
Please let us wait for the re
Uwe Stöhr wrote:
>>Your patch doesn't fix the bugs and it gives out e.g. "\{\}"
(always both commands).
> Yes, that's the point. They will see all options at the same time
before pressing "Insert". You
> think the user needs a SMALL info, I think otherwise that the user
should need the
> IMO we should not wait an additional month. We should do that now.
Of course!
>>3. 3-4 weeks after beta 2 we discuss the release again to have a definite
release date.
> I think we should set the release date now, independently from the remaining
bugs. I propose
> approximatively one mo
>>Your patch doesn't fix the bugs and it gives out e.g. "\{\}" (always both
commands).
> Yes, that's the point. They will see all options at the same time before pressing
"Insert". You
> think the user needs a SMALL info, I think otherwise that the user should need the full info. The
> sma
Abdelrazak Younes wrote:
> Leuven, E. wrote:
>> > Attached your patched patch. I've only
>> > added includes to iconpalette.C/.h.
>>
>> thanks i've added them here as well
>>
>> > But some symbols are missing, I only see
>> > the latex command, see png.
>>
>> i don't see this, perhaps something
> I'm not following this... Can I just assume that nothing needs to be changed
on the search links
> that I put on the wiki pages?
Yes, the links are correct.
Uwe
Leuven, E. wrote:
>> Attached your patched patch. I've only
>> added includes to iconpalette.C/.h.
>
> thanks i've added them here as well
>
>> But some symbols are missing, I only see
>> the latex command, see png.
>
> i don't see this, perhaps something went still wrong with stdtoolbars.inc ?
> Are the pixmaps used in the panel autogenerated?
no, they are available ...
Leuven, E. wrote:
I guess Peter is missing some fonts. Uwe just added the font to SVN but
maybe those are not loaded correctly because of path problems when
running "in build tree" (which is the only option with CMake).
ok, but then these symbols won't show up with math panel either...
Are t
> I guess Peter is missing some fonts. Uwe just added the font to SVN but
> maybe those are not loaded correctly because of path problems when
> running "in build tree" (which is the only option with CMake).
ok, but then these symbols won't show up with math panel either...
Leuven, E. wrote:
> Attached your patched patch. I've only
> added includes to iconpalette.C/.h.
thanks i've added them here as well
> But some symbols are missing, I only see
> the latex command, see png.
i don't see this, perhaps something went still wrong with stdtoolbars.inc ?
I gues
Stefan Schimanski wrote:
Hi!
Here is a proposal to fix the crash when you try to define macros with
self references, i.e. by using \foo inside of the definition of \foo
itself (or by any other definitional loop):
Hello Stephan,
Sorry I can't comment on your patch (cause I am totally ignoran
Uwe Stöhr wrote:
I'm a bit worried about how you discussed this topic, so let me propose
a plan:
1. We've made a HUGE step forward toward LyX 1.5.0 since beta 1, so put
the beta 2 out now!
We need more people to test our efforts in bugfixing. That's why I
publish new 1.5svn-versions
for
Hi!
I was investigating the macro system for the last days to find a way
to implement it in a cleaner way than it is at the moment. The main
well known problems with the current approach:
1. Macro definitions are shared among all open document, i.e. one big
global macro table
2. Macro ins
Jürgen Spitzmüller wrote:
John McCabe-Dansted wrote:
I am getting ToC crashes again. This is with SVN of 16 Apr on FC6.
I don't get the crash, but I see the (dramatic) slowdown.
I've been investigating this bug for a long time without success :-(
Do you have a backtrace?
On windows, the
Uwe Stöhr wrote:
> That won't work with big delimiters. Besides, that's not what I was
talking about, I meant to
> display the full LFUN argument.
Fro what is this needed? The users needs a SMALL info, so just giving
out e.g. "\bigg\{" should be enough. Even \right and \left is in my
opinio
On Sun, 15 Apr 2007, Uwe Stöhr wrote:
I think you need to add a check on version. As an example bug 2965 is
listed in the critical list even though it is not present in 1.5svn.
The the fixedintrunk flag was not set. I did this now for this bug. But
for the critical bugs, the LyX-version doe
Hi!
Here is a proposal to fix the crash when you try to define macros
with self references, i.e. by using \foo inside of the definition of
\foo itself (or by any other definitional loop):
http://bugzilla.lyx.org/attachment.cgi?id=1548&action=view
It basically implements a locking counter
On Sun, 15 Apr 2007, Angus Leeming wrote:
<[EMAIL PROTECTED]> writes:
http://wiki.lyx.org/Devel/BuglistsForLyX150
The page takes a while to load, and I've only verified that it works in
Opera 7.3/Linux.
Doesn't work with IE 7.0.5730.11.
Does work with Firefox 1.5.0.6.
Nor does it work with
63 matches
Mail list logo
