From: Eli Zaretskii <eliz@gnu.org>
To: Ergus <spacibba@aol.com>
Cc: 61613@debbugs.gnu.org
Subject: bug#61613: 30.0.50; ffap-other-window ignores ffap-require-prefix
Date: Mon, 20 Feb 2023 14:50:18 +0200 [thread overview]
Message-ID: <83r0ukv6ut.fsf@gnu.org> (raw)
In-Reply-To: <20230219213255.rhyiu44udzpgqsq2@Ergus> (message from Ergus on Sun, 19 Feb 2023 22:32:55 +0100)
> Date: Sun, 19 Feb 2023 22:32:55 +0100
> From: Ergus <spacibba@aol.com>
> Cc: 61613@debbugs.gnu.org
>
> On Sun, Feb 19, 2023 at 12:15:49PM +0200, Eli Zaretskii wrote:
> >> Date: Sun, 19 Feb 2023 11:09:04 +0100
> >> From: Ergus <spacibba@aol.com>
> >> CC: 61613@debbugs.gnu.org
> >>
> >> emacs -Q
> >> M-x ffap-bindings
> >> M-: (setq ffap-require-prefix t)
> >> Write /somedir
> >>
> >> C-x C-f (you see: ~/)
> >>
> >> But
> >>
> >> C-x 4 f (you see /somedir)
> >>
> >> This seems to be related with the ffap-prompter called before the switch then?
> >
> >Yes, I think so.
>
> Hi Eli:
>
> So, what do you think? The fix may be to put the ffap-require-prefix
> condition in ffap-read-file-or-url directly or in ffap-prompter??
I don't understand what you want to achieve by that, so please
elaborate. ffap-file-finder's default value is a command that doesn't
display the file in another window, so how will ffap-require-prefix
help here?
next prev parent reply other threads:[~2023-02-20 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pma6tlth.fsf.ref@aol.com>
2023-02-19 2:45 ` bug#61613: 30.0.50; ffap-other-window ignores ffap-require-prefix Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19 9:21 ` Eli Zaretskii
2023-02-19 10:09 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19 10:15 ` Eli Zaretskii
2023-02-19 21:32 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-20 12:50 ` Eli Zaretskii [this message]
2023-02-20 15:49 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-20 17:01 ` Eli Zaretskii
2023-02-19 21:43 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-20 12:51 ` Eli Zaretskii
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=83r0ukv6ut.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61613@debbugs.gnu.org \
--cc=spacibba@aol.com \
/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).