* `delete-windows-on' completion list should include only buffers that correspond to FRAME arg
@ 2006-08-26 15:29 Drew Adams
2006-08-27 14:34 ` Richard Stallman
0 siblings, 1 reply; 4+ messages in thread
From: Drew Adams @ 2006-08-26 15:29 UTC (permalink / raw)
The completion list of command `delete-windows-on' is all buffers -
`interactive' is simply called with "bDelete windows on (buffer): ". Most of
the time, however, many of those buffers have no windows to delete.
It would be better to have `interactive' check the FRAME arg, and propose a
list of buffer candidates for completion that is compatible (consistent)
with FRAME.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: `delete-windows-on' completion list should include only buffers that correspond to FRAME arg
2006-08-26 15:29 `delete-windows-on' completion list should include only buffers that correspond to FRAME arg Drew Adams
@ 2006-08-27 14:34 ` Richard Stallman
2006-08-27 15:27 ` `delete-windows-on' completion list should include only buffersthat " Drew Adams
0 siblings, 1 reply; 4+ messages in thread
From: Richard Stallman @ 2006-08-27 14:34 UTC (permalink / raw)
Cc: emacs-devel
The completion list of command `delete-windows-on' is all buffers -
`interactive' is simply called with "bDelete windows on (buffer): ". Most of
the time, however, many of those buffers have no windows to delete.
It would be better to have `interactive' check the FRAME arg, and propose a
list of buffer candidates for completion that is compatible (consistent)
with FRAME.
I think it is better to leave this alone. It could be confusing for
completion to fail to recognize a buffer name.
^ permalink raw reply [flat|nested] 4+ messages in thread* RE: `delete-windows-on' completion list should include only buffersthat correspond to FRAME arg
2006-08-27 14:34 ` Richard Stallman
@ 2006-08-27 15:27 ` Drew Adams
2006-08-28 22:09 ` Richard Stallman
0 siblings, 1 reply; 4+ messages in thread
From: Drew Adams @ 2006-08-27 15:27 UTC (permalink / raw)
The completion list of command `delete-windows-on' is all buffers -
`interactive' is simply called with "bDelete windows on
(buffer): ". Most of
the time, however, many of those buffers have no windows to delete.
It would be better to have `interactive' check the FRAME
arg, and propose a list of buffer candidates for completion
that is compatible (consistent) with FRAME.
I think it is better to leave this alone. It could be confusing for
completion to fail to recognize a buffer name.
Could you explain a little more what you mean? I use this in my own code,
with no problem. What do you mean by completion failing to recognize a
buffer name?
All I'm suggesting is to reduce the number of candidate buffer names, not
augment it, by filtering them to make sure that each candidate is in fact
displayed in a window.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-08-28 22:09 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-26 15:29 `delete-windows-on' completion list should include only buffers that correspond to FRAME arg Drew Adams
2006-08-27 14:34 ` Richard Stallman
2006-08-27 15:27 ` `delete-windows-on' completion list should include only buffersthat " Drew Adams
2006-08-28 22:09 ` Richard Stallman
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).