From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: gdb patch to suppress empty lines, re-visited
Date: Wed, 11 Dec 2002 22:17:00 -0000 [thread overview]
Message-ID: <200212120552.gBC5qIf16063@duracef.shout.net> (raw)
I've often wished for this feature as a user of gdb.
My vote: yes, provided that it doesn't systemically hose the test
suite. There are some tests that explicitly check that repeated
commands work and it's fine to update those. But I am gun shy of
readline and its mysterious refresh algorithms now and I don't want
gdb to start issuing "(gdb) ^M(gdb) p^M(gdb) pr^M(gdb) pri..."
style output.
Michael C
next reply other threads:[~2002-12-12 5:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 22:17 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2002-12-13 13:36 ` Per Bothner
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=200212120552.gBC5qIf16063@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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