From: Michael Piotrowski <mxp@dynalabs.de>
To: info-gnus-english@gnu.org
Subject: Re: incremental search and Umlauts
Date: Fri, 20 Apr 2007 11:29:34 +0200 [thread overview]
Message-ID: <x6r6qftmv5.fsf@eurus.mag.dynalabs.de> (raw)
In-Reply-To: <871wik0xq8.fsf@debian.IGP>
On 2007-04-17, "Andreas Goesele" <goesele@hfph.mwn.de> wrote:
> When I do an incremental search in xemacs' gnus' summary window and
> use umlauts I get an error message (e.g. adiaeresis not defined) and
> the search doesn't.
>
> Some time ago I found/got a tip for simple key combination which would
> enable the use of umlauts during incremental search.
I don't know about a keyboard command, but I just played around a bit,
and the following code seems to work:
--8<---------------cut here---------------start------------->8---
(mapc (lambda (key)
(define-key isearch-mode-map key 'isearch-printing-char))
'([(adiaeresis)] [(odiaeresis)] [(udiaeresis)] [(ssharp)]
[(Adiaeresis)] [(Odiaeresis)] [(Udiaeresis)] [(section)]))
--8<---------------cut here---------------end--------------->8---
The problem seems to be that non-ASCII characters are not classified as
"printing" when using isearch in Gnus (even though it works in other
modes). Note that you may still not find all occurrences of a certain
character in the summary buffer; this is likely caused by encoding
differences (Latin 1 vs. Latin 9, etc.).
HTH
--
Michael Piotrowski, M.A. <mxp@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt>
next prev parent reply other threads:[~2007-04-20 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871wik0xq8.fsf@debian.IGP>
2007-04-18 0:00 ` Bill Harris
[not found] ` <87bqhkz4bb.fsf@debian.IGP>
2007-04-21 0:21 ` Bill Harris
2007-04-20 9:29 ` Michael Piotrowski [this message]
2007-04-21 9:31 ` XEmacs: Incremental search for non-ASCII chars in the summary buffer (was: incremental search and Umlauts) Reiner Steib
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x6r6qftmv5.fsf@eurus.mag.dynalabs.de \
--to=mxp@dynalabs.de \
--cc=info-gnus-english@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).