From: Yoni Rabkin <yoni@rabkins.net>
To: emacs-devel@gnu.org
Subject: TODO item: obsolete bug-reporting commands
Date: Wed, 27 Feb 2008 21:26:18 +0200 [thread overview]
Message-ID: <87y7962obp.fsf@rabkins.net> (raw)
Hello,
The TODO file says: "Check for any included packages that define
obsolete bug-reporting commands. Change them to use report-emacs-bug."
After taking a preliminary look at the emacs source, I have the
following questions:
What is the difference between reporter.el and emacsbug.el (the
emacs-devel archives seem to be silent on reporter.el)? The following
files use reporter.el:
calc-misc.el
dired-x.el
hilit19.el
viper-cmd.el
tramp-cmds.el
ps-mode.el
vera-mode.el
octave-mod.el
vhdl-mode.el
cc-mode.el
...and maybe a few more I couldn't find at first grep.
The following use emacsbug.el:
eshell.el
supercite.el
edebug.el
ffap.el
...once again, there may be more.
Some of the those use `define-obsolete-function-alias' to point at
report-emacs-bug for emacs version "23.1", and some use`defalias'
instead. Also, some autoload the alias, and some don't.
To recapitulate the questions:
1. Should Emacs packages which use reporter.el be converted to using
emacsbug.el and reporter.el retired?
2. Should report-emacs-bug be called using
`define-obsolete-function-alias' or `defalias'?
3. Should (2) be autoload-ed?
--
"Cut your own wood and it will warm you twice"
next reply other threads:[~2008-02-27 19:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 19:26 Yoni Rabkin [this message]
2008-02-28 19:24 ` TODO item: obsolete bug-reporting commands Glenn Morris
2008-02-29 5:04 ` Stefan Monnier
2008-02-29 7:18 ` Yoni Rabkin
2008-03-01 1:00 ` Xavier Maillard
2008-03-03 9:12 ` Yoni Rabkin
2008-03-03 21:09 ` Stefan Monnier
2008-03-03 21:09 ` Stefan Monnier
2008-03-08 10:22 ` Yoni Rabkin
2008-03-08 20:47 ` Stefan Monnier
2008-04-12 17:33 ` Yoni Rabkin
2008-04-12 19:37 ` Stefan Monnier
2008-04-15 16:50 ` Yoni Rabkin
2008-04-15 17:50 ` Stefan Monnier
2008-04-16 8:34 ` Yoni Rabkin
2008-04-16 14:10 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y7962obp.fsf@rabkins.net \
--to=yoni@rabkins.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.