From: Nick Roberts <nickrob@snap.net.nz>
Cc: snogglethorpe@gmail.com, emacs-devel@gnu.org, miles@gnu.org
Subject: Re: isearch-forward and Info-search
Date: Thu, 10 Mar 2005 20:56:42 +1300 [thread overview]
Message-ID: <16943.64954.585396.893418@farnswood.snap.net.nz> (raw)
In-Reply-To: <87ekeot3th.fsf@jurta.org>
> > I think it would be a lot less annoying if it at least changed the
> > prompt to say what it was doing, in the manner of a wrapped isearch
> > ("I-search in node ...: " ?).
> >
> > Maybe it could even act more like wrapped i-search, and fail once,
> > before proceeding to the next info page if you hit C-s again.
>
> It seems this is the most reasonable default behavior.
> But I also think it would be too annoying to fail before
> leaving every Info node. It would be better to fail only
> in the first Info node where isearch was started. Of course,
> this doesn't preclude creating at least four different options
> for the `Info-isearch-search' variable:
>
> - never fail (current behavior)
> - fail only in the node where isearch was started (proposed default)
> - fail in every node visited by isearch (somebody may like this)
> - fail and wrap to the beginning of the current node (old behavior)
This sounds a like a good idea. The proposed default would also be my
preferred behaviour.
Me> > I've also noticed that if you abort a search (C-s) before it gets to the
Me> > end of the manual the formatting of the links on the current page gets
Me> > messed up.
> This looks like a bug, but I can't reproduce it. Could you provide
> a precise receipt to reproduce it?
I can't seem to reproduce it. All the links after a certain point (where the
search had reached displayed as ordinary text like this:
Important Text-Changing Commands
* Mark:: The mark: how to delimit a ``region'' of text.
* Killing:: Killing (cutting) text.
* Yanking:: Recovering killed text. Moving text. (Pasting.)
If I can remember exactly what I did, I'll file a bug report.
Nick
next prev parent reply other threads:[~2005-03-10 7:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 7:32 isearch-forward and Info-search Nick Roberts
2005-03-09 7:59 ` Miles Bader
2005-03-10 2:02 ` Richard Stallman
2005-03-10 6:29 ` Juri Linkov
2005-03-10 7:56 ` Nick Roberts [this message]
2005-03-10 17:20 ` Drew Adams
2005-03-11 1:48 ` Richard Stallman
2005-03-10 6:33 ` Juri Linkov
2005-03-10 17:19 ` Drew Adams
2005-03-11 7:28 ` Juri Linkov
2005-03-11 8:15 ` Nick Roberts
2005-03-11 14:40 ` Drew Adams
2005-03-12 2:23 ` Juri Linkov
2005-03-12 13:47 ` Stefan Monnier
2005-03-13 1:00 ` Juri Linkov
2005-03-13 21:15 ` Nick Roberts
2005-03-29 12:17 ` Kai Großjohann
2005-03-29 13:48 ` Stefan Monnier
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=16943.64954.585396.893418@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=snogglethorpe@gmail.com \
/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).