From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Refilling overrides texinfo commands
Date: 06 Jul 2003 14:14:46 +0200 [thread overview]
Message-ID: <5xn0frj1hl.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <E19Vw0B-0000uJ-Rj@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> 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.
>
> You are right.
>
> So I have gone back to my conclusion of a week ago, that we should
> stop refilling paragraphs in Info. When some xref text is hidden, the
> line will be shorter. That looks a little strange, but it is not
> really wrong. When refilling is done, the results can be positively
> wrong.
I agree. Rather than completely removing the refilling, I have added
a new variable Info-refill-paragraphs (default disabled) with suitable
warnings about its potential ill effects.
Take a look at the end of "(texinfo)makeinfo in Emacs" for a really
extreme example of how bad the text can look _without_ refilling.
>
> 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.
>
> Perhaps makeinfo is fast enough now that we could stop installing
> Info files and have them regenerated when users want them.
> If so, we could have an option to generate them in various ways
> (hiding xrefs, showing xrefs, etc).
We could do that always, provided that the result is cached.
However, we would then require specific (very new) versions of
makeinfo to be installed on the user's system. That would be a
problem for many users.
So I think we should still install info files as a fall-back, and only
require to run makeinfo when some option (like
Info-hide-note-references) is explicitly turned on.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2003-07-06 12:14 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
2003-06-27 0:43 ` Luc Teirlinck
2003-06-27 16:23 ` Richard Stallman
2003-07-06 12:14 ` Kim F. Storm [this message]
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=5xn0frj1hl.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.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).