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:51:39 +0200 [thread overview]
Message-ID: <83pma4v6sk.fsf@gnu.org> (raw)
In-Reply-To: <20230219214326.ueue6mpb5krefjdx@Ergus> (message from Ergus on Sun, 19 Feb 2023 22:43:26 +0100)
> Date: Sun, 19 Feb 2023 22:43:26 +0100
> From: Ergus <spacibba@aol.com>
> Cc: 61613@debbugs.gnu.org
>
> 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?
It's hard to say without seeing the code you have in mind. Please
post a patch, and let's take it from there.
prev parent reply other threads:[~2023-02-20 12:51 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
2023-02-20 12:51 ` Eli Zaretskii [this message]
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=83pma4v6sk.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).