From: David Carlton <carlton@math.stanford.edu>
To: Per Bothner <per@bothner.com>
Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: gdb patch to suppress empty lines, re-visited
Date: Fri, 13 Dec 2002 12:53:00 -0000 [thread overview]
Message-ID: <ro1r8clr6iy.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <3DFA356F.6000405@bothner.com>
On Fri, 13 Dec 2002 11:30:55 -0800, Per Bothner <per@bothner.com> said:
> A few people have expresses themselves in favor, and none
> have been opposed. I don't know if that counts as a consensus ...
I don't know if I like it or not, and I don't think I'll know until
I've actually tried it. My first reaction is slightly negative, and
I'm not at all sure how well it will work with XEmacs's GDB mode: if I
do a bunch of steps through a function, I get output like this:
(gdb) s
(gdb)
(gdb)
(gdb)
(gdb)
(gdb)
(gdb)
because the mode isn't showing me the source code information in that
buffer (since it's available in another buffer), and I can't imagine
your patch doing anything good to that output. (I have no idea what
GNU Emacs's GDB mode looks like: for some reason, XEmacs uses a
different (older?) one.) So if your patch would change the output in
this situation, I'm dubious. But maybe it wouldn't; I'm not sure if
the ISATTY (instream) guard would protect against this situation.
I guess if it doesn't affect the output under (X)Emacs then I don't
care one way or another because I'll never see its results.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-12-13 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 23:01 Per Bothner
2002-12-11 15:38 ` Michael Snyder
2002-12-11 15:50 ` Per Bothner
2002-12-11 16:01 ` Daniel Jacobowitz
2002-12-13 12:22 ` Per Bothner
2002-12-13 12:38 ` Andrew Cagney
[not found] ` <ac131313@redhat.com>
2002-12-13 12:44 ` Kevin Buettner
2002-12-13 13:16 ` Daniel Jacobowitz
2002-12-13 13:49 ` Per Bothner
2002-12-13 12:53 ` David Carlton [this message]
2002-12-13 13:36 ` Per Bothner
2002-12-11 22:17 Michael Elizabeth Chastain
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=ro1r8clr6iy.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@redhat.com \
--cc=per@bothner.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox