unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: vose@eecs.utk.edu
Cc: 19924@debbugs.gnu.org
Subject: bug#19924: 24.4; incremental search for octal character
Date: Mon, 21 Feb 2022 17:15:09 +0100	[thread overview]
Message-ID: <87a6ekgprm.fsf@gnus.org> (raw)
In-Reply-To: <87r3thep3z.fsf@eecs.utk.edu> (vose@eecs.utk.edu's message of "Sun, 22 Feb 2015 14:13:36 -0500")

vose@eecs.utk.edu writes:

> TWO (2) problems; for both I follow the GNU Emacs manual from
> "https://www.gnu.org/software/emacs/manual/emacs.html"
>
> PROBLEM 1: The following is quoted from page 91:
>
> "To search for non-ASCII characters, use one of the following methods:
> • Type C-q, followed by a non-graphic character or a sequence of octal
> digits."
>
> In my case I typed C-q, followed by 213 and then return (the enter key).
> Rather than searching, the octal character \213 is inserted into the
> file.
>
> PROBLEM 2: Vose conjectured that the manual was simply mistaken, and
> should have said something closer to: To search for an octal character,
> type C-s C-q, followed by a sequence of octal digits.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

Yes, that's what the manual means.  The section starts with "In addition
to characters described in the previous subsections, some of the other
characters you type during incremental search have special effects." and
all the keys described are during incremental search.

But I've clarified this in the Emacs 29 manual

> In my case I typed C-s C-q, followed by 213 and then return (the enter
> key).  Rather than searching, the message "Failing I-search: \213" was
> displayed (see attached screen shot).

Yes -- you probably didn't have that byte in the buffer?  For
instance, having this character in the buffer:

®

And then C-s C-q 2 5 6 RET works fine for me (at least in Emacs 29).

So it seems like things are working as designed here, and I'm therefore
closing this bug report.  If I misunderstood what the problem was about,
please respond to the debbugs address and we'll reopen.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2022-02-21 16:15 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
2022-02-21 16:15 ` Lars Ingebrigtsen [this message]
     [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=87a6ekgprm.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=19924@debbugs.gnu.org \
    --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).