From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: vose@eecs.utk.edu, 19924@debbugs.gnu.org
Subject: bug#19924: 24.4; incremental search for octal character
Date: Fri, 06 Mar 2015 16:57:01 +0200 [thread overview]
Message-ID: <83wq2umawy.fsf@gnu.org> (raw)
In-Reply-To: <c23a8302-3be6-46f1-aa91-cbb5c8b85f26@default>
> Date: Thu, 5 Mar 2015 14:54:55 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: vose@eecs.utk.edu
>
> > I anticipate that the following is an explanation of some kind:
> >
> > "As the screenshot shows, the problem is that the search doesn't find
> > the character 213 in the `no-conversion' (binary) buffer, because
> > there is a mismatch between the coding of the buffer and the search."
> >
> > But I don't know what the above means. In particular, I don't know how
> > to search for octal 213. Given my current (lack of) understanding, it
> > seems that emacs is broken, or searching in octal is not possible.
It means that we have a missing feature: we don't have any reasonable
way of typing unibyte characters at Isearch's prompt. We need to
provide one. There was such a kludgey feature in the past, but it
conflicted with a much more useful possibility of inserting Unicode
codepoints with C-q, and so the kludge was deleted in one of the
previous versions. We need to restore it, at least for when Isearch
was initiated from a unibyte buffer.
Another possibility would be to have an input method for that.
(The manual isn't wrong, strictly speaking: it says "non-ASCII
characters", not "raw bytes in unibyte buffers".)
next prev parent reply other threads:[~2015-03-06 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 19:13 bug#19924: 24.4; incremental search for octal character vose
2015-02-22 22:02 ` Drew Adams
2015-02-22 23:03 ` Andreas Schwab
2015-02-23 0:22 ` Drew Adams
2015-02-23 11:43 ` Andreas Schwab
2015-02-23 15:13 ` Drew Adams
2015-02-23 19:16 ` Juri Linkov
2015-03-05 22:54 ` Drew Adams
2015-03-06 14:57 ` Eli Zaretskii [this message]
2022-02-21 16:15 ` Lars Ingebrigtsen
[not found] <<87r3thep3z.fsf@eecs.utk.edu>
[not found] ` <<c23a8302-3be6-46f1-aa91-cbb5c8b85f26@default>
[not found] ` <<83wq2umawy.fsf@gnu.org>
2015-03-06 16:27 ` Drew Adams
2015-03-06 16:33 ` Dani Moncayo
2015-03-06 16:36 ` Drew Adams
2015-03-06 19:20 ` Eli Zaretskii
[not found] <<83dbd618-1126-4b4e-a0e2-274e2494ae44@default>
[not found] ` <<83twxylyq3.fsf@gnu.org>
2015-03-06 19:42 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wq2umawy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19924@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=vose@eecs.utk.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).