unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: gmorris@ast.cam.ac.uk, emacs-devel@gnu.org
Subject: Re: Advanced calendar usage in emacs-xtra.texi
Date: Sat, 26 Mar 2005 14:00:42 -0600 (CST)	[thread overview]
Message-ID: <200503262000.j2QK0gx16946@raven.dms.auburn.edu> (raw)
In-Reply-To: <01c53236$Blat.v2.4$287360c0@zahav.net.il> (eliz@gnu.org)

Eli Zaretskii wrote:

   Since emacs-xtra is not distributed with the Emacs manual, I think all
   references to it should be inside @ifinfo.  That way, someone who
   reads a printed version of the Emacs manual will not wonder where to
   find the (non-existent) emacs-xtra manual.

Somebody reading the Emacs manual presumably does so with the intent
of using emacs.  When using Emacs, he can read emacs-xtra using Info.
He can even print out hardcopy for emacs-xtra.  So things like this
should definitely _not_ be in @ifinfo.

   Alternatively, change all references to emacs-xtra to use @inforef.

That would be a lot better.

However, last time when I proposed something similar (for url.texi, if
I remember well), you and Karl and Dave opposed me on this and I wound
up using a regular @xref.  Did you change your mind on this or is
there a fundamental difference between emacs-xtra and url.texi?

Sincerely,

Luc.

  reply	other threads:[~2005-03-26 20:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1DFFm4-0005xm-DR@monty-python.gnu.org>
2005-03-26 19:00 ` Advanced calendar usage in emacs-xtra.texi Eli Zaretskii
2005-03-26 20:00   ` Luc Teirlinck [this message]
2005-03-26 22:06     ` Eli Zaretskii
2005-03-26 22:32       ` Luc Teirlinck
2005-03-26 20:14   ` Glenn Morris
2005-03-26 21:21   ` Luc Teirlinck
2005-03-28 16:25     ` Richard Stallman

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=200503262000.j2QK0gx16946@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=gmorris@ast.cam.ac.uk \
    /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).