unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: Divergence in menu appearance between Emacs Info and standalone Info
Date: Wed, 4 Jun 2003 21:38:18 -0500 (CDT)	[thread overview]
Message-ID: <200306050238.h552cIj26820@eel.dms.auburn.edu> (raw)
In-Reply-To: <200306041714.h54HEURm026453@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)

Stefan Monnier wrote:

       (info "<node name>") is a better way than using `g' since the
       `somebody' can just click on it (or hit C-x C-e).

That is, assuming the `somebody' receives mail in an emacs buffer.
In general, I would not consider M-: (info "<node name>") to be more
convenient or intuitive than C-h i g <node-name>.

But, your question was:

   How many users currently actively use node names ?  From what I can
   tell, these seem to be mostly used internally, much like URLs in
   HTML.

(info "<node-name>") uses a node name just as actively as g, or not?
The point I am trying to make is that it is useful for an Info user to
know the concept of a node name, it is not something of purely
internal importance.  This does not mean that it is the first thing a
beginning Info user should worry about.  It does also not necessarily
mean that node names should be displayed in menus, that is a separate
question.

Sincerely,

Luc.

  reply	other threads:[~2003-06-05  2:38 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04 14:04 Divergence in menu appearance between Emacs Info and standalone Info 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 [this message]
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
  -- 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-05 12:59 Karl Berry
2003-06-05 15:52 ` Luc Teirlinck
2003-06-05 16:23 ` Luc Teirlinck
2003-06-05 18:19   ` Luc Teirlinck
2003-06-06 17:02   ` Richard Stallman
2003-06-04 23:12 Karl Berry
2003-06-05  0:39 ` 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

  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=200306050238.h552cIj26820@eel.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    /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).