From: Dima Kogan <dima@secretsauce.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21777@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#21777: 25.0.50; gud-gdb uses a pager, which is harmful inside emacs
Date: Thu, 29 Oct 2015 20:43:35 -0700 [thread overview]
Message-ID: <87mvv1ggwo.fsf@secretsauce.net> (raw)
In-Reply-To: <87pozxgu3d.fsf@secretsauce.net>
Dima Kogan <dima@secretsauce.net> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Dima Kogan <dima@secretsauce.net>
>>>
>>> 3. handle this inside emacs, not relying on gdb behavior
>>
>> 3 is okay in principle, but you didn't show any specific suggestions.
>> What did you have in mind?
>
> gud-gdb.el can send a "set height unlimited" command when it starts the
> gdb process. I'm happy to give you a patch, if you want.
Something like this:
---------------------------------------------------------------------------
diff --git a/lisp/progmodes/gud.el b/lisp/progmodes/gud.el
index 9ab0667..61ae85c 100644
--- a/lisp/progmodes/gud.el
+++ b/lisp/progmodes/gud.el
@@ -785,6 +785,8 @@ directory and source-file directory for your debugger."
(setq gdb-first-prompt t)
(setq gud-running nil)
(setq gud-filter-pending-text nil)
+
+ (gud-basic-call "set height unlimited")
(run-hooks 'gud-gdb-mode-hook))
;; The completion process filter indicates when it is finished.
---------------------------------------------------------------------------
This works. The main issue is that it creates an extra "(gdb)" prompt
we'd want to suppress. You get the idea, however.
next prev parent reply other threads:[~2015-10-30 3:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 19:20 bug#21777: 25.0.50; gud-gdb uses a pager, which is harmful inside emacs Dima Kogan
2015-10-28 22:27 ` Andreas Schwab
2015-10-28 22:57 ` Dima Kogan
2015-10-29 16:16 ` Eli Zaretskii
2015-10-29 22:58 ` Dima Kogan
2015-10-30 3:43 ` Dima Kogan [this message]
2015-10-30 8:17 ` Eli Zaretskii
2015-10-30 9:13 ` Dima Kogan
2015-10-30 9:32 ` Eli Zaretskii
2015-10-30 14:01 ` Eli Zaretskii
2015-10-30 19:05 ` Dima Kogan
2015-10-30 20:34 ` Eli Zaretskii
2020-09-20 21:18 ` Lars Ingebrigtsen
2020-09-21 14:03 ` Eli Zaretskii
2020-09-21 14:07 ` Lars Ingebrigtsen
2020-09-22 15:46 ` Eli Zaretskii
2020-09-22 15:51 ` Lars Ingebrigtsen
2020-09-22 15:57 ` Andreas Schwab
2020-09-22 16:09 ` Eli Zaretskii
2020-09-22 16:19 ` Andreas Schwab
2020-09-22 16:51 ` Eli Zaretskii
2020-09-22 17:18 ` Andreas Schwab
2020-09-22 17:39 ` Eli Zaretskii
2020-09-22 17:46 ` Andreas Schwab
2020-09-23 12:53 ` Lars Ingebrigtsen
2020-09-23 14:41 ` Eli Zaretskii
2020-09-24 14:15 ` Lars Ingebrigtsen
2020-09-24 15:06 ` Eli Zaretskii
2020-09-25 9:55 ` Lars Ingebrigtsen
2020-09-24 14:16 ` Eli Zaretskii
2020-09-24 14:29 ` Lars Ingebrigtsen
2020-09-24 15:08 ` Eli Zaretskii
2015-10-30 7:54 ` Eli Zaretskii
2019-09-29 21:49 ` Stefan Kangas
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=87mvv1ggwo.fsf@secretsauce.net \
--to=dima@secretsauce.net \
--cc=21777@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=schwab@linux-m68k.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.