From: D. Goel <deego@glue.umd.edu>
Cc: emacs-devel@gnu.org
Subject: Re: patch to emacsbug.el proposed..
Date: 01 Sep 2002 20:13:36 -0400 [thread overview]
Message-ID: <87wuq5uu33.fsf@computer.localdomain> (raw)
In-Reply-To: <E17lefA-0003I7-00@fencepost.gnu.org>
>
> Isn't that method easier than remembering another command to do the
> job?
the user can still always follow the older method :). This will just
provide an additional way.
>
>
> imho, it would be nice if the system-info part of M-x
> report-emacs-bug could be separated into a nice function called, say
> insert-system-info..
>
> Would you envision using this interactively, or from a program?
[a] Interactively: i think i do, i would even prefer the shorter name
for the command that i suggested, "insert-system-info" and i even want
to locally bind it to a key. Often, i am writing an email to, say,
emacs-devel or gnu.emacs.help (which was not started via
report-emacs-bug), with, say, X problems etc., and then decide that it
would be relevant to include system-info..
[b] From a program: none (yet) that i can think of.
I think it will be nice to provide the user a way to easily insert
system-info, and help towards making "problem-reports" more
descriptive... Just as today peole ask users to post backtrace, they
might also start asking users with X problems etc. to M-x
insert-system-info :).
Anyways, no big deal, there's always the older method :)
DG http://24.197.159.102/~deego/
--
RIAA logic applied to cars--->
http://www.bbspot.com/News/2002/08/ride_sharing.html
next prev parent reply other threads:[~2002-09-02 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-31 19:57 patch to emacsbug.el proposed D. Goel
2002-09-02 0:01 ` Richard Stallman
2002-09-02 0:13 ` D. Goel [this message]
2002-09-03 13:26 ` Richard Stallman
2002-09-04 1:44 ` Miles Bader
2002-09-05 2:46 ` 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=87wuq5uu33.fsf@computer.localdomain \
--to=deego@glue.umd.edu \
--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 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).