Re: Release candidate for XEmacs 21.4.4 / my vacation
Don't forget the contents of /etc and $HOME. ;)
Seriously, though, it's a hard balancing act between collecting enough
information to be useful, and invading someone's privacy. That said, it's
not as if the report gets sent without the user's knowledge, so there
shouldn't be much to worry about. But for example, the user's .emacs file
might be a really helpful thing to include, but it might also contain
private information.
-Jim
----- Original Message -----
From: "Steve Youngs" <youngs(a)xemacs.org>
To: "XEmacs Beta" <xemacs-beta(a)xemacs.org>
Sent: Thursday, July 26, 2001 7:23 AM
Subject: Re: Release candidate for XEmacs 21.4.4 / my vacation
|--==> "SJT" == Stephen J Turnbull
<turnbull(a)sk.tsukuba.ac.jp> writes:
>>>>>>"APA" == Adrian Aichner <adrian(a)xemacs.org>
writes:
APA> This would add yet another complication to debugging people's
APA> setups who turn to comp.emacs.xemacs, stating: "My XEmacs
APA> does not work."
APA> In addition to the usual stuff we would have to find whether
APA> they run with any or some "lisp-updates".
SJT> Maybe we should add the feature list to M-x report-emacs-bug.
That,
SJT> in combination with the output of list-packages, would go a
long
way
SJT> toward identifying the configuration in use.
I'm going to patch emacsbug.el to make it report the installed
packages together with their versions. While I'm at it, what else
should 'report-emacs-bug' show?
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|