[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#34749: 26.1; `delete-windows-on': (1) doc, (2) bug, (3) bug, (4) can

From: martin rudalics
Subject: bug#34749: 26.1; `delete-windows-on': (1) doc, (2) bug, (3) bug, (4) candidates
Date: Sun, 10 Mar 2019 09:48:29 +0100

> Those other-* function also need to allow the user to specify a count,
> something that we don't have to do here.  So there's no reason to
> expect consistency here.  (I do think it would be good to allow the
> user to control the last argument of other-window and other-frame as
> well, if that's possible, but the solution doesn't have to be
> identical to what we do with delete-windows-on.)

I sometimes wonder whether we try to invent a raison d'ĂȘtre for the
prefix argument even if there's none.  'other-window' is one example.
How are users able to calculate in advance the window that would
result from a prefix argument larger than say 1 here?  Wouldn't that
depend on the knowledge of how the window list is constructed from the
traversal of the window trees, how it wraps, where in that list the
active minibuffer window is and what the ALL-FRAMES argument is?  As a
matter of fact, I could use 'other-window' only if a frame contains at
most two windows and always use directional movement instead.

Note: This is no suggestion how things should be specified.  It only
serves to explain why I'm not able to come up with a useful proposal


reply via email to

[Prev in Thread] Current Thread [Next in Thread]