emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#13402: closed (24.2.92 pretest: bugs in isearch-ya


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#13402: closed (24.2.92 pretest: bugs in isearch-yank-line in info page)
Date: Thu, 14 Feb 2013 09:25:03 +0000

Your message dated Thu, 14 Feb 2013 11:16:16 +0200
with message-id <address@hidden>
and subject line Re: bug#13402: 24.2.92 pretest: bugs in isearch-yank-line in 
info page
has caused the debbugs.gnu.org bug report #13402,
regarding 24.2.92 pretest: bugs in isearch-yank-line in info page
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
13402: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13402
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.2.92 pretest: bugs in isearch-yank-line in info page Date: Thu, 10 Jan 2013 13:25:30 +0000 User-agent: Mutt/1.5.21 (2010-09-15)
Emacs 24.2.92.

emacs -Q
C-u C-h i
Enter path/to/elisp.info <CR>
g Syntax Table Internals

1. Place point at the start of the first paragraph ("Syntax tables are
implemented ...").  Attempt C-s M-s C-e (isearch-yank-line).  This
produces the error message:

Failing I-search: syntax tables are implemented as char-tables (*note 
char-tables::), but [end of node]

This is a bug.

2. Place point at the start of the second paragraph ("Each entry in a
....").  Attempt C-s M-s C-e (isearch-yeank-line).  This works, but
wrongly highlights the gap preceding the paragraph with lazy-highlight
face.


-- 
Alan Mackenzie (Nuremberg, Germany).



--- End Message ---
--- Begin Message --- Subject: Re: bug#13402: 24.2.92 pretest: bugs in isearch-yank-line in info page Date: Thu, 14 Feb 2013 11:16:16 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (x86_64-pc-linux-gnu)
>> > I think it should either skip it properly, or not at all.
>> > There is an inconsistency here between parts of isearch.
>>
>> This can be fixed by the patch below that takes into account
>> the default value `open' of `search-invisible' and treats it the same
>> as its value `t', i.e. matches hidden text (but it still can't "open" it
>> in a meaningful way).
>
> OK.  The patch seems to work.

Thanks for confirmation.  This is now installed in trunk and the bug closed.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]