>> I also removed `isearch-within-brackets' because it is used nowhere
>> within Emacs.
> I think the intent of that was to allow SPC to be a shortcut to mean
> "any whitespace", whereas SPC inside brackets still stands for itself.
IIRC it's a left over of a previous implementation of that featur
Juri Linkov <[EMAIL PROTECTED]> writes:
> I also removed `isearch-within-brackets' because it is used nowhere
> within Emacs.
I think the intent of that was to allow SPC to be a shortcut to mean
"any whitespace", whereas SPC inside brackets still stands for itself.
But I lost track of the discus
> > The implementation looks clean. I just suggest that we should simply
> > replace isearch-invalid-regexp with isearch-error (there can only be one
> > error at any given time, either a search failure or an invalid regexp, or
> > ...).
>
> OK.
>
> I also removed `isearch-within-bracket
Stefan Monnier <[EMAIL PROTECTED]> writes:
> The implementation looks clean. I just suggest that we should simply
> replace isearch-invalid-regexp with isearch-error (there can only be one
> error at any given time, either a search failure or an invalid regexp, or
> ...).
OK.
I also removed `ise
> In the implementation below it would be possible to reuse
> `isearch-invalid-regexp' to hold the error message, but this is not
> a clean solution. Adding a new special variable `isearch-error' looks
The implementation looks clean. I just suggest that we should simply
replace isearch-invalid-r
Below is an implementation that works as follows:
after an attempt to leave the first Info node,
isearch fails with the following message:
Failing I-search: search string [failed in current node]
After leaving the first Info node with subsequent C-s or C-r,
isearch doesn't fail more in other
> Would you like it if isearch failed before proceeding to the
> next Info node?
>
> I would. I suggested this long ago. It should first wrap, as Richard
> suggested. After the entire Info node has been searched, it should
> fail. A subsequent invocation should conti
> > Would you like it if isearch failed before proceeding to the
> > next Info node?
> >
> > I would. I suggested this long ago. It should first wrap, as Richard
> > suggested. After the entire Info node has been searched, it should
> > fail. A subsequent invocation should continue th
"Drew Adams" <[EMAIL PROTECTED]> writes:
> Would you like it if isearch failed before proceeding to the
> next Info node?
>
> I would. I suggested this long ago. It should first wrap, as Richard
> suggested. After the entire Info node has been searched, it should
> fail. A subsequent invoca
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.
Yes, I think that is right.
Could you please do it?
Of
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.
Good point - I agree.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://l
Would you like it if isearch failed before proceeding to the
next Info node?
I would. I suggested this long ago. It should first wrap, as Richard
suggested. After the entire Info node has been searched, it should fail. A
subsequent invocation should continue through the manual.
IOW, isear
> > 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 pa
Miles Bader <[EMAIL PROTECTED]> writes:
> 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 proceedi
Nick Roberts <[EMAIL PROTECTED]> 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
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
On Wed, 9 Mar 2005 20:32:35 +1300, Nick Roberts <[EMAIL PROTECTED]> wrote:
> If I look for something in an Info manual, I use Info-search (s) and if I
> looked for something on a particular page, I would use isearch-forward
> (C-s). However, now isearch-forward now also searches the subsequent manu
If I look for something in an Info manual, I use Info-search (s) and if I
looked for something on a particular page, I would use isearch-forward
(C-s). However, now isearch-forward now also searches the subsequent manual
pages and takes me away from the page I'm interested in. That seems a bit
red
18 matches
Mail list logo
