From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Nevermind (was Re: find-files prompt discrepancy)
Date: Thu, 21 Mar 2019 13:15:45 -0700 [thread overview]
Message-ID: <87d0mkq8zy.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m1bm246lot.fsf@nwalsh.com>
Norman Walsh <ndw@nwalsh.com> writes:
>> Can anyone explain the discrepancy? (I usually run M-x gnus in the
>> *scratch* buffer, as it happens, though I doubt that’s relevant.)
>
> Lived with this behavior for ages, asked a question about it, five
> minutes later noticed for the first that the behavior is *in fact*
> dependent on where the cursor is in the *Groups* buffer. So this is
> definitely helm-find-files trying to be clever in some way.
And my default-directory question was a red herring...
next prev parent reply other threads:[~2019-03-21 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 19:45 find-files prompt discrepancy Norman Walsh
2019-03-21 20:01 ` Nevermind (was Re: find-files prompt discrepancy) Norman Walsh
2019-03-21 20:15 ` Eric Abrahamsen [this message]
2019-03-21 20:12 ` find-files prompt discrepancy Eric Abrahamsen
2019-03-22 12:09 ` Jeffrey DeLeo
2019-03-22 16:22 ` Andreas Schwab
2019-03-21 20:19 ` Andreas Schwab
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=87d0mkq8zy.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).