From: Ergus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61613@debbugs.gnu.org
Subject: bug#61613: 30.0.50; ffap-other-window ignores ffap-require-prefix
Date: Sun, 19 Feb 2023 22:43:26 +0100 [thread overview]
Message-ID: <20230219214326.ueue6mpb5krefjdx@Ergus> (raw)
In-Reply-To: <833572x8oa.fsf@gnu.org>
BTW:
Looking at the ffap code I think some minor update/cleanup will be
beneficial any-way.
Nothing very drastic, for example, isn't more consistent to make
ffap-bindings a minor mode to allow load and unload? Or use the
"interactive" in find-file-at-point to simplify the initial conditions
there and remove the optional? Or update the global-set-key to use the
new keymap-set thing? Or add autoload decorators to the interactive
functions?
WDYT?
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.
next prev parent reply other threads:[~2023-02-19 21:43 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230219214326.ueue6mpb5krefjdx@Ergus \
--to=bug-gnu-emacs@gnu.org \
--cc=61613@debbugs.gnu.org \
--cc=eliz@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 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.