unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dima Kogan <dima@secretsauce.net>
Cc: 21528@debbugs.gnu.org
Subject: bug#21528: 25.0.50; gud tries to guess what file we're debugging, which can take a long	time
Date: Mon, 21 Sep 2015 10:04:28 +0300	[thread overview]
Message-ID: <83oagwnthf.fsf@gnu.org> (raw)
In-Reply-To: <87r3ls8p02.fsf@secretsauce.net>

> From: Dima Kogan <dima@secretsauce.net>
> Date: Sun, 20 Sep 2015 19:50:21 -0700
> 
> Hi. Currently when the user invokes any gud-based mode ('M-x pdb' for
> instance) the minibuffer pops up with a suggested command. This command
> tries to guess what you're trying to debug based on some pretty
> arbitrary heuristics. This is in 'gud-query-cmdline' in gud.el
> 
> These heuristics include looking at each file in the current directory
> to find the most recent executable file. In my experience this almost
> never is what I want. If I'm doing remote debugging with tramp and the
> current directory has many files in it, then emacs can sit there for a
> very long time before opening the minibuffer, while it looks at all the
> files in the remote directory. I think this delay changes this behavior
> from not-useful to harmful, and I think it should be removed. Thoughts?

Removing it altogether, based on your personal and very specific use
case, would be too drastic, IMO.  Can you propose some less drastic
measure?  If nothing smarter could be done automatically, a defcustom
to control this should be a stopgap, I think.

And while at that: the search for executables could bypass certain
files, like shell scripts, for example.





  reply	other threads:[~2015-09-21  7:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21  2:50 bug#21528: 25.0.50; gud tries to guess what file we're debugging, which can take a long time Dima Kogan
2015-09-21  7:04 ` Eli Zaretskii [this message]
2015-09-21  7:39   ` Dima Kogan
2015-09-21  7:59     ` Eli Zaretskii
2015-09-21  9:03       ` Dima Kogan
2015-09-21  9:43         ` Eli Zaretskii
2015-09-21 18:24           ` Dima Kogan
2022-01-24 13:56       ` Lars Ingebrigtsen

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=83oagwnthf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21528@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).