From: Oleh Krehel <ohwoeowho@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: thibaut.verron@gmail.com, emacs-devel@gnu.org
Subject: Re: Use of dedicated windows in gdb-mi.el
Date: Mon, 09 Feb 2015 19:58:19 +0100 [thread overview]
Message-ID: <87pp9ioqt0.fsf@gmail.com> (raw)
In-Reply-To: <83zj8m9atc.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 09 Feb 2015 20:52:47 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> If you have 9 minutes and a way to view Youtube videos, you can see my
>> demo of a neat approach to manipulating windows (especially the window
>> swap). This approach of course won't work with non-soft dedicated
>> windows: https://www.youtube.com/watch?v=_qZliI1BKzI.
>
> That's cute, but is this related to GDB-MI and the issue being
> discussed here? If so, how?
There's a function that swaps the current window with the selected one.
It fails miserably with dedicated windows, although works with
soft-dedicated.
The point is that the user may know better how to manipulate the window
layout. Random dedicated windows that behave differently from normal windows,
without a visual indication that they are different, aren't a good design.
next prev parent reply other threads:[~2015-02-09 18:58 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 18:02 Use of dedicated windows in gdb-mi.el Oleh Krehel
2015-02-06 19:07 ` Eli Zaretskii
2015-02-06 19:14 ` Oleh Krehel
2015-02-06 21:33 ` Eli Zaretskii
2015-02-09 9:19 ` Thibaut Verron
2015-02-09 14:29 ` Stefan Monnier
2015-02-09 14:50 ` Oleh Krehel
2015-02-09 15:51 ` Eli Zaretskii
2015-02-09 18:42 ` martin rudalics
2015-02-09 15:44 ` Eli Zaretskii
2015-02-09 15:57 ` Oleh Krehel
2015-02-09 17:05 ` Eli Zaretskii
2015-02-09 17:22 ` Oleh Krehel
2015-02-09 17:56 ` Eli Zaretskii
2015-02-09 18:11 ` Oleh Krehel
2015-02-09 18:26 ` Drew Adams
2015-02-09 18:39 ` Oleh Krehel
2015-02-09 18:56 ` Eli Zaretskii
2015-02-09 19:48 ` Oleh Krehel
2015-02-09 20:00 ` Eli Zaretskii
2015-02-09 19:44 ` Drew Adams
2015-02-09 19:50 ` Oleh Krehel
2015-02-09 20:01 ` Eli Zaretskii
2015-02-09 20:09 ` Oleh Krehel
2015-02-09 20:27 ` Eli Zaretskii
2015-02-09 20:33 ` Oleh Krehel
2015-02-09 20:44 ` Eli Zaretskii
2015-02-09 20:46 ` Oleh Krehel
2015-02-10 15:42 ` Eli Zaretskii
2015-02-10 2:20 ` Stefan Monnier
2015-02-10 3:48 ` Eli Zaretskii
2015-02-10 6:39 ` Oleh Krehel
2015-02-10 15:54 ` Eli Zaretskii
2015-02-09 18:52 ` Eli Zaretskii
2015-02-09 18:53 ` Oleh Krehel
2015-02-09 18:58 ` Oleh Krehel [this message]
2015-02-09 19:20 ` Eli Zaretskii
2015-02-09 19:47 ` Oleh Krehel
[not found] ` <<8761bb9cq8.fsf@gmail.com>
[not found] ` <<83zj8m9atc.fsf@gnu.org>
2015-02-09 20:42 ` Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2015-02-24 17:56 Glenn Brown
2015-02-24 18:02 ` Oleh Krehel
2015-02-24 18:31 ` Eli Zaretskii
2015-02-24 22:23 ` Paul Eggert
2015-02-25 3:46 ` Eli Zaretskii
2015-02-25 3:57 ` Stefan Monnier
2015-02-25 6:09 ` Glenn Brown
2015-02-10 0:49 Barry OReilly
2015-02-10 16:05 ` Eli Zaretskii
[not found] <<87h9uynckc.fsf@gmail.com>
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=87pp9ioqt0.fsf@gmail.com \
--to=ohwoeowho@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=thibaut.verron@gmail.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).