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: info
Date: Mon, 3 Feb 2003 13:00:07 -0600 (CST)	[thread overview]
Message-ID: <200302031900.NAA27632@moose.dms.auburn.edu> (raw)
In-Reply-To: <200302031440.h13EeTR11294@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)

Stefan Monnier wrote:

   > Another idea is that any blank line ends the menu item.

   That's what the "sorting and duplicate-elimination for dir" code
   I installed a few months back does.

I am starting to lean toward implementing Kay's and Richard's
suggestion.  I have not found any single example defeating it.

Even if something would go wrong, the confusion caused by it (in as
far as RETURN is concerned) would be less than the confusion caused by
the present Emacs behavior.  We are not exactly talking about deleting
directories or such.

Eli is opposed to it, but he seems to have misunderstood the proposal.

The fundamental question is, how likely are we to see something like:

* Menu:

* Interactive Customization::
* Permanent Customization::
* Hooks::
* Styles::
* Advanced Customizations::
   ---------- Footnotes ----------
   (1) Available in Emacs 20 and later, and XEmacs 19.15 and later.
   (2) Obviously, you use the key binding interactively, and the
function call programmatically!

Not an actual example, but an example I gave before with some newlines
removed.  Everything depends on the likelihood of such examples
occurring on practice.  Especially the missing newline before the
"Footnotes" line (the only problem) looks ugly to me.  But, are there
any hard stylistic guidelines against writing in such a
blank-line-less style?

I have not really made up my mind one way or the other.  Everything
depends on the above questions.

Sincerely,

Luc.

  reply	other threads:[~2003-02-03 19:00 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <84smvc2guf.fsf@lucy.is.informatik.uni-duisburg.de>
2003-01-29 14:20 ` info Eli Zaretskii
2003-01-30 15:21   ` info Richard Stallman
2003-01-30 16:21     ` info Luc Teirlinck
2003-01-31 19:20       ` info Richard Stallman
2003-02-01  1:22         ` info Luc Teirlinck
2003-02-01 22:11           ` info Richard Stallman
2003-02-02  4:59             ` info Luc Teirlinck
2003-02-02  5:44             ` info Eli Zaretskii
2003-02-02  6:09               ` info Miles Bader
2003-02-03 14:40             ` info Stefan Monnier
2003-02-03 19:00               ` Luc Teirlinck [this message]
2003-02-03 19:16                 ` info Luc Teirlinck
2003-02-03 19:19                   ` info Luc Teirlinck
2003-02-04 15:41                 ` info Richard Stallman
2003-02-05  6:08                   ` info Eli Zaretskii
2003-02-05 20:07                     ` info Luc Teirlinck
2003-02-09  4:45                       ` info Luc Teirlinck
2003-01-29  1:33 info Luc Teirlinck
2003-01-29  3:53 ` info Luc Teirlinck
2003-01-29  6:29   ` info Eli Zaretskii
2003-01-29 19:57     ` info Luc Teirlinck
2003-01-30  5:46       ` info Eli Zaretskii
2003-01-29 21:17   ` info Richard Stallman
2003-01-29 17:33 ` info Eli Zaretskii
2003-01-29 20:39   ` info Luc Teirlinck
2003-01-29 23:21     ` info Luc Teirlinck
2003-01-30  5:48     ` info Eli Zaretskii
2003-01-30  8:39       ` info Kai Großjohann
2003-01-30 15:11         ` info Luc Teirlinck
2003-01-30 16:30           ` info Luc Teirlinck
2003-01-30 20:02         ` info Eli Zaretskii
2003-01-30 20:51           ` info Kai Großjohann
2003-01-30 22:37           ` info Robert J. Chassell
2003-01-31  1:51             ` info Luc Teirlinck
2003-01-31 13:05               ` info Robert J. Chassell
2003-01-31 20:22                 ` info Luc Teirlinck
2003-02-01  1:22                   ` info Robert J. Chassell
2003-01-29 21:17 ` info Richard Stallman
2003-01-30  0:31   ` info Luc Teirlinck
2003-01-30  1:43     ` info Luc Teirlinck
2003-01-30  2:03       ` info Luc Teirlinck

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=200302031900.NAA27632@moose.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.