Re: Can't search 'ö'

[Peter Dyballa]

Am 16.04.2005 um 18:35 schrieb Stefan Monnier:

> > Launch freshly compiled GNU Emacs from CVS: src/emacs -q -g 80x45 &
>
> In the lines I quoted of your message, it said "with your patch".
> I can reproduce the problem you describe when the patch is not 
> applied, what
> I can't reproduce is the problem you seem to say is introduce by my 
> patch.
> I thought it was clear from the patch I quoted.  Please explain how I 
> could
> have made it more clear.

I did not pay that much attention to your quote, since I started both 
descriptions the same way. I thought you would need a description of 
how the error happens in a regular Emacs.

Besides this error I made another mistake: I did not install the 
patched Emacs from yesterday! 'make clean' removed it and my 
description references indeed a standard GNU Emacs from CVS from 
yesterday morning. I re-installed the patched keyboard.c and re-made 
GNU Emacs half an hour ago. This version too does not take care whether 
it's launched from an ISO 8859-1 or ISO 8859-15 or UTF-8 environment. 
Here is what happens when launched as 'env LANG=de_DE.ISO8859-1 
LC_CTYPE=de_DE.ISO8859-1 Quellen/Emacs_CVS/emacs/src/emacs -q -g 80x45 
&' from Terminal from my home directory:

Check unify-8859-on-decoding-mode's value: C-h v unif TAB de TAB RET   
==> nil
Open the directory with test files: C-x d ~/ISO TAB RET
Click with mouse-1 the ISO 8859-15 test file   ==> opens writable in 
new buffer
I-search that accented e: C-s ´e RET   ==> success, é found!
Close that buffer: C-x k
Toggle unify-8859-on-decoding-mode's value: M-x unif TAB de TAB RET
Check unify-8859-on-decoding-mode's value: C-h v unif TAB de TAB RET   
==> t
Click with mouse-1 the ISO 8859-15 test file   ==> opens writable in 
new buffer
I-search that accented e: C-s ´e   ==> error message: Failing I-search: 
é


Can you too see that toggling unify-8859-on-decoding-mode does not 
change the behaviour of isearch when the text buffer is left open 
during invocation of unify-8859-on-decoding-mode? I.e. success both 
times, before and after the change? Is that a correct behaviour, or is 
it another fault?

--
Greetings

  Pete