From: Eli Zaretskii <eliz@gnu.org>
To: Joe Wells <jbw@macs.hw.ac.uk>
Cc: bug-gnu-emacs@gnu.org, rms@gnu.org
Subject: Re: Emacs exited with message “X protocol error: BadPixmap”
Date: Tue, 14 Aug 2007 06:07:33 +0300 [thread overview]
Message-ID: <u1we6eruy.fsf@gnu.org> (raw)
In-Reply-To: <86odhbdv5l.fsf@macs.hw.ac.uk> (message from Joe Wells on Mon, 13 Aug 2007 21:41:42 +0100)
> Cc: rms@gnu.org, bug-gnu-emacs@gnu.org
> From: Joe Wells <jbw@macs.hw.ac.uk>
> Date: Mon, 13 Aug 2007 21:41:42 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Joe Wells <jbw@macs.hw.ac.uk>
> >> Date: Mon, 13 Aug 2007 06:20:53 +0100
> >> Cc: bug-gnu-emacs@gnu.org
> >>
> >> Sorry, I'm not going to run Emacs under GDB indefinitely just on the
> >> off chance Emacs will crash.
> >
> > Why not? As long as Emacs doesn't crash, you will not notice any
> > difference in behavior or performance--GDB is simply invisible until
> > there's some event that is noteworthy for the debugger.
>
> I'm not going to run every program on my system under the debugger
> forevermore on the off chance that the program might crash!
You just reiterated what you said before, but didn't explain why. Can
you say why you don't like the idea? I tried to point out that a
debugger will stay out of your way as long as the program runs
normally, so you should not see any ill effects.
next prev parent reply other threads:[~2007-08-14 3:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 1:20 Emacs exited with message “X protocol error: BadPixmap” Joe Wells
2007-08-12 17:56 ` Richard Stallman
2007-08-12 18:17 ` Joe Wells
2007-08-13 5:01 ` Richard Stallman
2007-08-13 5:20 ` Joe Wells
2007-08-13 19:41 ` Eli Zaretskii
2007-08-13 20:41 ` Joe Wells
2007-08-14 0:28 ` Richard Stallman
2007-08-14 8:27 ` Kim F. Storm
2007-08-14 19:23 ` Eli Zaretskii
2007-08-14 23:26 ` Richard Stallman
2007-08-14 3:07 ` Eli Zaretskii [this message]
2007-08-14 0:27 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u1we6eruy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=jbw@macs.hw.ac.uk \
--cc=rms@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.