unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: David Forrest <drf5n@mug.sys.virginia.edu>
Subject: Self-documentation adjustment
Date: Tue, 10 Dec 2002 20:32:19 -0500	[thread overview]
Message-ID: <Pine.LNX.4.33.0212101959450.9731-100000@mug.sys.virginia.edu> (raw)
In-Reply-To: <at60r3$cdisu$1@ID-142197.news.dfncis.de>

Is there a way to modify/advise the documentation strings in functions and
variables after they have been defined?

What I would be looking for would be something like the scenario:

C-h a mouse

;;; notice apropos-mouse-follow is not documented
;;; research it and then execute something like:

(document apropos-mouse-follow "Use the mouse to follow an apropos link.")

;;; and then have C-h a apropos-mouse-follow show the new documentation


apropos-mouse-follow	      <mouse-2>
  Use the mouse to follow an apropos link.


-------------------

I know I could redefine the function and edit my copy of the original
file, but I would like to be able to extend the documentation without
ham-handedly corrupting the underlying files, functions, or variables.

Thanks for your time,
Dave
-- 
 Dave Forrest    (434)924-3954w(111B) (804)642-0662h (804)695-2026p
 drf5n@virginia.edu             http://mug.sys.virginia.edu/~drf5n/

  reply	other threads:[~2002-12-11  1:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 14:24 xml indenting, possibly with psgml? Bjoern
2002-12-06 15:55 ` Jim Crossley
2002-12-10 23:13   ` Bjoern
2002-12-11 20:34     ` Kai Großjohann
2002-12-06 16:19 ` Stefan Monnier <foo@acm.com>
2002-12-10 23:29   ` Bjoern
2002-12-11  0:32     ` Bjoern
2002-12-11  1:32       ` David Forrest [this message]
2002-12-11 14:25         ` Self-documentation adjustment Stefan Monnier <foo@acm.com>
2002-12-11 14:53         ` Kevin Rodgers
2002-12-24  3:22         ` Moving a symbol from one obarray to another Greg Hill
2003-01-10  5:33   ` xml indenting, possibly with psgml? Gman
2003-01-12 20:46     ` Stefan Monnier <foo@acm.com>
2002-12-06 21:45 ` Michael Slass

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=Pine.LNX.4.33.0212101959450.9731-100000@mug.sys.virginia.edu \
    --to=drf5n@mug.sys.virginia.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. 
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).