From: Juri Linkov <juri@jurta.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 13402@debbugs.gnu.org
Subject: bug#13402: 24.2.92 pretest: bugs in isearch-yank-line in info page
Date: Fri, 11 Jan 2013 02:43:16 +0200 [thread overview]
Message-ID: <87k3rktu9v.fsf@mail.jurta.org> (raw)
In-Reply-To: <20130110132530.GA2805@acm.acm> (Alan Mackenzie's message of "Thu, 10 Jan 2013 13:25:30 +0000")
> 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]
Info hides the text "*note Char-Tables::" and uses the text property `display'
to put another text "(see Char-Tables)" instead. Some users complained
when isearch-yank-line yanked invisible text "*note", so now it ignores
invisible text. But it seems ignoring invisible text is worse than yanking.
So perhaps `Info-isearch-filter' shouldn't skip invisible text.
next prev parent reply other threads:[~2013-01-11 0:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 13:25 bug#13402: 24.2.92 pretest: bugs in isearch-yank-line in info page Alan Mackenzie
2013-01-10 18:21 ` Andreas Schwab
2013-01-11 0:43 ` Juri Linkov [this message]
2013-02-13 9:47 ` Alan Mackenzie
2013-02-13 17:53 ` Juri Linkov
2013-02-13 21:59 ` Alan Mackenzie
2013-02-14 9:16 ` Juri Linkov
2013-02-14 20:09 ` 24.2.92 pretest: bugs in isearch-yank-line in info page. [Patch] Alan Mackenzie
2013-02-14 23:53 ` bug#13402: " Glenn Morris
2013-02-15 7:47 ` Juri Linkov
2013-02-15 10:10 ` Juri Linkov
2013-02-15 11:55 ` Alan Mackenzie
2013-02-15 13:20 ` Alan Mackenzie
2013-02-16 21:50 ` Juri Linkov
2013-02-17 10:03 ` Juri Linkov
2013-02-19 14:50 ` Alan Mackenzie
2013-02-20 10:49 ` Juri Linkov
2013-02-20 22:37 ` Alan Mackenzie
2013-02-21 0:45 ` Juri Linkov
2013-02-21 12:27 ` Alan Mackenzie
2013-02-21 17:09 ` Glenn Morris
2013-02-21 17:48 ` Juri Linkov
2013-02-14 20:09 ` Alan Mackenzie
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3rktu9v.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=13402@debbugs.gnu.org \
--cc=acm@muc.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.