unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Refilling overrides texinfo commands
Date: Wed, 25 Jun 2003 18:58:08 -0500 (CDT)	[thread overview]
Message-ID: <200306252358.h5PNw8F17085@eel.dms.auburn.edu> (raw)
In-Reply-To: <5xznk5zmc8.fsf@kfs2.cua.dk> (storm@cua.dk)

Kim Storm wrote:

   Your example illustrates such a case, but I have been unable to find
   any actual examples in the existing texi files (I haven't looked at
   every @*, but I'd say it seems like a non-problem in practice).

and:

   Emacs info does respect @* in general -- it is only in connection with
   note references that it may accidentally be undone.

Yes, but we have to worry not just about present info files included
with the Emacs distribution, but about future info files and about
`Texinfo' as a language.  It reduces the attractiveness of a language
if one of its main readers respects its commands "most of the time" as
opposed to "all of the time".  If commands not working as specified
does not even get considered a "bug", reliability is gone.

Sincerely,

Luc.

  reply	other threads:[~2003-06-25 23:58 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 [this message]
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
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=200306252358.h5PNw8F17085@eel.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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).