From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>, 34749@debbugs.gnu.org
Subject: bug#34749: 26.1; `delete-windows-on': (1) doc, (2) bug, (3) bug, (4) candidates
Date: Tue, 05 Mar 2019 11:12:59 +0100 [thread overview]
Message-ID: <5C7E4BAB.3050508@gmx.at> (raw)
In-Reply-To: <b375da42-2b65-4579-902c-85e9fdcaeac7@default>
> It seems like the interactive behavior is not correct, as well as being
> poorly documented. It's hard to know just what behavior was intended,
> or what behavior would be best if (as it seems) we still need to design
> this.
If anyone has any ideas, we should implement that. Suggestions highly
welcome.
> 3. Why is `B' used in the interactive spec instead of `b'? What's the
> use case for deleting windows showing a nonexistent buffer?
I hopefully fixed that now on master.
> 4. The buffer candidates available for completion (which should also be
> the only buffer names available for entry - see #3) should depend on
> which frames are used, i.e., on the prefix arg or its absence.
>
> You should be presented only with the names of buffers that are actually
> shown in windows on the frames that you've chosen to consider for
> window-deletion.
Good idea.
martin
next prev parent reply other threads:[~2019-03-05 10:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 16:25 bug#34749: 26.1; `delete-windows-on': (1) doc, (2) bug, (3) bug, (4) candidates Drew Adams
2019-03-05 10:12 ` martin rudalics [this message]
2019-03-08 10:29 ` Eli Zaretskii
2019-03-08 11:02 ` martin rudalics
2019-03-08 13:15 ` Eli Zaretskii
2019-03-08 18:52 ` martin rudalics
2019-03-08 19:45 ` Drew Adams
2019-03-09 8:39 ` martin rudalics
2019-03-09 16:37 ` Drew Adams
2019-03-08 19:58 ` Eli Zaretskii
2019-03-09 8:39 ` martin rudalics
2019-03-09 10:58 ` Eli Zaretskii
2019-03-09 13:16 ` martin rudalics
2019-03-09 16:33 ` Drew Adams
2019-03-09 16:46 ` Eli Zaretskii
2019-03-10 8:46 ` martin rudalics
2019-03-10 8:48 ` martin rudalics
2019-03-08 10:27 ` Eli Zaretskii
2022-04-26 12:32 ` Lars Ingebrigtsen
[not found] <<b375da42-2b65-4579-902c-85e9fdcaeac7@default>
[not found] ` <<83o96lacf8.fsf@gnu.org>
2019-03-08 16:34 ` Drew Adams
2019-03-08 17:00 ` Eli Zaretskii
[not found] ` <<5C7E4BAB.3050508@gmx.at>
[not found] ` <<83mum5accd.fsf@gnu.org>
[not found] ` <<5C824BAC.4090907@gmx.at>
[not found] ` <<83lg1pa4oa.fsf@gnu.org>
[not found] ` <<5C82B9E1.1080302@gmx.at>
[not found] ` <<83zhq587g6.fsf@gnu.org>
[not found] ` <<5C837BD6.9010200@gmx.at>
[not found] ` <<83ef7g8gbc.fsf@gnu.org>
[not found] ` <<5C83BC9B.5020803@gmx.at>
[not found] ` <<e0b90f9b-2d1f-4877-b83a-aeca5425dbea@default>
[not found] ` <<8336nw807g.fsf@gnu.org>
2019-03-09 17:35 ` Drew Adams
2019-03-09 18:12 ` Eli Zaretskii
[not found] <<<b375da42-2b65-4579-902c-85e9fdcaeac7@default>
[not found] ` <<<83o96lacf8.fsf@gnu.org>
[not found] ` <<6aae54ec-85bf-4447-bec0-7c916caeb2f8@default>
[not found] ` <<83a7i59u85.fsf@gnu.org>
2019-03-08 17:14 ` Drew Adams
2019-03-08 18:58 ` Eli Zaretskii
[not found] ` <<<5C7E4BAB.3050508@gmx.at>
[not found] ` <<<83mum5accd.fsf@gnu.org>
[not found] ` <<<5C824BAC.4090907@gmx.at>
[not found] ` <<<83lg1pa4oa.fsf@gnu.org>
[not found] ` <<<5C82B9E1.1080302@gmx.at>
[not found] ` <<<83zhq587g6.fsf@gnu.org>
[not found] ` <<<5C837BD6.9010200@gmx.at>
[not found] ` <<<83ef7g8gbc.fsf@gnu.org>
[not found] ` <<<5C83BC9B.5020803@gmx.at>
[not found] ` <<<e0b90f9b-2d1f-4877-b83a-aeca5425dbea@default>
[not found] ` <<<8336nw807g.fsf@gnu.org>
[not found] ` <<dd8e2b24-ab4a-4a4c-b9b8-9249f9ec035b@default>
[not found] ` <<83sgvv7w99.fsf@gnu.org>
2019-03-09 22:32 ` Drew Adams
[not found] <<<<b375da42-2b65-4579-902c-85e9fdcaeac7@default>
[not found] ` <<<<83o96lacf8.fsf@gnu.org>
[not found] ` <<<6aae54ec-85bf-4447-bec0-7c916caeb2f8@default>
[not found] ` <<<83a7i59u85.fsf@gnu.org>
[not found] ` <<a1314708-0feb-4092-8b60-37d7282a328f@default>
[not found] ` <<834l8d9orm.fsf@gnu.org>
2019-03-08 19:48 ` Drew Adams
2019-03-08 20:14 ` Eli Zaretskii
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=5C7E4BAB.3050508@gmx.at \
--to=rudalics@gmx.at \
--cc=34749@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).