5:08 a.m.
Here's what the new bug reports will look like. I'll put out a new
net-utils package asap.
--------------------------------------------------------------
This bug report will be sent to the XEmacs Development Team,
not to your local site managers!!
Please write in English, because the XEmacs maintainers do not have
translators to read other languages for them.
Please describe as succinctly as possible:
- What happened.
- What you thought should have happened.
- Precisely what you were doing at the time.
Please also include any C or lisp back-traces that you may have.
================================================================
Dear Bug Team!
Every time I switch my puter on I see this god ugly screen with a
multi-coloured flag flappin in the breeze and the words "Starting
Microsoft Windows....".
And then a couple of minutes later I see this blue screen saying
something about a "Fatal exception error".
The only thing I can do is to hit the 'reset' button and reboot.
================================================================
System Info to help track down your bug:
---------------------------------------
uname -a: Linux slackware 2.4.7 #1 Sun Jul 22 10:25:53 EST 2001 i686 unknown
./configure '--extra-verbose' '--dynamic=yes' '--with-gtk=no'
'--with-gnome=no' '--with-athena=next' '--with-menubars=lucid'
'--with-scrollbars=athena' '--with-dialogs=athena'
'--with-widgets=athena' '--with-png=yes'
'--with-sound=native,noesd' '--with-modules'
'--with-site-lisp=yes' '--with-site-modules=yes' '--pdump'
'--with-mule' '--error-checking=none' '--use-union-type'
'--with-clash-detection'
XEmacs 21.5-b2 "artichoke" configured for `i686-pc-linux'.
Compilation / Installation:
Source code location: /usr/local/src/xemacs
Installation prefix: /usr/local
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -g -O3 -Wall -Wno-switch -Winline
-Wmissing-prototypes -Wshadow -Wsign-compare
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11R6/include
- X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
Compiling in support for the Athena widget set:
- Athena headers location: X11/neXtaw
- Athena library to link: neXtaw
Using Lucid menubars.
Using Athena scrollbars.
Using Athena dialog boxes.
Using Athena native widgets.
TTY:
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Compiling in support for X-Face message headers.
Sound:
Compiling in support for sound (native).
Databases:
Compiling in support for Berkeley database.
Compiling in support for GNU DBM.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using raw Xlib to provide XIM support.
Mail:
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Compiling in support for dynamic shared object modules.
Using the union type for Lisp_Objects.
Using the new portable dumper.
Compiling in support for extra debugging code.
Installed XEmacs Packages:
-------------------------
((zenirc :version 1.11 :type regular)
(xslt-process :version 1.04 :type regular)
(xemacs-devel :version 1.37 :type single-file)
(xemacs-base :version 1.55 :type regular)
(w3 :version 1.2 :type regular)
(vm :version 6.95 :type regular)
(viper :version 1.26 :type regular)
(view-process :version 1.11 :type regular)
(vhdl :version 1.13 :type regular)
(vc-cc :version 1.16 :type regular)
(vc :version 1.28 :type regular)
(tpu :version 1.12 :type regular)
(tooltalk :version 1.13 :type regular)
(tm :version 1.29 :type regular)
(time :version 1.11 :type regular)
(textools :version 1.12 :type regular)
(text-modes :version 1.32 :type single-file)
(texinfo :version 1.2 :type regular)
(supercite :version 1.17 :type regular)
(strokes :version 1.08 :type regular)
(speedbar :version 1.21 :type regular)
(sounds-wav :version 1.1 :type regular)
(sounds-au :version 1.1 :type regular)
(slider :version 1.13 :type regular)
(sh-script :version 1.13 :type regular)
(sgml :version 1.08 :type regular)
(semantic :version 1.06 :type regular)
(scheme :version 1.11 :type regular)
(rmail :version 1.12 :type regular)
(reftex :version 1.23 :type regular)
(psgml :version 1.23 :type regular)
(ps-print-nomule :version 1.05 :type regular)
(prog-modes
:version
1
.4
:type
single-file)
(pcomplete :version 1.01 :type regular)
(pcl-cvs :version 1.55 :type regular)
(pc :version 1.2 :type single-file)
(os-utils :version 1.25 :type single-file)
(net-utils :version 1.18 :type single-file)
(misc-games :version 1.15 :type single-file)
(mine :version 1.14 :type regular)
(mh-e :version 1.13 :type regular)
(mew :version 1.14 :type regular)
(mailcrypt :version 2.09 :type regular)
(mail-lib :version 1.39 :type regular)
(jde :version 1.27 :type regular)
(ispell :version 1.22 :type regular)
(ilisp :version 1.19 :type regular)
(igrep :version 1.08 :type regular)
(idlwave :version 1.23 :type regular)
(hm--html-menus :version 1.16 :type regular)
(gnats :version 1.12 :type regular)
(games :version 1.13 :type regular)
(fsf-compat :version 1.09 :type single-file)
(frame-icon :version 1.09 :type regular)
(footnote :version 1.13 :type regular)
(eudc :version 1.33 :type regular)
(eterm :version 1.13 :type regular)
(eshell :version 1.01 :type regular)
(emerge :version 1.09 :type regular)
(elib :version 1.08 :type single-file)
(eieio :version 1.01 :type regular)
(efs :version 1.26 :type regular)
(edt :version 1.12 :type regular)
(edit-utils :version 1.64 :type single-file)
(ediff :version 1.31 :type regular)
(edebug :version 1.14 :type regular)
(dired :version 1.11 :type regular)
(debug :version 1.14 :type regular)
(crisp :version 1.12 :type regular)
(cookie :version 1.13 :type regular)
(cc-mode :version 1.25 :type regular)
(calendar :version 1.16 :type regular)
(calc :version 1.17 :type regular)
(c-support :version 1.16 :type single-file)
(build :version 1.02 :type regular)
(bbdb :version 1.13 :type regular)
(auctex :version 1.25 :type regular)
(apel :version 1.2 :type regular)
(ada :version 1.1 :type regular)
(Sun :version 1.13 :type regular)
(skk :version 1.19 :type regular)
(mule-base :version 1.39 :type regular)
(lookup :version 1.08 :type regular)
(locale :version 1.18 :type regular)
(leim :version 1.17 :type regular)
(egg-its :version 1.26 :type regular)
(edict :version 1.12 :type regular))
Features:
--------
(ansi-color shell makefile regexp-opt add-log env dired-faces
dired-xemacs dired ispell bbdb-gui bbdb-hooks sort gnus-cite
gnus-async gnus-topic nndraft nnmh gnus-cache nnfolder gnus-demon
supercite-steve mailcrypt rfc822 boxquote rect nnspool nntp earcon
gnus-audio gnus-score score-mode gnus-picon w3-forms w3-display
w3-imap w3-widget css font disp-table w3-mouse w3-vars w3-cus
w3-keyword url mm mule-sysdp url-parse url-vars gnus-ml gnus-msg
gnus-art mm-uu binhex uudecode mm-view gnus-sum nnoo gnus-group
gnus-undo nnmail mail-source format-spec gnus-start gnus-range
gnus-spec gnus-int gnus-win view-less view hyper-apropos bbdb-com
xemacsbug holidays lunar solar cal-dst cal-persia cal-julian diary-lib
appt calendar bbdb-w3 bbdb-sc supercite mail-extr regi bbdb-gnus gnus
gnus-ems gnus-xmas bbdb tex-site cperl-mode ibuffer dired-tar compile
time-stamp rsz-minibuf byte-optimize zenirc-color zenirc-trigger
zenirc-signal zenirc-notify zenirc-netsplit zenirc-format
zenirc-ignore zenirc-history zenirc-fill zenirc-dcc zenirc-complete
zenirc-away zenirc diff-mode ediff-merg ediff-diff ediff-tbar
ediff-wind ediff-help ediff-util ediff-mult ediff-init ediff vc-hooks
balloon-help lazy-shot efs-cu eicq-toolbar eicq bytecomp byte-compile
advice advice-preload smiley annotations goto-addr overlay thingatpt
wid-edit timezone outline browse-url sb-texinfo sb-info info speedbar
sb-image dframe assoc filladapt footnote mic-paren paren blink-paren
pending-del scroll-in-place redo savehist big-menubar time backup-dir
edmacro iswitchb message messagexmas mml mml-sec mml-smime mml2015 gpg
timer smime comint ring dig mm-decode mm-bodies mm-encode mailcap
mail-parse rfc2045 rfc2231 rfc2047 gnus-util qp ietf-drums time-date
parse-time mail-abbrevs sendmail nnheader nnheaderxm mm-util
mail-prsvr mail-utils mailheader crypt crypt++ history recent-files
font-lock func-menu x-compose cus-face blink-cursor zenirc-autoloads
xslt-process-autoloads xemacs-devel-autoloads xemacs-base-autoloads
w3-autoloads vm-autoloads viper-autoloads view-process-autoloads
vhdl-autoloads vc-cc-autoloads vc-autoloads tpu-autoloads
tooltalk-autoloads tm-autoloads time-autoloads textools-autoloads
text-modes-autoloads texinfo-autoloads supercite-autoloads
strokes-autoloads speedbar-autoloads sounds-wav-autoloads
sounds-au-autoloads slider-autoloads sh-script-autoloads
sgml-autoloads semantic-autoloads scheme-autoloads rmail-autoloads
reftex-autoloads psgml-autoloads ps-print-nomule-autoloads
prog-modes-autoloads pcomplete-autoloads pcl-cvs-autoloads
pc-autoloads os-utils-autoloads net-utils-autoloads
misc-games-autoloads mine-autoloads mh-e-autoloads mew-autoloads
mailcrypt-autoloads mail-lib-autoloads jde-autoloads ispell-autoloads
ilisp-autoloads igrep-autoloads idlwave-autoloads
hm--html-menus-autoloads gnats-autoloads games-autoloads
fsf-compat-autoloads frame-icon-autoloads footnote-autoloads
eudc-autoloads eterm-autoloads eshell-autoloads emerge-autoloads
elib-autoloads eieio-autoloads efs-autoloads edt-autoloads
edit-utils-autoloads ediff-autoloads edebug-autoloads dired-autoloads
debug-autoloads crisp-autoloads cookie-autoloads cc-mode-autoloads
calendar-autoloads calc-autoloads c-support-autoloads build-autoloads
bbdb-autoloads auctex-autoloads apel-autoloads ada-autoloads
Sun-autoloads skk-autoloads mule-base-autoloads lookup-autoloads
locale-autoloads leim-autoloads egg-its-autoloads edict-autoloads
eicq-autoloads -autoloads loadhist auto-show fontl-hooks x-iso8859-1
slovenian czech romanian ccl mule-help code-cmds gutter-items
menubar-items x-menubar mode-motion mouse itimer auto-save lisp-mode
easymenu iso8859-1 page buff-menu lib-complete cus-file derived frame
text-props obsolete cus-start custom widget cl-extra mini-cl cl cl-19
packages backquote very-early-lisp file-coding mule athena-scrollbars
cut-buffer lucid-menubars athena-dialogs x c-balloon-help tty-frames
tty toolbar native-sound scrollbar unix-processes multicast
network-streams subprocesses modules menu-accelerator-support menubar
berkeley-db dbm md5 xemacs xim gutter tiff png gif jpeg xface xpm xbm
lisp-float-type linux dialog devices window-system base64)
Recent keystrokes:
-----------------
right right right right right right right right right
right right right right right right right right x down
left left left left left left x up C-x 4 a U s e SPC
' r e p o r t - x e m a c s - b u g ' . f7 C-x k RET
C-x 0 C-s C-s C-s C-s C-a f7 C-x k RET C-x k RET M-x
g n u s RET n n n n n n n n n n n n n n n n q M-x up
up up RET
Recent messages (most recent first):
-----------------------------------
Parsing BBDB... (frobnicating...)
Parsing BBDB... (reading...)
Parsing BBDB...
(No changes need to be saved)
Destroying external MIME viewers
Checking new news...done
Opening nndraft server...
Checking new news...
No new newsgroups
Opening nnfolder server on saved-messages...
Opening nnfolder server...
Generating the cache active file...done
Generating the cache active file...
Reading active file from archive via nnfolder...done
Reading active file from archive via nnfolder...
Opening nnfolder server on archive...
Reading active file from archive via nnfolder...
Reading active file from saved-messages via nnfolder...done
Reading active file from saved-messages via nnfolder...
Opening nnfolder server on saved-messages...
User Init File:
--------------
;; -*- Emacs-Lisp -*-
;; Add ~/etc/XEmacs to the load-path
(push (expand-file-name "~/etc/XEmacs/") load-path)
;:*======================
;:* This is where it all starts...
(load "fonts-steve")
(load "variables-steve")
(load "keys-steve")
(load "packages-steve")
(load "misc-steve")
(load "c-and-java-steve")
(load "perl-steve")
(load "w3-steve")
(load "latex-steve")
(load "html-steve")
(load "bbdb-steve")
(load "calendar-steve")
(load "sounds-steve")
(load "modes-steve")
;:* XEmacs ready for take-off!!!
;:*======================
(let* ((string "XEmacs ready for take-off!!!"))
(string-match "XEmacs ready for take-off!!!" string)
(put-text-property (match-beginning 0) (match-end 0) 'face 'bold string)
(display-message 'message string)
(sit-for 1))
(message "XEmacs ready for take-off!!")
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
7:03 a.m.
On Mon, 06 Aug 2001 14:08:03 +1000, Steve Youngs <youngs(a)xemacs.org> said:
Every time I switch my puter on I see this god ugly screen with a
multi-coloured flag flappin in the breeze and the words "Starting
Microsoft Windows....".
And then a couple of minutes later I see this blue screen saying
something about a "Fatal exception error".
The only thing I can do is to hit the 'reset' button and reboot.
Damn. Don't *DO* that to me at 2AM local time. I had to re-read it about 3 times
before I saw your comment about "here's how it will look" and realized it
was a rigged demo ;)
/Valdis (who has seen too many SirCam attachments this week ;)
2:59 p.m.
|--==> "VK" == Valdis Kletnieks <Valdis.Kletnieks(a)vt.edu> writes:
VK> On Mon, 06 Aug 2001 14:08:03 +1000, Steve Youngs <youngs(a)xemacs.org>
said:
>Every time I switch my puter on I see this god ugly screen with a
>multi-coloured flag flappin in the breeze and the words "Starting
>Microsoft Windows....".
>
>And then a couple of minutes later I see this blue screen saying
>something about a "Fatal exception error".
>
>The only thing I can do is to hit the 'reset' button and reboot.
VK> Damn. Don't *DO* that to me at 2AM local time. I had to re-read it about 3
times
VK> before I saw your comment about "here's how it will look" and
realized it
VK> was a rigged demo ;)
It was probably because the bug report was so believable. :-)
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
1:42 p.m.
Steve Youngs writes:
Here's what the new bug reports will look like. I'll put out
a new
net-utils package asap.
I like the new bug report format, but wonder if including the users's
.emacs file might be going a bit too far. Some people might have
plaintext passwords in this file (e.g. in setting the variable
`vm-spool-files' for POP access). Admittedly storing plaintext
passwords in your .emacs file isn't a great idea, but people may not
realize that when they file a bug report their .emacs file is going to
get broadcast not only to the mailing list but also archived in the
mailing list archives, where it can be read by anybody on the Wild
Wild Web...
Another thought - we are constantly plagued by people reporting dired
and efs bugs to the main list, which always generates the pedantic
replies "Please use dired-report-bug" or "Please use efs-report-bug".
It would be really great if there were a single function for bug
reporting. While it would take a lot to try to determine (either from
the backtrace or from the user's description) whether the bug was a
dired bug, an efs bug, or an "other" bug, maybe at the very least the
new bug report template could include some wording, preferably right
near the top, saying: "If this is a bug in the FOO package, please use
FOO-report bug; if this is a bug in the BAR package, please use
BAR-report bug, else use this bug report form".
Daydreaming a bit, one could imagine a "hook" system where different
packages added to the report-bug-hook, thereby obviating the need for
N different FOO-report-bug functions.... but this sounds like work.
Including a bit of text in the template would be easy and would
eliminate some amount of frustration.
2:58 p.m.
|--==> "CGW" == Charles G Waldman <Charles> writes:
CGW> Steve Youngs writes:
>Here's what the new bug reports will look like. I'll put
out a new
>net-utils package asap.
CGW> I like the new bug report format, but wonder if including the users's
CGW> .emacs file might be going a bit too far. Some people might have
CGW> plaintext passwords in this file (e.g. in setting the variable
CGW> `vm-spool-files' for POP access).
Which is why I put...
,----
| (princ "\n\n
| You are very welcome to scan through the bug report and remove any
| potentially sensitive data.")
`----
Which shows up in the Bug Help buffer.
CGW> Another thought - we are constantly plagued by people reporting dired
CGW> and efs bugs to the main list, which always generates the pedantic
CGW> replies "Please use dired-report-bug" or "Please use
efs-report-bug".
CGW> It would be really great if there were a single function for bug
CGW> reporting. While it would take a lot to try to determine (either from
CGW> the backtrace or from the user's description) whether the bug was a
CGW> dired bug, an efs bug, or an "other" bug, maybe at the very least the
CGW> new bug report template could include some wording, preferably right
CGW> near the top, saying: "If this is a bug in the FOO package, please use
CGW> FOO-report bug; if this is a bug in the BAR package, please use
CGW> BAR-report bug, else use this bug report form".
CGW> Daydreaming a bit, one could imagine a "hook" system where different
CGW> packages added to the report-bug-hook, thereby obviating the need for
CGW> N different FOO-report-bug functions.... but this sounds like work.
CGW> Including a bit of text in the template would be easy and would
CGW> eliminate some amount of frustration.
Agreed. Something like...
"A lot of the XEmacs Packages have their own bug reporting functions.
If the bug report you are about to fill out is for an XEmacs Package,
please check to see if that package has it's own bug reporting system
and use that. That way, your bug report is sure to be read by the
right people."
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
6:54 p.m.
Anyone use Debian's "reportbug" tool? It's very nice. It actually
queries the BTS and lets you see what bugs have already been
submitted against a package. You can add to a report, or abort if
the bug has already been reported.
9:49 p.m.
|--==> "KMH" == Karl M Hegbloom <karlheg(a)hegbloom.net> writes:
KMH> Anyone use Debian's "reportbug" tool? It's very nice. It
actually
KMH> queries the BTS and lets you see what bugs have already been
KMH> submitted against a package. You can add to a report, or abort if
KMH> the bug has already been reported.
Sounds cool, you reckon you could port it to lisp? :-)
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
2:32 p.m.
Steve Youngs writes:
Here's what the new bug reports will look like. I'll put out
a new
net-utils package asap.
[snip]
Please also include any C or lisp back-traces that you may have.
================================================================
Dear Bug Team!
Every time I switch my puter on I see this god ugly screen with a
multi-coloured flag flappin in the breeze and the words "Starting
Microsoft Windows....".
And then a couple of minutes later I see this blue screen saying
something about a "Fatal exception error".
The only thing I can do is to hit the 'reset' button and reboot.
================================================================
<geek humor>
well the only solution i can suggest for this "feature" is to install
a UNIX based OS here is a few web sites to look at
freebsd.org linux.org debian.org slackware.org
</geek humor>
:)
couldnt help myself, had to do it.
System Info to help track down your bug:
---------------------------------------
this looks good steve
there is concern for including the users init.el file
cause it may contain passwords
maybe we could borrow from adrians build package and do a "dont
include these lines" thing so the users password's won't get emailed to
everyone on the list and such
i could do it in perl but not lisp (still teaching myself)
does this sound good ???
[snip]
--
-------------------------------------------------------------------------
Peter (Rendhalver)
XEmacs Advocate
Perl Hacker
Apache God
FreeBSD Devote
rendhalver(a)users.sourceforge.net
There are only two things that are infinite,
the universe and human stupidity,
and i am not certain about the former
- Albert Einstein
-------------------------------------------------------------------------
2:36 p.m.
Steve Youngs <youngs(a)xemacs.org> writes:
Here's what the new bug reports will look like. I'll put out
a new
net-utils package asap.
Ummm... do you really think it is a good idea to include the user's
initialization file? There could be sensitive information in there.
-bp
--
Ceterum censeo vi esse delendam
4:17 p.m.
|--==> "WMP" == William M Perry <wmperry(a)gnu.org> writes:
WMP> Steve Youngs <youngs(a)xemacs.org> writes:
>Here's what the new bug reports will look like. I'll put
out a new
>net-utils package asap.
WMP> Ummm... do you really think it is a good idea to include the user's
WMP> initialization file? There could be sensitive information in there.
I've included a clause in the Bug Help buffer that basically says "hey
have a look at the report before you send it and delete any sensitive
data". Is that good enough?
Or is the general consensus "get rid of the init file, we don't want
or need it in our bug reports"?
I actually thought it was a good idea, but it wouldn't be the first
time that one of my "good" ideas turned out to be not so good. :-)
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
4:34 p.m.
Steve Youngs writes:
Or is the general consensus "get rid of the init file, we
don't want
or need it in our bug reports"?
I actually thought it was a good idea, but it wouldn't be the first
time that one of my "good" ideas turned out to be not so good. :-)
It's not that it isn't useful; I just think this puts too much of a
burden on clueless users. Oh, I forgot, there are no clueless XEmacs
users ;-)
4:52 p.m.
Steve Youngs writes:
|--==> "WMP" == William M Perry <wmperry(a)gnu.org>
writes:
WMP> Steve Youngs <youngs(a)xemacs.org> writes:
>>Here's what the new bug reports will look like. I'll put out a new
>>net-utils package asap.
WMP> Ummm... do you really think it is a good idea to include the user's
WMP> initialization file? There could be sensitive information in there.
I've included a clause in the Bug Help buffer that basically says "hey
have a look at the report before you send it and delete any sensitive
data". Is that good enough?
did you see my suggestion ???
basically dont include the lines with passwords on them
Or is the general consensus "get rid of the init file, we
don't want
or need it in our bug reports"?
I actually thought it was a good idea, but it wouldn't be the first
time that one of my "good" ideas turned out to be not so good. :-)
it is a good idea steve
would be very helpful to know what stuff has been customised
i for one have my email passwords in a separete file anyway
and i assume most of the serious beta-testers have as well
its cool to be able to split up the config into logical units
but new users might not have grocked this yet
so not including the lines with passwords, or replacing the password
with appropriate charaters would help in this instance
--
-------------------------------------------------------------------------
Peter (Rendhalver)
XEmacs Advocate
Perl Hacker
Apache God
FreeBSD Devote
rendhalver(a)users.sourceforge.net
There are only two things that are infinite,
the universe and human stupidity,
and i am not certain about the former
- Albert Einstein
-------------------------------------------------------------------------
5:03 p.m.
Peter Brown writes:
did you see my suggestion ???
basically dont include the lines with passwords on them
I don't think this is possible. It's more complicated than
"grep -v password .emacs" I don't know how you can parse a .emacs
file and hope to determine what is and what is not a password.
What if I have
(setq carbuncle "my-super-secret-password")
...
(set vm-spool-files
(format "foo:110:pass:me:%s"
carbuncle))
In fact, I believe that since .emacs can contain any valid Lisp
expression, the problem of determining what is and is not a password
is equivalent to solving the Halting problem....
Let's err on the side of caution and just not include the .emacs file,
OK?
5:27 p.m.
Charles G Waldman writes:
Peter Brown writes:
>
> did you see my suggestion ???
> basically dont include the lines with passwords on them
I don't think this is possible. It's more complicated than
"grep -v password .emacs" I don't know how you can parse a .emacs
file and hope to determine what is and what is not a password.
What if I have
(setq carbuncle "my-super-secret-password")
...
(set vm-spool-files
(format "foo:110:pass:me:%s"
carbuncle))
In fact, I believe that since .emacs can contain any valid Lisp
expression, the problem of determining what is and is not a password
is equivalent to solving the Halting problem....
good point
im more a perl hacker than a lisp hacker so i respect your greater knowledge
i agree, it would be a nightmare in those cases
thanks for the impromptu lisp lesson btw :)
Let's err on the side of caution and just not include the .emacs
file,
OK?
yep im with you
--
-------------------------------------------------------------------------
Peter (Rendhalver)
XEmacs Advocate
Perl Hacker
Apache God
FreeBSD Devote
rendhalver(a)users.sourceforge.net
There are only two things that are infinite,
the universe and human stupidity,
and i am not certain about the former
- Albert Einstein
-------------------------------------------------------------------------
10:45 p.m.
On Mon, 6 Aug 2001, Charles G. Waldman gibbered:
In fact, I believe that since .emacs can contain any valid Lisp
expression, the problem of determining what is and is not a password
is equivalent to solving the Halting problem....
It's worse than that. Because the user may have passwords in there which
will be used by packages that aren't installed yet (I have a couple like
that for things I haven't got around to installing) the bug-reporting
package would also need to be either telepathic, or clairvoyant, or of
human-level intelligence, or all three.
Also, it's no use for complex .emacs's: Mine has, just after the start,
(require 'init-prog-modes) ; Initialize programming-language-related stuff.
(require 'init-message-modes) ; Initialize email/news-related stuff.
and a bunch of others. Working out which `require' is needed could be
tricky.
(Plus, there's >2000 lines of sitewide config. You want that mailed as
well? And all locally installed and patched site-packages? This starts
to sound like a DoS attack...)
The replicability problem with (X)Emacs bugs on sites with complex
configuration will always remain, I think; the good part is that sites
with complex configuration probably have a local (X)Emacs guru who can
be trusted to do most of the debugging work on his own...
--- btw, my line_number_cache corruption patch from last month is still
quasi-unreviewed...
--
`It's all about bossing computers around. Users have to say "please".
Programmers get to say "do what I want NOW or the hard disk gets it".'
-- Richard Heathfield on the nature of programming
4:52 p.m.
>>>> "SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> |--==> "WMP" == William M Perry <wmperry(a)gnu.org> writes:
WMP> Steve Youngs <youngs(a)xemacs.org> writes:
>> Here's what the new bug reports will look like. I'll
put out a new
>> net-utils package asap.
WMP> Ummm... do you really think it is a good idea to include the user's
WMP> initialization file? There could be sensitive information in there.
SY> I've included a clause in the Bug Help buffer that basically says
"hey
SY> have a look at the report before you send it and delete any sensitive
SY> data". Is that good enough?
SY> Or is the general consensus "get rid of the init file, we don't want
SY> or need it in our bug reports"?
Would you want to debug the users init file? I wouldn't. So whether
or not the init file contains sensitive data, I'd wouldn't want it
because I wouldn't use it.
Besides, let's be safe with user's data. Sometimes that C-c C-c comes
too fast before I've had a chance to think about it.... :-)
Ray
5:21 p.m.
Please don't include the user's .emacs or init.el file. I consider
including it to be an invasion of the user's privacy. If you want to
create a mechanism to allow the user optionally to include his/her
startup file, I think that's OK, as long as that defaults to off.
- vin
Raymond Toy <toy(a)rtp.ericsson.se> writes:
>>>>> "SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> |--==> "WMP" == William M Perry <wmperry(a)gnu.org> writes:
WMP> Steve Youngs <youngs(a)xemacs.org> writes:
>>> Here's what the new bug reports will look like. I'll put out a
new
>>> net-utils package asap.
WMP> Ummm... do you really think it is a good idea to include the user's
WMP> initialization file? There could be sensitive information in there.
SY> I've included a clause in the Bug Help buffer that basically says
"hey
SY> have a look at the report before you send it and delete any sensitive
SY> data". Is that good enough?
SY> Or is the general consensus "get rid of the init file, we don't want
SY> or need it in our bug reports"?
Would you want to debug the users init file? I wouldn't. So whether
or not the init file contains sensitive data, I'd wouldn't want it
because I wouldn't use it.
Besides, let's be safe with user's data. Sometimes that C-c C-c comes
too fast before I've had a chance to think about it.... :-)
Ray
1:50 a.m.
|--==> "VS" == Vin Shelton <acs(a)xemacs.org> writes:
VS> If you want to create a mechanism to allow the user optionally
VS> to include his/her startup file, I think that's OK, as long as
VS> that defaults to off.
This is what I've done now.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
3:26 a.m.
Thanks, Steve.
- vin
Steve Youngs <youngs(a)xemacs.org> writes:
|--==> "VS" == Vin Shelton <acs(a)xemacs.org>
writes:
VS> If you want to create a mechanism to allow the user optionally
VS> to include his/her startup file, I think that's OK, as long as
VS> that defaults to off.
This is what I've done now.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
8298
days inactive
8303
days old
18 comments
9 participants
participants (9)
-
Charles Waldman -
Karl M. Hegbloom -
Nix -
Peter Brown -
Raymond Toy -
Steve Youngs -
Valdis Kl=?iso8859-4?Q?=BA?=tnieks -
Vin Shelton -
William M. Perry