From: Eli Zaretskii <eliz@gnu.org>
To: dhruv@physics.utexas.edu, 1188@emacsbugs.donarmstrong.com
Cc: bug-gnu-emacs@gnu.org
Subject: bug#1188: Info reader and newlines in dir file
Date: Fri, 17 Oct 2008 10:28:06 +0200 [thread overview]
Message-ID: <uod1jmxrd.fsf@gnu.org> (raw)
In-Reply-To: <87tzbc9q56.fsf@silicon.austin.rr.com>
> From: dhruv@physics.utexas.edu
> Date: Thu, 16 Oct 2008 16:38:45 -0500
> Cc:
>
> I built and installed the MySQL Info manual. The manual would show up
> in the dir node when I invoked `info' from the command line but was
> nowhere to be found when I invoked `info' within Emacs. I tracked
> this down to the fact that the MySQL entry in the Info dir node was
> the last one and that there was no newline after it. Inserted a
> newline allowed Emacs to "see" the manual and load it up properly
> inside Info running in Emacs. This might be purposeful design, but it
> feels like a bug to me: Emacs Info should behave like the command-line
> info and not any different.
The Emacs Info reader and the stand-alone Info reader are two
different implementations of the same informal specification. There's
no formal specification of the structure of a valid Info file. So
there's little hope for both of them working identically in bordeline
cases such as this one, especially since they are written in two very
different programming languages. As a matter of fact, they have
different features, albeit minor ones.
I would also argue that an entry in DIR without a newline is a bug in
whatever procedure you followed to install that Info manual.
Bottom line, my recommendation is not to try to fix this, at least not
now, for fear of breaking something more important at the time when
the efforts are on fixing real bugs (of which there are too many, IMO)
in order to begin the pretest. But that's me.
next prev parent reply other threads:[~2008-10-17 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 21:38 bug#1188: Info reader and newlines in dir file dhruv
2008-10-17 8:28 ` Eli Zaretskii [this message]
2021-06-03 10:11 ` Lars Ingebrigtsen
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=uod1jmxrd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=1188@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=dhruv@physics.utexas.edu \
/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.