unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dima@secretsauce.net
Cc: 21777@debbugs.gnu.org
Subject: bug#21777: 25.0.50; gud-gdb uses a pager, which is harmful inside emacs
Date: Fri, 30 Oct 2015 16:01:01 +0200	[thread overview]
Message-ID: <83y4ekzc9u.fsf@gnu.org> (raw)
In-Reply-To: <838u6k1z28.fsf@gnu.org>

> Date: Fri, 30 Oct 2015 11:32:47 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 21777@debbugs.gnu.org, schwab@linux-m68k.org
> 
> > - we have a variable 'gud-gdb-set-height-unlimited',
> >   which has 3 states: uninitialized, yes, no
> > 
> > - when gud starts up, if it's 'uninitialized', we ask the user if they
> >   want to override, and whether to do so in the future; if they say yes,
> >   we update their .emacs.d/init.el. narrow-to-region has this type of
> >   user querying. We override only if it's 'yes'
> 
> Why not a simpler boolean, off by default?  This problem will go away
> soon enough, so maybe solutions that are too complicated would be
> over-engineering it?

I think if we have such an option, and it's by default off, we might
consider not bothering about gdbinit commands that contradict the
effect of that option.  The option gives users enough power to decide
what they want more.

WDYT?





  reply	other threads:[~2015-10-30 14:01 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
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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83y4ekzc9u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21777@debbugs.gnu.org \
    --cc=dima@secretsauce.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).