unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: isearch-forward and Info-search
Date: Thu, 10 Mar 2005 08:33:08 +0200	[thread overview]
Message-ID: <878y4w43y6.fsf@jurta.org> (raw)
In-Reply-To: <16942.42643.503788.488893@farnswood.snap.net.nz> (Nick Roberts's message of "Wed, 9 Mar 2005 20:32:35 +1300")

Nick Roberts <nickrob@snap.net.nz> writes:
> Maybe theres been a long thread about this which I've missed, in which case
> I apologise but is there a variable to change this behaviour back to the
> old one?

The variable is `Info-isearch-search' and when set to nil it changes
the behavior to the old one.

> Could it be made the default?

Let's try to fix the new behavior and see if it will satisfy most
people.  Would you like it if isearch failed before proceeding to the
next Info node?

> I've also noticed that if you abort a search (C-s) before it gets to the end
> of the manual the formatting of the links on the current page gets messed up.

This looks like a bug, but I can't reproduce it.  Could you provide
a precise receipt to reproduce it?

-- 
Juri Linkov
http://www.jurta.org/emacs/

  parent reply	other threads:[~2005-03-10  6:33 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
2005-03-10 17:20     ` Drew Adams
2005-03-11  1:48     ` Richard Stallman
2005-03-10  6:33 ` Juri Linkov [this message]
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=878y4w43y6.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@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.
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).