daniel dabbled,
> I don't think searching backwards is that important. I have to admit I
> often use it (not only in (K)Lyx), but only to go back one position
> because I clicked too fast in forward search.
yikes! it's rather important, in figuring out where a word most
recently came up (issues
On Fre, 08 Jan 1999 Daniel Naber wrote:
>Jean-Marc Lasgouttes wrote:
>
>> I like the feature, but shouldn't it continue backwards if we were
>> searching backwards? We should keep a bool saying in which direction
>> the last search was, I think.
>
>I don't think searching backwards is that importa
Jean-Marc Lasgouttes wrote:
> I like the feature, but shouldn't it continue backwards if we were
> searching backwards? We should keep a bool saying in which direction
> the last search was, I think.
I don't think searching backwards is that important. I have to admit I
often use it (not only in
On Fre, 08 Jan 1999 Jean-Marc Lasgouttes wrote:
>> "Jochen" == Jochen Kuepper <[EMAIL PROTECTED]> writes:
>
>Jochen> Hi, Daniel Naber send in a patch to KLyX to find forward on
>Jochen> each replace in the Find&Replace dialog. We sent that patch to
>Jochen> Matthias to judge wether we want to
> "Jochen" == Jochen Kuepper <[EMAIL PROTECTED]> writes:
Jochen> Hi, Daniel Naber send in a patch to KLyX to find forward on
Jochen> each replace in the Find&Replace dialog. We sent that patch to
Jochen> Matthias to judge wether we want to put it in or not. ( It
Jochen> seems he is still thin
[Auto search after replace.]
> What do you think about that feature ?
I think it should go in. Jean-Marc?
Greets,
Asger
