unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: each command's date of birth without looking in OONEWS
Date: 19 Jul 2002 07:02:50 +0800	[thread overview]
Message-ID: <87r8i0bpwl.fsf_-_@jidanni.org> (raw)
In-Reply-To: vaf1ya1gs7t.fsf@lucy.cs.uni-dortmund.de

K> There is dired-jump (from dired-x, I think).

oops.  so there it was all along.  But how long?
PROPOSAL
Want a command that will show just when another command joined emacs,
without one having to pour thru OONEWS files.
For instance, C-x C-j is bound to dired-jump, but for just how long
has this been the case?  Well, such dates could come up with C-h f
output, or maybe another specialized command could be made.  A mere
C-? C-? C-x C-j would tell me
C-x C-j has been bound to dired-jump since 3 Sep 1998
dired-jump has existed since 2 Sep 1997
it was implemented by RMS
upon the urging of Chip Fiasco
with the assistance of Chuck Burger
after an idea posted by Clark Kvnt 

OK, it is easy enough to see the source dired-x.el however the dates
of birth of each individual command have been thrown away, and all be
know is the date list at the top of the file...

Anyways, maybe put the date of birth of each function into its
docstring. I mean many man pages have "a xxxx command existed in
Version 7 UNIX", "Example of <xxx> in HTML 2.0, 3.2..."
-- 
http://jidanni.org/ Taiwan(04)25854780

  reply	other threads:[~2002-07-18 23:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 20:29 add: dired cursor upon file I was just in Dan Jacobson
2002-07-18 12:01 ` Kai Großjohann
2002-07-18 23:02   ` Dan Jacobson [this message]
2002-07-19 11:58     ` each command's date of birth without looking in OONEWS Alfred M. Szmidt
2002-07-26 20:49       ` Dan Jacobson

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=87r8i0bpwl.fsf_-_@jidanni.org \
    --to=jidanni@dman.ddts.net \
    /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).