all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dima Kogan <dima@secretsauce.net>
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 18:16:02 +0200	[thread overview]
Message-ID: <837fm53b25.fsf@gnu.org> (raw)
In-Reply-To: <87twpaha8u.fsf@secretsauce.net>

> From: Dima Kogan <dima@secretsauce.net>
> Date: Wed, 28 Oct 2015 15:57:37 -0700
> Cc: 21777@debbugs.gnu.org
> 
> Hi. Thanks for replying. Looking at gdb/utils.c, apparently gdb looks at
> the EMACS environment variable, which was set previously but is not
> anymore:
> 
> https://github.com/emacs-mirror/emacs/commit/beaab898968caf8b243a33d24824d430fabc31fc
> 
> This patch in emacs is what broke it. Options:
> 
> 1. revert above patch

That patch fixed a real-life bug, so I don't think reverting it is an
option we should seriously consider.

> 2. patch gdb to look at INSIDE_EMACS not EMACS

That should be done regardless, I will submit a patch to GDB.

> 3. handle this inside emacs, not relying on gdb behavior
> 
> I like 3. Emacs should be responsible for things emacs wants, not
> external applications, even if they're GNU applications.

3 is okay in principle, but you didn't show any specific suggestions.
What did you have in mind?

Please also keep in mind that "M-x gud-gdb" is a legacy command, and
the more modern "M-x gdb" doesn't have that problem.

There's also:

 4. Fix this locally in your GDB init files (using GDB scripting
    facilities).

> Also, it looks like gdb checks EMACS in a few more places, and I haven't
> looked at those yet.

Maybe I'm missing something, but I don't see any additional places
except the one pointed out by Andreas.





  reply	other threads:[~2015-10-29 16:16 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 [this message]
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
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=837fm53b25.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21777@debbugs.gnu.org \
    --cc=dima@secretsauce.net \
    --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.