unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Oleh Krehel <ohwoeowho@gmail.com>
Cc: thibaut.verron@gmail.com, emacs-devel@gnu.org
Subject: Re: Use of dedicated windows in gdb-mi.el
Date: Mon, 09 Feb 2015 20:52:47 +0200	[thread overview]
Message-ID: <83zj8m9atc.fsf@gnu.org> (raw)
In-Reply-To: <8761bb9cq8.fsf@gmail.com>

> From: Oleh Krehel <ohwoeowho@gmail.com>
> Cc: thibaut.verron@gmail.com,  emacs-devel@gnu.org
> Date: Mon, 09 Feb 2015 19:11:27 +0100
> 
> >> > Don't you _want_ to see the output of a program you are debugging?
> >> 
> >> Nope. I can see all that I need through "p". The actual program output
> >> for my particular program is barely relevant during runtime, and completely
> >> irrelevant during debug time.
> >
> > Then perhaps a better solution would be an option not to pop the
> > *output* window at all, so that the need to switch to another buffer
> > in that window is eliminated?  Would you like such a solution better?
> 
> No this won't work. I don't want *output* in this particular program. I
> might want it for others.

If the option not to pop it is a defcustom, you can turn it on when
you want *output* and off when you don't.

> I just want the typical approach of burying a buffer once and then
> having it not surface, even if there's new output.

The option not to pop it in a window will solve this as well, right?

> Just imagine the havoc of *Messages* being a dedicated window and
> popping up each time there's a new message, even if you bury it.

JFYI, there are people who like to configure Emacs like that.  You've
just heard from one of them.  To each their own.

> I dislike non-soft dedicated windows because they're bad design.

Others will disagree.  gdb-many-windows is for them; if you don't like
that, it's very easy not to request those windows.

> I guess that I could just advice `set-window-dedicated-p' to be a
> noop in all cases.

If that's what you prefer.  I still think that an option to pop or not
to pop the *output* window, which is the only one that opens without
your say-so, is a better solution.  It gives you what you want without
affecting unrelated features and other users.

> 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?



  parent reply	other threads:[~2015-02-09 18:52 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 [this message]
2015-02-09 18:53                       ` Oleh Krehel
2015-02-09 18:58                       ` Oleh Krehel
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=83zj8m9atc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ohwoeowho@gmail.com \
    --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).