all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Divergence in menu appearance between Emacs Info and standalone Info
Date: Thu, 5 Jun 2003 10:52:42 -0500 (CDT)	[thread overview]
Message-ID: <200306051552.h55FqgZ27217@eel.dms.auburn.edu> (raw)
In-Reply-To: <200306051259.h55Cx4W14338@f7.net> (karl@freefriends.org)

Karl Berry wrote:

       in this case the
       differences are in numerous places in the node.  It may look very ugly
       to describe both alternatives.  Could you try?

   It would be better for someone who has actually used or programmed this
   feature to write at least the first draft.  I don't know any of the details.

   Luc, perhaps you make a first cut at changing info.texi, and then I'll
   review it?

I would be willing to help.  But does it make any sense to do this
right now?  We have not yet decided how either the Emacs or the
standalone versions are going to look like.  Would the first task at
hand not be to worry about those two questions?  Otherwise, we might
just keep rewriting the manual continuously, as we keep changing our
minds.  The relevant changes in the Emacs version of Info do not
appear in any released Emacs version and should (in my opinion) not
appear in any released Emacs version until we have made a decision on
how the Emacs version of Info is going to look.  It would be very bad
to just keep switching the behavior back and forth on the user, in as
far as released versions are concerned.  CVS users know (or should
know) that some features could change back and forth depending on the
unexpected problems that they turn out to cause.

In other words to me it would seem that the order should be:

1.  First decide how the Emacs version is going to look.

2.  Decide how the standalone version is going to look.

3.  Implement 1 and 2.

4.  Rewrite the documentation accordingly.

Is there any reason to do things in a different order, unless 3. is
scheduled for the extremely vague and extremely distant future?  I do
not believe implementation of 1. should be put off until then.
Implementation of 2. conceivably might, if nobody can find the time.
In that case, I would rewrite the manual based on current behavior of
the standalone version.

Sincerely,

Luc.

  reply	other threads:[~2003-06-05 15:52 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05 12:59 Divergence in menu appearance between Emacs Info and standalone Info Karl Berry
2003-06-05 15:52 ` Luc Teirlinck [this message]
2003-06-05 16:23 ` Luc Teirlinck
2003-06-05 18:19   ` Luc Teirlinck
2003-06-06 17:02   ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2003-06-09 23:17 Karl Berry
2003-06-11  0:24 ` Richard Stallman
2003-06-08 13:48 Karl Berry
2003-06-08 16:02 ` Eli Zaretskii
2003-06-09 23:00 ` Richard Stallman
2003-06-05 16:30 Karl Berry
2003-06-05 16:44 ` Luc Teirlinck
2003-06-05 23:39   ` Kim F. Storm
2003-06-06 17:03     ` Richard Stallman
2003-06-04 23:12 Karl Berry
2003-06-05  0:39 ` Luc Teirlinck
2003-06-04 14:04 Karl Berry
2003-06-04 14:26 ` Miles Bader
2003-06-04 15:01 ` Stefan Monnier
2003-06-04 15:24   ` Eli Zaretskii
2003-06-04 15:31     ` Stefan Monnier
2003-06-04 16:55       ` Luc Teirlinck
2003-06-04 17:14         ` Stefan Monnier
2003-06-05  2:38           ` Luc Teirlinck
2003-06-05  3:23             ` Miles Bader
2003-06-05  5:52           ` Eli Zaretskii
2003-06-05 13:35             ` Stefan Monnier
2003-06-06  9:46               ` Eli Zaretskii
2003-06-06 11:28                 ` Andreas Schwab
2003-06-06 15:38                 ` Stefan Monnier
2003-06-05  5:49       ` Eli Zaretskii
2003-06-05 10:58       ` Richard Stallman
2003-06-04 15:25 ` Eli Zaretskii
2003-06-04 15:47 ` Luc Teirlinck
2003-06-05 10:57 ` Richard Stallman
2003-06-05 12:27 ` Robert J. Chassell
2003-06-06  0:11   ` Kim F. Storm
2003-06-05 22:55     ` Miles Bader
2003-06-05 23:11     ` Robert J. Chassell
2003-06-05 23:23       ` Stefan Monnier
2003-06-05 23:56         ` Robert J. Chassell
2003-06-06  2:02           ` Miles Bader
2003-06-06 13:28             ` Robert J. Chassell
2003-06-06  9:50           ` Eli Zaretskii
2003-06-06 13:02             ` David Kastrup
2003-06-08  1:09               ` Richard Stallman
2003-06-08  1:20                 ` Stefan Monnier
2003-06-08  2:30                   ` David Kastrup
2003-06-09  8:53                   ` Richard Stallman
2003-06-06 14:00             ` Robert J. Chassell
2003-06-06 15:51               ` Eli Zaretskii
2003-06-06 16:54                 ` Robert J. Chassell
2003-06-06 17:25               ` Kevin Rodgers
2003-06-08  1:07               ` Richard Stallman
2003-06-15 15:47               ` Karl Eichwalder
2003-06-15 16:08                 ` Stefan Monnier
2003-06-15 22:27                   ` Miles Bader
2003-06-16 12:02                   ` Reiner Steib
2003-06-16 18:45                     ` Robert J. Chassell
2003-06-15 17:46                 ` Robert J. Chassell
2003-06-16  5:46                   ` Karl Eichwalder
2003-06-15 19:00                 ` Kai Großjohann
2003-06-06 17:24       ` Kevin Rodgers
2003-06-07 11:46         ` Kai Großjohann
2003-06-06 17:03   ` Richard Stallman
2003-06-05 16:50 ` Kai Großjohann
2003-06-05 20:50   ` Luc Teirlinck
2003-06-06 16:05     ` Luc Teirlinck
2003-06-06 16:29       ` Luc Teirlinck
2003-06-04  8:54 Richard Stallman
2003-06-04  9:06 ` Miles Bader
2003-06-04 15:12   ` Andreas Schwab
2003-06-04 21:54     ` David Kastrup
2003-06-12  6:47       ` Karl Eichwalder
2003-06-12 22:13         ` Luc Teirlinck
2003-06-13  3:58           ` Karl Eichwalder
2003-06-13  5:00             ` Luc Teirlinck
2003-06-13  5:10               ` Luc Teirlinck
2003-06-13  6:16                 ` Stefan Monnier
2003-06-05  2:47     ` Kim F. Storm
2003-06-05 13:04       ` Andreas Schwab
2003-06-10  0:03         ` Kim F. Storm

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=200306051552.h55FqgZ27217@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 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.