From: Vitalie Spinu <spinuvit@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 19710-done@debbugs.gnu.org
Subject: bug#19710: 24.4.51; Isearch is broken in comints which relly on regexp
Date: Thu, 05 Feb 2015 11:03:41 +0100 [thread overview]
Message-ID: <877fvwvfnm.fsf@gmail.com> (raw)
In-Reply-To: <87vbjhdvas.fsf@mail.linkov.net> (Juri Linkov's message of "Thu, 05 Feb 2015 02:57:07 +0200")
Thanks. It works.
Vitalie
>>> Juri Linkov on Thu, 05 Feb 2015 02:57:07 +0200 wrote:
>> >> Recent changes to commit to allow for multiline search assume fields
>> >> throughout. The common case when comint-use-prompt-regexp is non-nil is
>> >> not captured.
>> >>
>> >> To see the problem start shell and issue a couple of commands. Then
>> >> (setq comint-use-prompt-regexp t), and add a couple of RETs. Then try M-r.
>> >>
>> >> You should see "Regexp history I-search backward:" several lines above
>> >> where it should be and isearch will not work as expected.
>> >>
>> >> If you restart your shell, you will not even see the "Regexp history
>> >> I-search backward:" as there are no fields in the buffer.
>>
>> > Thanks for the report. This can be fixed by the patch that
>> > reverts the change of callers, and instead modifies
>> > `comint-line-beginning-position' to support multi-line input
>> > for both cases of comint-use-prompt-regexp = t/nil:
>>
>> Thanks Juri, this patch solves the problem indeed.
> I fixed this on the emacs-24 branch because bug#19572 backported
> previous changes to emacs-24.
next prev parent reply other threads:[~2015-02-05 10:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 9:10 bug#19710: 24.4.51; Isearch is broken in comints which relly on regexp Vitalie Spinu
2015-01-29 0:50 ` Juri Linkov
2015-01-29 8:13 ` Vitalie Spinu
2015-02-05 0:57 ` Juri Linkov
2015-02-05 10:03 ` Vitalie Spinu [this message]
2015-02-10 0:39 ` Juri Linkov
2015-02-18 15:55 ` Vitalie Spinu
2015-02-18 17:01 ` Juri Linkov
2015-02-18 17:46 ` Eli Zaretskii
2015-02-18 18:20 ` Juri Linkov
2015-02-18 18:18 ` Vitalie Spinu
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=877fvwvfnm.fsf@gmail.com \
--to=spinuvit@gmail.com \
--cc=19710-done@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).