unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Drew Adams <drew.adams@oracle.com>,
	"Stephen J. Turnbull" <stephen@xemacs.org>,
	emacs-devel <emacs-devel@gnu.org>
Subject: RE: Changes in revision 114466
Date: Mon, 30 Sep 2013 22:27:09 -0700 (PDT)	[thread overview]
Message-ID: <abf3509b-9467-4af9-a7ee-69707e7ea57e@default> (raw)
In-Reply-To: <fe13424f-f4c8-47f8-9240-62ef57703e58@default>

> >  > What we might want/need (I have proposed this several times, and so
> >  > have others) is linking from doc strings to the manuals.  That would
> >  > indeed be useful, IMO.  It would provide missing glue, as you put it.
> >  >
> >  > There are a very few doc strings, IIRC, that actually do this.  It
> >  > would be good to generalize it, or at least make use of it more.
> >
> > XEmacs has `Info-elisp-ref' which jumps to the Elisp manual entry for
> > a function, defaulting to the function at point.  Add a fallback to
> > the current docstring's function, and you're most of the way there
> > (the problem being that I-e-r currently doesn't know how to check
> > other manuals than the Lispref).
> 
> GNU Emacs has `info-lookup-symbol', which is bound to `C-h S' globally,
> so you can use it anywhere.  But users are not necessarily aware of it.
> It would be good to provide explicit (visible) links for some symbols
> in some doc strings.

Here is a previous discussion of this, FWIW.
http://lists.gnu.org/archive/html/emacs-devel/2009-01/msg00938.html



  reply	other threads:[~2013-10-01  5:27 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 [this message]
2013-10-01  6:11                     ` Stephen J. Turnbull
2013-10-01  7:44                       ` Drew Adams
2013-10-01  8:29                         ` Stephen J. Turnbull

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=abf3509b-9467-4af9-a7ee-69707e7ea57e@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=stephen@xemacs.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).