From: Juri Linkov <juri@linkov.net>
To: pillule <pillule@riseup.net>
Cc: 48916@debbugs.gnu.org
Subject: bug#48916: 28.0.50; allow windmove to select windows with the 'no-other-window parameter
Date: Tue, 08 Jun 2021 19:46:23 +0300 [thread overview]
Message-ID: <87fsxscpw4.fsf@mail.linkov.net> (raw)
In-Reply-To: <878s3kzm66.fsf@riseup.net> (pillule@riseup.net's message of "Tue, 08 Jun 2021 12:09:21 +0200")
>>> +(defcustom windmove-ignore-no-other-window nil
>>
>> This name is not the best one. For starters, "ignore-no" is a kind of
>> double negation, which makes it harder to understand and remember.
>> Can you come up with a better description of what exactly is ignored
>> here?
> Yes, i think 'windmove-move-in-all-windows' will be more explicit.
Repeating words "...move-move..." doesn't look nice. Maybe a better name
would be 'windmove-allow-all-windows'.
> Because it applies to `windmove-find-other-window', it allows the commands
> windmove-right, windmove-left, windmove-down, windmove-up to select windows
> with the no-other-window parameter, but not for the `windmove-display-*'
> functions. I suppose it is the desired behavior.
You could try using new option in all functions that call window-in-direction:
in windmove-display-in-direction, in windmove-delete-in-direction,
in windmove-swap-states-in-direction.
next prev parent reply other threads:[~2021-06-08 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 10:09 bug#48916: 28.0.50; allow windmove to select windows with the 'no-other-window parameter pillule
2021-06-08 11:44 ` Eli Zaretskii
2021-06-08 13:28 ` pillule
2021-06-08 14:12 ` Eli Zaretskii
2021-06-08 14:48 ` Robert Pluim
2021-06-09 17:37 ` pillule
2021-06-09 20:13 ` Juri Linkov
2021-06-10 8:58 ` pillule
2021-06-08 13:57 ` pillule
2021-06-08 14:13 ` Eli Zaretskii
2021-06-08 14:26 ` pillule
2021-06-08 16:46 ` Juri Linkov [this message]
2021-06-15 19:50 ` pillule
2021-06-15 23:27 ` 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
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=87fsxscpw4.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=48916@debbugs.gnu.org \
--cc=pillule@riseup.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 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).