Re: \S

2023-07-27 Thread Richard Kimberly Heck
On 7/27/23 17:00, Enrico Forestieri wrote: On Thu, Jul 27, 2023 at 01:27:09AM -0400, Richard Kimberly Heck wrote: This is really a special case, so I'm inclined just to handle it as one via the attached hack-ish patch. But maybe someone else knows how to fix Encodings::fromLaTeXCommand? It

Re: \S

2023-07-27 Thread Enrico Forestieri
On Thu, Jul 27, 2023 at 01:27:09AM -0400, Richard Kimberly Heck wrote: This is really a special case, so I'm inclined just to handle it as one via the attached hack-ish patch. But maybe someone else knows how to fix Encodings::fromLaTeXCommand? It has been a long time and I don't remember an

Re: s/.*_moc.cpp/moc_\1.cpp

2008-11-14 Thread Andre Poenitz
On Fri, Nov 14, 2008 at 02:55:26PM +0100, Jürgen Spitzmüller wrote: > Andre Poenitz wrote: > > Jean-Marc had the same idea. > > Excellent. Now the fun can begin, I guess :-) > > BTW feel free to backport fixes to the new branch while you are sober. > Just put them in if you are confident enough (

Re: s/.*_moc.cpp/moc_\1.cpp

2008-11-14 Thread Jürgen Spitzmüller
Andre Poenitz wrote: > Jean-Marc had the same idea. Excellent. Now the fun can begin, I guess :-) BTW feel free to backport fixes to the new branch while you are sober. Just put them in if you are confident enough (this only applies for the meeting, of course). Jürgen

Re: s/.*_moc.cpp/moc_\1.cpp

2008-11-14 Thread Andre Poenitz
On Fri, Nov 14, 2008 at 02:40:06PM +0100, Jürgen Spitzmüller wrote: > Andre Poenitz wrote: > > Unless someone complains very loudly soon I'll change the naming of > > our generated moc files to the "more standard" moc_*.cpp scheme. > > Makes interaction with one of the tools I'd like to use simpler

Re: s/.*_moc.cpp/moc_\1.cpp

2008-11-14 Thread Jürgen Spitzmüller
Andre Poenitz wrote: > Unless someone complains very loudly soon I'll change the naming of > our generated moc files to the "more standard" moc_*.cpp scheme. > Makes interaction with one of the tools I'd like to use simpler. But please remember to create an 1_6_X branch before breaking trunk into

Re: S+R already fixed

2002-07-25 Thread Jean-Marc Lasgouttes
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes: Juergen> Michael Schmitt wrote: >> Hi, I prepared two small test cases for s+r problems. The first one >> is related to mathed (math text is replaced endlessly), the second >> one demonstrates that "replace all" sometimes misses some >>

Re: S+R already fixed

2002-07-25 Thread Juergen Vigna
Michael Schmitt wrote: > Hi, > > I prepared two small test cases for s+r problems. The first one is > related to mathed (math text is replaced endlessly), the second one > demonstrates that "replace all" sometimes misses some occurrences. It > happens very seldom but it is easily reproducible.

Re: S+R already fixed

2002-07-10 Thread Andre Poenitz
On Wed, Jul 10, 2002 at 03:22:36PM +0200, Juergen Vigna wrote: > >it (this bug sounds familiar to me). > > I think that this is matheds problem Andre could you have a look at this? As I can reproduce this without using any math it does not look like my fault. Search for 'ss' in the attached doc.

Re: S+R already fixed

2002-07-10 Thread Juergen Vigna
Michael Schmitt wrote: Hi Michael! > just some short information (I have not managed to prepare nice-looking test > cases yet). > > First of all: The new S+R code is very fast. It seems to work in most cases > but nonetheless there are at least two problems: #:O) > 1. Given a math formular in

Re: S+R already fixed

2002-07-09 Thread Juergen Vigna
Michael Schmitt wrote: > I will patch my 1.2.1cvs this evening. Since I use LyX excessively at the > moment, we could agree on waiting for a week or so and see whether I get > into trouble. When processing smaller docs, I could run valgrind to make > sure that S+R does not corrupt the memory. Goo

Re: S+R already fixed

2002-07-09 Thread Michael Schmitt
Hi Jean Marc, > Juergen> Jean-Marc if you think you want this let me know and I apply > Juergen> it with some ChangeLog entries :) > > What does this patch do? It is a bit large for my taste? How confident > are you that it actually works? I will patch my 1.2.1cvs this evening. Since I use LyX

Re: S+R already fixed

2002-07-09 Thread Jean-Marc Lasgouttes
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes: Juergen> Michael Schmitt wrote: >> Hi Jürgen, Juergen> Hi Michael! >> I tend you use 1.2.x instead 1.3.0. How big is your S+R patch? Can >> it be back-ported to 1.2.1cvs? If you can send me a patch against >> 1.2.1cvs, I will give it

Re: S+R already fixed

2002-07-09 Thread Juergen Vigna
Michael Schmitt wrote: > Hi Jürgen, Hi Michael! > I tend you use 1.2.x instead 1.3.0. How big is your S+R patch? Can it be > back-ported to 1.2.1cvs? If you can send me a patch against 1.2.1cvs, I > will give it a try. If it takes too long for you to prepare such a > patch, you could give me

Re: S+R already fixed

2002-07-09 Thread Andre Poenitz
On Tue, Jul 09, 2002 at 09:55:31AM +0200, Juergen Vigna wrote: > Well I had a look into the sourcecode (as I had a spare minute) > and discovered that the changes to S+R have been already commited > by Lars quite some time ago. Strange nobody noticed??? Did the > patch not work or is nobody using

Re: S-C-T for update postscript

2001-02-01 Thread Jean-Marc Lasgouttes
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes: Dekel> On Wed, Jan 31, 2001 at 05:10:28PM +0100, Jean-Marc Lasgouttes Dekel> wrote: >> > "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes: >> Richard> I assume this means shift-control-t ? It doesn't work, but Richard> alt-v u

Re: S-C-T for update postscript

2001-01-31 Thread Dekel Tsur
On Wed, Jan 31, 2001 at 05:10:28PM +0100, Jean-Marc Lasgouttes wrote: > > "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes: > > Richard> I assume this means shift-control-t ? It doesn't work, but > Richard> alt-v u t (though the menu) does. > > Yes, it is shift-control-t, and it wor

Re: S-C-T for update postscript

2001-01-31 Thread Jean-Marc Lasgouttes
> "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes: Richard> I assume this means shift-control-t ? It doesn't work, but Richard> alt-v u t (though the menu) does. Yes, it is shift-control-t, and it works well here. JMarc