From: Pengji Zhang <kunhtkun@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 65558@debbugs.gnu.org
Subject: bug#65558: 30.0.50; project-other-{window,frame,tab}-command a bit too obtrusive
Date: Tue, 29 Aug 2023 23:58:18 -0400 [thread overview]
Message-ID: <CANOCUiyiSfTaf5JmOfYrGO8JZZ8a1EcHzpn+oCSGH=x6PTf-9w@mail.gmail.com> (raw)
In-Reply-To: <86ttskikm2.fsf@mail.linkov.net>
Thanks for the pointer! That is a long thread so I only skimmed it. I
think you meant this snippet in [0]:
> (defun project-other-window-command ()
> (interactive)
> (other-window-prefix)
> (set-transient-map (make-composed-keymap project-prefix-map
> project-other-window-map)))
That indeed fixes the issue. My only concern is that
`other-window-prefix' is a new function introduced in Emacs 28.
[0] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63648#95
On Sun, Aug 27, 2023 at 12:21 PM Juri Linkov <juri@linkov.net> wrote:
>
> > Currently the function `project--other-place-command' uses
> > `display-buffer-overriding-action' which IMO makes
> > project-other-{window,frame,tab}-command a bit too obtrusive. For
> > example,
> >
> > 1. Start Emacs with 'emacs -Q';
> > 2. Press 'C-x 5 p f';
> > 3. Press 'TAB'.
> >
> > Then the '*Completions*' buffer pops up in a new frame. The expected
> > behavior of mine is that the '*Completions*' buffer shows at the
> > bottom of the current frame, which is the same as most of other 'C-x
> > 5' commands.
>
> Thanks for the request. I believe this will be fixed in bug#63648.
next prev parent reply other threads:[~2023-08-30 3:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 19:25 bug#65558: 30.0.50; project-other-{window,frame,tab}-command a bit too obtrusive Pengji Zhang
2023-08-27 16:13 ` Juri Linkov
2023-08-30 3:58 ` Pengji Zhang [this message]
2023-08-30 16:50 ` Juri Linkov
2023-10-19 12:40 ` Dmitry Gutov
2023-10-19 17:49 ` Juri Linkov
2023-10-19 18:31 ` Dmitry Gutov
2023-10-19 18:51 ` Juri Linkov
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='CANOCUiyiSfTaf5JmOfYrGO8JZZ8a1EcHzpn+oCSGH=x6PTf-9w@mail.gmail.com' \
--to=kunhtkun@gmail.com \
--cc=65558@debbugs.gnu.org \
--cc=juri@linkov.net \
/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.