GNU bug report logs - #61613
30.0.50; ffap-other-window ignores ffap-require-prefix

Previous Next

Package: emacs;

Reported by: Ergus <spacibba <at> aol.com>

Date: Sun, 19 Feb 2023 02:46:01 UTC

Severity: normal

Found in version 30.0.50

Full log


Message #8 received at 61613 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ergus <spacibba <at> aol.com>
Cc: 61613 <at> debbugs.gnu.org
Subject: Re: bug#61613: 30.0.50; ffap-other-window ignores ffap-require-prefix
Date: Sun, 19 Feb 2023 11:21:02 +0200
> Date: Sun, 19 Feb 2023 03:45:30 +0100
> From:  Ergus via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
> 
> I just found that ffap-other-window ignores when ffap-require-prefix is
> non-nil.
> 
> Looking at the code it seems to be that find-file-at-point has:
> 
> (and (called-interactively-p 'interactive)
>      (if ffap-require-prefix (not current-prefix-arg)
> 	 current-prefix-arg))
> 
> but ffap-other-window calls find-file-at-point no interactively. Same
> for ffap-other-frame, ffap-other-tab and so on...

What would be the point of supporting ffap-require-prefix when you
call ffap-other-window?  That variable controls whether to invoke
ffap-file-finder, which is not suitable for -other-window commands, I
think?  That is why, AFAIU, when not called interactively,
find-file-at-point doesn't call ffap-file-finder at all, and therefore
there's no point in heeding ffap-require-prefix.  Right?




This bug report was last modified 2 years and 116 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.