From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: storm@cua.dk
Subject: Re: Refilling overrides texinfo commands
Date: Thu, 26 Jun 2003 18:53:38 -0500 (CDT) [thread overview]
Message-ID: <200306262353.h5QNrc718263@eel.dms.auburn.edu> (raw)
In-Reply-To: <E19VdFN-0007OE-Mj@fencepost.gnu.org> (message from Richard Stallman on Thu, 26 Jun 2003 16:21:33 -0400)
Richard Stallman wrote:
I have another solution to propose:
1. Change the standalone info to hide the same text as Emacs info does.
2. Change Makeinfo to recognize when filling that that text will be
hidden.
That would have the negative effect of effectively disabling
Info-hide-note-references and making the text-hiding "mandatory"
instead of having it as an optional feature. Several people prefer
not to have the information in question hidden and they have valid
reasons for that.
I have the impression that some people on this list believe that the
only reason one could probably want to have Info-hide-note-references
set to anything else but t is to satisfy some strange ideological
obsession. This is extremely far from the truth. I am not speaking
in the abstract here. I am using Info extensively. For instance, I
used Info recently to learn Texinfo. I was reluctant to just set
Info-hide-note-references to nil, because I am rewriting parts of the
tutorial and for that reason, I prefer to use all-default settings in
Info. But I tended to leave vis-mode on in the presence of
cross-references. The reason is that several cross-references in the
Texinfo manual led to the Emacs manual. Knowing that information
saved me the time and trouble to follow these cross-references: I
already knew that stuff anyway. Similar situations occur in various
other manuals I studied using Info.
Also, if we want to maximize quality of appearance to the fullest then
there are tons of things we might want to do. _This is really
important stuff_ would look a lot better if it were written in the
font used by texinfo-mode than enclosed in _..._. Same for *...*. It
would look nicer if @code, @kbd and several others would yield
different fonts and/or colors, rather than all being enclosed in
`...'. Same for various different stuff enclosed in "...". In the
case of @code, @kbd and the like, and even for _..._ and *...*, the
information can not be reliably recovered from the Info file, but it
is all in the source file. (I am not familiar with XML and DocBook.)
So one question is: how far do we want to go longer term? Is the
current hiding and refilling a first step to "better things to come"?
Are we happy with the Info format for the long term or do we want a
separate "Emacs format"?
I believe that trying to reformat Info files, as currently being
attempted, makes no sense. Info is an output format, not a mark up
language. Texinfo is a mark up language. So are XML and DocBook.
Sincerely,
Luc.
next prev parent reply other threads:[~2003-06-26 23:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 13:21 Refilling overrides texinfo commands Luc Teirlinck
2003-06-26 0:58 ` Kim F. Storm
2003-06-25 23:58 ` Luc Teirlinck
2003-06-26 20:21 ` Richard Stallman
2003-06-26 23:53 ` Luc Teirlinck [this message]
2003-06-27 0:43 ` Luc Teirlinck
2003-06-27 16:23 ` Richard Stallman
2003-07-06 12:14 ` Kim F. Storm
2003-07-06 11:36 ` Robert J. Chassell
2003-07-06 23:50 ` Kim F. Storm
2003-07-07 3:39 ` Richard Stallman
2003-07-07 3:39 ` Richard Stallman
2003-06-27 0:12 ` Kim F. Storm
-- strict thread matches above, loose matches on Subject: below --
2003-06-25 13:33 Karl Berry
2003-06-26 22:44 Karl Berry
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=200306262353.h5QNrc718263@eel.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=storm@cua.dk \
/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).