From: Thien-Thi Nguyen <ttn@glug.org>
Cc: gnu-emacs-bug@prep.ai.mit.edu
Subject: Re: Bugs in "Send Bug Report" command
Date: 21 Mar 2002 16:48:07 -0500 [thread overview]
Message-ID: <jkofhhy4mg.fsf@glug.org> (raw)
In-Reply-To: Järneström Jonas's message of "Thu, 21 Mar 2002 12:52:04 +0100"
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
Järneström Jonas <Jonas.Jarnestrom@ki.ericsson.se> writes:
I thought hooks was intended for additions/modifications by individual
users rather than a means of official bug fixes of the main code? :-)
the concept of hooks is non-specific. emacs conventional hooks are for users,
but the report-emacs-bug-hook (function) serves the bug reporting mechanism
primarily. (this function is added to mail-send-hook, a normal hook.) in
this case, the function name is confusing because it ends in "-hook"; maybe it
is better to rename it report-emacs-bug-confirm-and-send, since that is what
it does.
the code snippet posted was added to this function rather than added as a new
hook. see emacsbug.el for more info.
thi
_______________________________________________
Bug-gnu-emacs mailing list
Bug-gnu-emacs@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs
next prev parent reply other threads:[~2002-03-21 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200203201553.g2KFrHYg028440@skurup.eral.ericsson.se>
2002-03-21 3:38 ` Bugs in "Send Bug Report" command D. Goel
2002-03-21 6:29 ` Eli Zaretskii
2002-03-22 12:24 ` Richard Stallman
2002-03-22 14:12 ` Eli Zaretskii
2002-03-21 13:05 ` Järneström Jonas
2002-03-21 14:23 ` D. Goel
[not found] ` <jkr8mey8dm.fsf@glug.org>
2002-03-21 11:52 ` Järneström Jonas
2002-03-21 21:48 ` Thien-Thi Nguyen [this message]
2002-03-22 12:26 ` Richard Stallman
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=jkofhhy4mg.fsf@glug.org \
--to=ttn@glug.org \
--cc=gnu-emacs-bug@prep.ai.mit.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.
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).