From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFC-version3] Fix completion bug for directories
Date: Wed, 25 Mar 2009 00:50:00 -0000 [thread overview]
Message-ID: <m3y6uu1m0u.fsf@fleche.redhat.com> (raw)
In-Reply-To: <000001c9a234$9e4486e0$dacd94a0$@u-strasbg.fr> (Pierre Muller's message of "Wed\, 11 Mar 2009 11\:32\:03 +0100")
>>>>> "Pierre" == Pierre Muller <muller@ics.u-strasbg.fr> writes:
Pierre> This is a new patch to fix the problem with completion on
Pierre> directories.
Oh, nice. This has bothered me a bit. I even dug into it once, but
it looked like a pain.
Thanks for posting URLs of the previous revisions of this patch. That
helps a lot.
One question I have is whether this works with the "complete" command.
(I suspect it does not.) When I looked into this I sort of concluded
that we would be better off not messing with readline's notions of
word breaks, and furthermore that we'd be better off just adding
filename completion directly to gdb. But, that was a lot more work
than I wanted to do...
I'd really like it to work with "complete", since that is what Emacs
uses :-). But I suppose it is not really a requirement for the patch
-- it remains an improvement even if it is not "perfect".
Pierre> I do get some random success/failure differences
Pierre> in
Pierre> gdb.threads/schedlock.exp
Pierre> or
Pierre> gdb.threads/attach-into-signal.exp
Pierre> but I understood from other emails that these are
Pierre> non-deterministic tests that do fail/succeed more or less
Pierre> randomly.
Yes, that's correct.
Pierre> Apparently, there are no listings of the header
Pierre> dependencies in Makefile.in anymore, I suppose that
Pierre> these are now generated automatically somehow now, is this right?
Yes, dependency tracking is now automatic.
Pierre> I didn't find anything in the generated Makefile,
Pierre> how does that work?
The dependencies themselves are stored in a .deps subdir.
You need GNU make for this feature to be enabled.
I can provide a fuller explanation if you want...
A few nits on the patch:
+ if REASON is handle_brkchars:
Capitalize: "If". There's a few of these.
+ depending gon the current command in line_buffer.
Typo: s/gon/on/
When FOR_HELP is false, we will call a sub-command's completion
- function. */
+ function.
It seems to me that this entire sentence ought to be deleted.
This patch is ok with those changes. Thanks!
Tom
next prev parent reply other threads:[~2009-03-25 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 15:25 Pierre Muller
2009-03-25 0:50 ` Tom Tromey [this message]
2009-03-25 13:43 ` Pierre Muller
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=m3y6uu1m0u.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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