From: Dave Abrahams <dave@boostpro.com>
To: Juri Linkov <juri@jurta.org>
Cc: 10166@debbugs.gnu.org, John Wiegley <johnw@boostpro.com>
Subject: bug#10166: 23.3; [Info-search] "Search Failed"
Date: Wed, 30 Nov 2011 10:55:43 -0500 [thread overview]
Message-ID: <m2liqx7gg0.fsf@boostpro.com> (raw)
In-Reply-To: <8739d5aad2.fsf@mail.jurta.org> (Juri Linkov's message of "Wed, 30 Nov 2011 17:38:49 +0200")
on Wed Nov 30 2011, Juri Linkov <juri-AT-jurta.org> wrote:
>>>> Almost any search in the attached fileset will fail in this way if you
>
>>>> repeat it enough times. Is the texi ill-formed?
>>>
>>> Yes, it's ill-formed.
>>>
>>> `Info-search' expects that "^_\nIndirect:" is preceded by a newline in std.info,
>>> so it fails trying to call (search-forward "\n\^_\nIndirect:").
>>
>> Amazing. It's the direct output of makeinfo, so I can't understand why
>> the newline would be missing and expected.
>
> makeinfo prepends some boilerplate to its output in every Info file
> that at least begins with a line like:
>
> This is std.info, produced by makeinfo version 4.13 from std.texi.
>
> so there is always a newline before ^_Indirect:
Well, I am getting some errors from makeinfo, so maybe that's why I
don't see that line at the top of the output. The output appears to be
otherwise usable (if imperfect).
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2011-11-30 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 10:10 bug#10166: 23.3; [Info-search] "Search Failed" Dave Abrahams
2011-11-30 10:28 ` Juri Linkov
2011-11-30 13:14 ` Dave Abrahams
2011-11-30 15:38 ` Juri Linkov
2011-11-30 15:55 ` Dave Abrahams [this message]
2011-12-01 7:41 ` Juri Linkov
2011-12-01 16:41 ` Dave Abrahams
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=m2liqx7gg0.fsf@boostpro.com \
--to=dave@boostpro.com \
--cc=10166@debbugs.gnu.org \
--cc=johnw@boostpro.com \
--cc=juri@jurta.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).