unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: RE: Changes in revision 114466
Date: Tue, 01 Oct 2013 17:29:53 +0900	[thread overview]
Message-ID: <87vc1hqtq6.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <d3269127-399e-4e73-b09d-6a1fc5de24ad@default>

Drew Adams writes:

 >>> But users are not necessarily aware of [info-lookup-symbol].
 >> 
 >> Isn't that what should be fixed, then?
 > 
 > 1) How?

Bind C-h f and C-h v (which pretty much everybody knows and uses, I
guess) to a command that offers a menu of ways to get help on a symbol
(as a variable vs. as a function, docstring vs. manual).  Put it under
control of the old-and-cranky library (an as-yet-nonexistent novice-
like module that puts the traditional binding back when the user
invokes the command M-x im-old-and-cranky-so-put-the-binding-back).

 > 2) It's still good to provide a visual cue that a given term
 > is in the manual.

*Everything* "should" be in the manual.  It shouldn't be possible to
find a place to click in a help buffer that doesn't find offer useful
new information, IMHO.  Yes, I acknowledge that both "everything in
the manual" and "no place left to click" are hard tasks. ;-)  But
shouldn't that be our goal?

 > Maybe use that for any link (e.g. source file target) that leaves
 > *Help*?

As long as you stay in Emacs, why would one care?  C-x b *Help* RET is
hardly onerous, and if it is inconvenient, we could provide a global
C-h binding for "help-back-to-last-help".

 > Doing it automatically is no doubt easier, not harder, than doing it
 > using judgment case by case.

In that case, the prosecution rests. :-)






      reply	other threads:[~2013-10-01  8:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.53349.1380335551.10747.emacs-diffs@gnu.org>
2013-09-28  7:46 ` Changes in revision 114466 Eli Zaretskii
2013-09-28 22:30   ` Xue Fuqiao
2013-09-29  2:36     ` Eli Zaretskii
2013-09-29  7:24       ` Thien-Thi Nguyen
2013-09-30  4:55         ` Xue Fuqiao
2013-09-30  5:21           ` Drew Adams
2013-09-30 10:29             ` Stephen Berman
2013-09-30 15:05               ` Drew Adams
2013-09-30 15:52                 ` Thien-Thi Nguyen
2013-10-01  2:11                 ` Stephen J. Turnbull
2013-09-30 15:42               ` Eli Zaretskii
2013-09-30 11:47             ` Andreas Röhler
2013-09-30 15:38           ` Eli Zaretskii
     [not found]           ` <<83k3hye2uq.fsf@gnu.org>
2013-09-30 16:38             ` Drew Adams
2013-10-01  3:40               ` Xue Fuqiao
2013-10-01  4:57                 ` Stephen J. Turnbull
2013-10-01  5:15                   ` Drew Adams
2013-10-01  5:27                     ` Drew Adams
2013-10-01  6:11                     ` Stephen J. Turnbull
2013-10-01  7:44                       ` Drew Adams
2013-10-01  8:29                         ` Stephen J. Turnbull [this message]

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=87vc1hqtq6.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=drew.adams@oracle.com \
    --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).