Johnathan Burchill wrote:
> This patch addresses bug#1277, and adds functionality to ct.
> The bug-fix addresses pasting while change-tracking. The main modification
> is the "Change" parameter that has been added to moveItem().
>
> The new functionality is to let the user break a paragraph within
Bennett Helm wrote:
>> Try changing the ss.tellp() bit to something comparing iterators:
>
> That seems to do the trick! (See output below.) I'll do more testing
> tomorrow.
Excellent! Thanks for your patience.
--
Angus
> Merhaba!
Merhaba :)
> Changing the buffer code would imply a change from 8bit chars to
> 16/32bit chars. So this is a solution that will take a lot of time.
I see.
> OTOH producing utf-8 latex would be much simpler. Since it all goes
> through an ostream, one would only need a latin-9 to utf
On Feb 14, 2005, at 2:51 PM, Angus Leeming wrote:
Well that seems pretty conclusive then. setEnvPath loops over the
elements
but doesn't do anything with them.
Try changing the ss.tellp() bit to something comparing iterators:
That seems to do the trick! (See output below.) I'll do more testing
> Do you want me to take your translation in cvs for now? We do not have
> a turkish translation distributed now, because it was out of date. We
> normally have a policy of keeping only language with half messages
> translated, but we can make an exception if you are committed to
> update it.
I w
Andreas Vox wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
>> Well that seems pretty conclusive then. setEnvPath loops over the
>> elements but doesn't do anything with them.
>>
>> Try changing the ss.tellp() bit to something comparing iterators:
>
> Sorry, but that doesn't look like the
Michael Schmitt <[EMAIL PROTECTED]> writes:
>
> > The new teTeX 3.0 has a way (or two) to handle spaces. Something like
> >\include{"My Files"}
> >
> > So probably we should drop all safety checks concerning this and just
> > include the quotes whenever LyX creates such a TeX command.
>
> Th
Angus Leeming <[EMAIL PROTECTED]> writes:
> Well that seems pretty conclusive then. setEnvPath loops over the elements
> but doesn't do anything with them.
>
> Try changing the ss.tellp() bit to something comparing iterators:
Sorry, but that doesn't look like the logical conclusion.
Is ss.str()
The new teTeX 3.0 has a way (or two) to handle spaces. Something like
\include{"My Files"}
So probably we should drop all safety checks concerning this and just
include the quotes whenever LyX creates such a TeX command.
That is not enough; see the following snippet from the MikTeX documentation
Michael> Hello, AFAICS, we have a problem with the generation of po
Michael> files. LyX 1.3.6 comprises 2838 messages, while the po files
Michael> of LyX 1.4.0 have only 1866 entries! I had a closer look at
Michael> the po files and noticed that, e.g., the message "Senseless:
Michael> " is no longe
Bennett Helm wrote:
> On Feb 14, 2005, at 12:45 PM, Angus Leeming wrote:
>
>> Angus Leeming wrote:
>>> Thanks, Bennett. What that tells me is that the problem doesn't lie in
>>> PutEnv at all. It lies in the code that calls PutEnv.
>>>
>>> I have a nasty feeling that this, or something like it, w
On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote:
> > "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> Andre> On Thu, Feb 10, 2005 at 09:50:40PM +0100, Jean-Marc Lasgouttes
> Andre> wrote:
> >> We agreed in Chemnitz to delay the 1.5 branch until 1.4.1 is out. I
> >>
On Mon, Feb 14, 2005 at 12:38:07PM +0100, Jean-Marc Lasgouttes wrote:
> I am not sure. I see there is a MathCursor::normalize(). Isn't it the
> same thing?
I think it is. But I have neither source handy right now.
Andre'
On Mon, Feb 14, 2005 at 02:54:08PM +, Angus Leeming wrote:
> The MSVC compiler is complaining about math_rootinset.C:
>
> \lyx\lyx-devel\src\mathed\math_rootinset.C(86) : warning C4805: '==' :
> unsafe mix of type 'DocIterator::idx_type' and type 'bool' in operation
>
> It seems to me that t
On Mon, Feb 14, 2005 at 01:21:24PM +0100, Lars Gullik Bjønnes wrote:
> | - return Point(x,y);
> | + --x;
>
> Why this extra line and not just:
>
> x += dit.bottom().text()->cursorX(dit.bottom()) - 1;
No specific reason other than that correction should not be there at
all. The cusor looks mu
On Mon, Feb 14, 2005 at 10:04:29AM +0100, Jean-Marc Lasgouttes wrote:
> Andre> My cvs copy is from Thursday.
>
> Andre> Nevertheless that patch of mine should be applied too, as it
> Andre> makes the whole dispatch process a bit more robust.
>
> What about 1.3.x? Do these patches apply? It seems
On Mon, Feb 14, 2005 at 04:47:12PM +0200, Martin Vermeer wrote:
> 1) new document
> 2) insert math inset
> 3) inside math inset: insert text box (Control-M)
> 4) click inside this box.
mbox is broken in many ways right now.
Andre'
Hi folks,
Please find attached three files: a change-tracking patch, and a new inset
declaration and implementation.
Use -p0 from the top-level source dir for applying the patch.
insetnewparagraph.{C,h} need to be placed in src/insets/.
This patch addresses bug#1277, and adds functionality to
On Feb 14, 2005, at 12:45 PM, Angus Leeming wrote:
Angus Leeming wrote:
Thanks, Bennett. What that tells me is that the problem doesn't lie in
PutEnv at all. It lies in the code that calls PutEnv.
I have a nasty feeling that this, or something like it, will fix the
problem (still in src/support/fil
Am Montag, 14. Februar 2005 15:58 schrieb Angus Leeming:
> I think you miss the point. He's talking about the display of the
> "Navigate" menu entries which are populated from the contents of the
> buffer. A "real" solution might be to have menu items that derive from
> QContentPane, but it see
On Mon, Feb 14, 2005 at 05:53:38PM +0100, Hartmut Haase wrote:
> JMarc,
> after the last 2 updates (today and 3 days ago) I got the following error
> messages:
>
> make[3]: Entering directory `/home/haase/Software/lyx-devel/src/client'
> if g++ -DHAVE_CONFIG_H -I. -I. -I../../src -I./../ -I../../
Bennett Helm wrote:
> On Feb 14, 2005, at 12:31 PM, Angus Leeming wrote:
>
>> I have a nasty feeling that this, or something like it, will fix the
>> problem (still in src/support/filetools.C)
>>
>> void setEnvPath(string const & name, vector const & env)
>> {
>> char const separator(o
Andreas Vox wrote:
> I think the
>
> void method() {
> if (in_method) return;
> in_method = true;
> // do something
> in_method = false;
> }
>
> pattern is quite simple and safe. It just protects the method against
> involuntary indirect recursive calls.
I agree entirely
On Feb 14, 2005, at 12:31 PM, Angus Leeming wrote:
I have a nasty feeling that this, or something like it, will fix the
problem (still in src/support/filetools.C)
void setEnvPath(string const & name, vector const & env)
{
char const separator(os::path_separator());
std::ostrings
> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
Michael> Hello, AFAICS, we have a problem with the generation of po
Michael> files. LyX 1.3.6 comprises 2838 messages, while the po files
Michael> of LyX 1.4.0 have only 1866 entries! I had a closer look at
Michael> the po files and no
Angus Leeming wrote:
> Bennett Helm wrote:
>
>>
>> On Feb 14, 2005, at 11:11 AM, Angus Leeming wrote:
>>
>>> Let's try and refine this. Do things work correctly if you use putenv
>>> rather than setenv? (Ie, maybe the problem lies with (our use of) gcc
>>> 2.95's setenv routine.)
>>>
>>> Could
Luke Simon wrote:
> The main editor pane of Lyx flickers when scrolling up or down using the
> scrollbar. It really destroys the visual "polish" of this great
> application.
I see this too. No idea what to do about it, though.
Jürgen
Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Andreas Vox wrote:
>
> I'm just
> thinking of the future when we have multiple LyX windows, each with their
> own set of dialogs.
>
> One improvement over your original patch would be to make 'showing' a
> member of the src/frontends/Dialogs
Bennett Helm wrote:
>
> On Feb 14, 2005, at 11:11 AM, Angus Leeming wrote:
>
>> Let's try and refine this. Do things work correctly if you use putenv
>> rather than setenv? (Ie, maybe the problem lies with (our use of) gcc
>> 2.95's setenv routine.)
>>
>> Could you alter this function in src/sup
Hartmut Haase wrote:
> JMarc,
> after the last 2 updates (today and 3 days ago) I got the following error
> messages:
>
> make[3]: Entering directory `/home/haase/Software/lyx-devel/src/client'
> if g++ -DHAVE_CONFIG_H -I. -I. -I../../src -I./../ -I../../boost -W
> -Wall
> -I/usr/X11R6/include
Andreas Vox wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
>>
>> Question: do you need to protect the call to "find_or_build"?
>
> Probably find_or_build needs to be protected from being called
> while a second show() hasn't finished yet. Maybe not.
> Doesn't matter because you have to pr
On Feb 14, 2005, at 11:11 AM, Angus Leeming wrote:
Let's try and refine this. Do things work correctly if you use putenv
rather than setenv? (Ie, maybe the problem lies with (our use of) gcc
2.95's setenv routine.)
Could you alter this function in src/support/filetools.C? Do it in two
steps. Ie, ad
JMarc,
after the last 2 updates (today and 3 days ago) I got the following error
messages:
make[3]: Entering directory `/home/haase/Software/lyx-devel/src/client'
if g++ -DHAVE_CONFIG_H -I. -I. -I../../src -I./../ -I../../boost -W -Wall
-I/usr/X11R6/include -g -O -fno-exceptions -MT debug.o -
Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Question: do you need to protect the call to "find_or_build"?
Probably find_or_build needs to be protected from being called
while a second show() hasn't finished yet. Maybe not.
Doesn't matter because you have to prevent the following call
to dialo
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> On Thu, Feb 10, 2005 at 09:50:40PM +0100, Jean-Marc Lasgouttes
Andre> wrote:
>> We agreed in Chemnitz to delay the 1.5 branch until 1.4.1 is out. I
>> hope this still holds...
Andre> Apropos Chemnitz. Where do we go this year?
If
Bennett Helm wrote:
>> So the fault lies in "prependEnvPath". Yet Andreas says that this
>> (identical) code works perfectly for him when using the 1.4.x version.
>> I'm a bit baffled.
>
> It works perfectly for me, too, in 1.4.x. (I use gcc version 3.1 for
> lyx-1.4, but 2.95.2 for lyx-1.3.
Ok.
On Feb 14, 2005, at 10:42 AM, Angus Leeming wrote:
So the fault lies in "prependEnvPath". Yet Andreas says that this
(identical) code works perfectly for him when using the 1.4.x version.
I'm
a bit baffled.
It works perfectly for me, too, in 1.4.x. (I use gcc version 3.1 for
lyx-1.4, but 2.95.2
Bennett Helm wrote:
> My output (confirming my suspicions -- at least I'm not crazy!):
>
> Env var "PATH", "/usr/bin:/bin:/usr/sbin:/sbin:/Users/bennett", is
> prepended with "/Applications/LyX-136.app/Contents/MacOS/"
> result:
How interesting! I've erased the PATH environment variable!
> lyxrc
Andreas Vox wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
>> Being more explicit:
>
> Thanks!
>
>> std::cout << _("my dynamic string") << '\n';
>
> I was confused there. So "dynamic string" is short for
> "string in a dynamic context".
> I first thought you had to treat static strin
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote: It won't apply as such. What is
Juergen> the equivalent of cursor::normalize() in 1.3?
>> I am not sure. I see there is a MathCursor::normalize(). Isn't it
>> the same thing?
Juergen> Yes, it
Jean-Marc Lasgouttes wrote:
> Angus> The MSVC compiler is complaining about math_rootinset.C:
> Angus> \lyx\lyx-devel\src\mathed\math_rootinset.C(86) : warning C4805:
> Angus> '==' : unsafe mix of type 'DocIterator::idx_type' and type
> Angus> 'bool' in operation
>
> Angus> It seems to me that the
On Feb 13, 2005, at 12:35 PM, Angus Leeming wrote:
Here it results in output to the console:
lyxrc.path_prefix is /foo/bar
Env var "PATH",
"/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/
angus/bin",
is prepended with "/foo/bar"
result:
/foo/bar:/usr/kerberos/bin:/us
Andreas Vox wrote:
>> It seems to me that the global 'bool showing' should actually be a
>> one-per-dialog variable.
> ...
>> Do I miss anything?
>>
> The "showing" flag only protects the call to show() itself, therefore it
> should be named "opening".
> The dialog is shown between the call to show
> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
Michael> Dear Jean-Marc, enclosed please find a patch for LyX 1.3. It
Michael> includes yet another update to de.po and fixes some text
Michael> messages in the cross reference dialog (the term "label"
Michael> should be used instead o
Angus Leeming <[EMAIL PROTECTED]> writes:
> Being more explicit:
Thanks!
> std::cout << _("my dynamic string") << '\n';
I was confused there. So "dynamic string" is short for
"string in a dynamic context".
I first thought you had to treat static string constants
and calculated strings
> "Gürer" == Gürer Özen <[EMAIL PROTECTED]> writes:
Gürer> Hi,
Gürer> I'm a developer on Uludag Project (a national Linux
Gürer> distribution targeted at Turkish users and government,
Gürer> http://www.uludag.org.tr/en/ ).
Gürer> We are using LyX/LaTeX for our documents and distribute it wit
Here's another obvious fix. Ok to commit?
\lyx\lyx-devel\src\insets\insetlatexaccent.C(431) : warning C4309:
'argument' : truncation of constant value
Index: src/insets/insetlatexaccent.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-dev
Jean-Marc Lasgouttes wrote:
> Juergen> It won't apply as such. What is the equivalent of
> Juergen> cursor::normalize() in 1.3?
>
> I am not sure. I see there is a MathCursor::normalize(). Isn't it the
> same thing?
Yes, it's exactly the same.
But I have no idea where the normalize() call should g
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> The MSVC compiler is complaining about math_rootinset.C:
Angus> \lyx\lyx-devel\src\mathed\math_rootinset.C(86) : warning C4805:
Angus> '==' : unsafe mix of type 'DocIterator::idx_type' and type
Angus> 'bool' in operation
Angus> It
Angus Leeming <[EMAIL PROTECTED]> writes:
> I don't think that the patch should be committed as it is, although it has
> enabled Andreas to work out what was going wrong --- good detective work,
> Andreas!
Thanks! :-)
>
> It seems to me that the global 'bool showing' should actually be a
>
Andreas Vox wrote:
> > Difficult to describe. Seems like the workarea gets a huge descend while
> > the scrollbar isn't updated and anything you type is invisible. Quite
> > weird.
>
> Maybe another problem which is avoided by double-buffering in Aqua?
Probably
> What platform do you use?
Linux
Andreas Vox wrote:
>> > | I think there are two solutions for this problem. Best one is
>> > | modifying buffer code to accept and understand utf8. This will make
>> > | it possible to generate and use utf8 encoded files (something we aim
>> > | in our distribution).
>
> Merhaba!
>
> Changing the
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> Andreas Vox wrote:
> > What kind of mess-up? I can't see anything here
> > (MacAqua)
>
> Difficult to describe. Seems like the workarea gets a huge descend while the
> scrollbar isn't updated and anything you type is invisible. Quite weird.
Ma
The MSVC compiler is complaining about math_rootinset.C:
\lyx\lyx-devel\src\mathed\math_rootinset.C(86) : warning C4805: '==' :
unsafe mix of type 'DocIterator::idx_type' and type 'bool' in operation
It seems to me that the fix is both obvious and makes the code more
transparent. Ok to commit?
On Fri, 2005-02-11 at 03:11, John Levon wrote:
> Since I can't access bugzilla. I only tried for about 10 minutes so please
> don't think this is exhaustive. On the whole, the current CVS isn't too bad. A
> couple of bad assertions, but after a few of these are fixed, I think we can
> let Michael S
Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Lars Gullik BjÃnnes wrote:
>
> > GÃrer Ãzen <[EMAIL PROTECTED]> writes:
> >
> > | I think there are two solutions for this problem. Best one is modifying
> > | buffer code to accept and understand utf8. This will make it possible
> > | to generate a
On 8.02.05, [EMAIL PROTECTED] wrote:
> Regarding the ability to create "hypertext" links in LyX documents
> (originated in a discussion on the lyx-docs list)
>
> Jean-Marc wrote:
> > chr> * Link to another part of the same document (this we have
> > chr> already, right?)
> >
> > Yes, but this mea
Jean-Marc Lasgouttes wrote:
>
> When I have errors in latex, the nice errors dialog pops up. If I
> close it, how can I get it back? I cannot find it in the menus.
>
> Where should it be added? Tools? Documents? View?
>
> JMarc
It looks like the same dialog is used for multiple different cases
Jean-Marc Lasgouttes wrote:
> When I have errors in latex, the nice errors dialog pops up. If I
> close it, how can I get it back? I cannot find it in the menus.
>
> Where should it be added? Tools? Documents? View?
I'd say Documents (because the LaTeX Logfile also resides there).
Jürgen
When I have errors in latex, the nice errors dialog pops up. If I
close it, how can I get it back? I cannot find it in the menus.
Where should it be added? Tools? Documents? View?
JMarc
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Fri, Feb 11, 2005 at 06:33:14PM +0100, [EMAIL PROTECTED] wrote:
>> When the cursor is to the very right of an inset, it's drawn outside of the
>> red
>> box. It looks like it's not in the inset: very, very confusing.
>
| Patch attached. Please apply.
Jean-Marc Lasgouttes wrote:
> The following patch fixes several *GOTO* lfuns:
Excellent.
> It would be nice to have some testing before committing it.
Yes. Unfortunately, I will not have time this week.
Regards,
Jürgen
On Fri, Feb 11, 2005 at 06:42:01PM +0100, [EMAIL PROTECTED] wrote:
> http://bugzilla.lyx.org/show_bug.cgi?id=1804
>
>Summary: inlined ERTs can have zero width
>Product: LyX
>Version: 1.4.0cvs
> Platform: Other
> OS/Version: other
>
On Fri, Feb 11, 2005 at 06:33:14PM +0100, [EMAIL PROTECTED] wrote:
> When the cursor is to the very right of an inset, it's drawn outside of the
> red
> box. It looks like it's not in the inset: very, very confusing.
Patch attached. Please apply.
--- bufferview_funcs.C.orig 2005-02-13 07:43
To one of the probolems recently reported here (double click on
collapsable label)
[I have mail problems, so this may have been on the list already]
Please commit.
Andre'
--- insetcollapsable.C.orig 2005-02-12 16:17:06.0 +0100
+++ insetcollapsable.C 2005-02-12 16:18:35.0
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
It looks nice. But I agree some testing would be nice.
--
Lgb
On Monday 14 February 2005 11:38, Angus Leeming wrote:
> Jose' Matos wrote:
> > This patch fixes bug 1816.
> >
> > I don't understand why the pextra_widthp argument goes in a separate
> > line, but if it happens then this patch takes that into account.
> >
> > The patch seems clean, and safe, so I
The following patch fixes several *GOTO* lfuns:
- use proper inset iterators to be able to move inside/outside insets
- use BufferView::setCursor so that insets are open as needed
- move the handling of these LFUNS from LyXText to BufferView::Pimpl
- move gotoInset to bufferview_funcs.C.
It w
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote:
>> What about 1.3.x? Do these patches apply? It seems that at least
>> Juergen's patch makes sense...
Juergen> It won't apply as such. What is the equivalent of
Juergen> cursor::normalize() in
Jose' Matos wrote:
> This patch fixes bug 1816.
>
> I don't understand why the pextra_widthp argument goes in a separate
> line, but if it happens then this patch takes that into account.
>
> The patch seems clean, and safe, so I will apply it it. Any objection?
No objection, but a couple of sug
On Saturday 12 February 2005 16:59, Georg Baum wrote:
> The advantage of this would be that it is very easy to implement. And
> more flexible (i. e. I can export one document with pngs and another one
> with bmps).
I agree. The mechanism is already in place let us use it. :-)
> Georg
--
José
This patch fixes bug 1816.
I don't understand why the pextra_widthp argument goes in a separate line,
but if it happens then this patch takes that into account.
The patch seems clean, and safe, so I will apply it it. Any objection?
--
José Abílio
Index: lyx_1_2.py
==
Juergen Spitzmueller wrote:
> John Levon wrote:
>> > The attached patch just ignores subsequent calls to show if the old
>> > one isn't finished yet.
>>
>> I think this is pretty much the right thing to do.
>
> So should this patch be committed?
I don't think that the patch should be committed a
John Levon wrote:
> > The attached patch just ignores subsequent calls to show if the old one
> > isn't finished yet.
>
> I think this is pretty much the right thing to do.
So should this patch be committed?
Jürgen
BTW I think valgrind's Helgrind seems to be useful to track down such
problems.
Jean-Marc Lasgouttes wrote:
> What about 1.3.x? Do these patches apply? It seems that at least
> Juergen's patch makes sense...
It won't apply as such. What is the equivalent of cursor::normalize() in 1.3?
Jürgen
Lars Gullik Bjønnes wrote:
> Gürer Özen <[EMAIL PROTECTED]> writes:
>
> | I think there are two solutions for this problem. Best one is modifying
> | buffer code to accept and understand utf8. This will make it possible
> | to generate and use utf8 encoded files (something we aim in our
> | distr
Gürer Özen <[EMAIL PROTECTED]> writes:
| I think there are two solutions for this problem. Best one is modifying
| buffer code to accept and understand utf8. This will make it possible to
| generate and use utf8 encoded files (something we aim in our
| distribution). Other one is doing charset con
Georg Baum wrote:
>> - I copied the Alert message verbatim from another place. What do I have
>>to do if I introduce new internationalized strings? Any suggestions
>>for a better error message?
>
> Simply enclose the string with _(). It will appear in the po files the
> next time they are
Andreas Vox wrote:
>> Can you be more explicit? What fails? If LyX is refusing to do
>> something, can you track down the place in the code? (I've only got so
>> much time, y'know...)
>
> Something like this (found in Exporter::Export())
>
> } else if (contains(buffer->filePath(), ' ')) {
> Alert
Andreas Vox wrote:
> I thought about that. I changed the methods in Exporter to create non-
> existing directories (I thought first about your advice to add an
> "addExternalDirectory" method, but when I looked at the code this
> looked simpler).
It is simpler indeed. But "addExternalDirectory" e
Jean-Marc Lasgouttes wrote:
> It seems that would be useful to do the same for 1.3.x.
>
> Can you do it?
I'll do it this evening.
Georg
Hi,
I'm a developer on Uludag Project (a national Linux distribution
targeted at Turkish users and government,
http://www.uludag.org.tr/en/ ).
We are using LyX/LaTeX for our documents and distribute it with our live
CD. I've made a Turkish translation (mostly to qt frontend) available at
http://
Asger Alstrup wrote:
> Martin Vermeer wrote:
>> See attached patch, which has been on the list for a few days.
>
> Technically, you posted the first version of this before the freeze was
> announced, so I think it's fair to put it in, also considering the number
> of revisions you have made.
Ple
On Mon, Feb 14, 2005 at 10:14:57AM +0100, Asger Alstrup wrote:
> Hi,
>
> - do we release ...
> - often enough:
> - too often:
How diplomatic...
- Martin
pgp1q40SBGzyJ.pgp
Description: PGP signature
Hi,
It is very popular these days to do user surveys, so I figured I'd
copy'n'paste the monotone survey and /s/monotone/LyX/, and change it a bit.
We can then send to the user's list, or if someone is really nice, turn it
into a web survey instead.
I know the focus right now is to get 1.4.0 out
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> On Sun, Feb 13, 2005 at 11:37:00AM +0100, Juergen Spitzmueller
Andre> wrote:
>> Andre Poenitz wrote: > Aehm. I can't apply the patch I send myself.
>> So it would be nice if > someone checked and committed it.
>>
>> I thought I fix
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> The last item of tex_graphics is "", not "last_item".
It seems that would be useful to do the same for 1.3.x.
Can you do it?
JMarc
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> - LCursor & cur = bv_->cursor();
Andre> + LCursor & cur = cursor_;
Andre> Looks like even more potential for improvements...
Yes. I had to stop at some point, but there are so many things that
should be cleaned up that I got very
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Am Freitag, 11. Februar 2005 22:19 schrieb Andre Poenitz:
>> Please add a FIXME line.
Georg> Like the attached? I must admit that I don't really know what
Georg> the FIXME should say, because some lines later it is clearly
Georg> docu
> "Luke" == Luke Simon <[EMAIL PROTECTED]> writes:
Luke> Fedora Core 3 with apt for RPM, Gnome, and the LyX 1.3.5 with
Luke> the Qt frontend. I posted the RPM that I got the LyX binaries
Luke> from earlier.
I cannot reproduce that here: readhat 9 (yes, I know...), qt 3.1, Xeon
2.8GHz.
JMarc
Martin Vermeer wrote:
See attached patch, which has been on the list for a few days.
Technically, you posted the first version of this before the freeze was
announced, so I think it's fair to put it in, also considering the number
of revisions you have made.
Regards,
Asger
Andre Poenitz wrote:
> Attached patch fixes a crach when changing a font over a range
> containing a nested math inset.
>
> I am not sure whether nested insets should be immune to font changes in
> general. It is the right thing for e.g. footnotes, but I am not sure
> about the general case.
>
> I
92 matches
Mail list logo
