unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sam Steingold <sds@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 11365@debbugs.gnu.org
Subject: bug#11365: 24.1.50; quitting gdb does not restore window configuration
Date: Sun, 06 May 2012 01:40:09 -0400	[thread overview]
Message-ID: <87y5p57tqe.fsf@gnu.org> (raw)
In-Reply-To: <4FA4F5F0.6030401@gmx.at> (martin rudalics's message of "Sat, 05 May 2012 11:42:08 +0200")

> * martin rudalics <ehqnyvpf@tzk.ng> [2012-05-05 11:42:08 +0200]:
>
> !   (remove-hook 'after-save-hook 'gdb-create-define-alist t)
> !   ;; Quit window of any *gud- buffer.
> !   (when (string-match "\\*gud-" (buffer-name (window-buffer)))
> !     (quit-window)))

quit-window is not a solution, because it often kills the window.
I live in a maximized emacs frame which is split vertically in to two
columns, and an indiscriminate use of quit-window quickly destroys that.

In fact, I would like a feature which would make these two side-by-side
windows indestructible (i.e., prevent them from being destroyed other
than by an explicit interactive C-x 0).  I guess I can set their
delete-window parameters to ignore but then

-1- C-x 0 will NOT delete them while

-2- any application which binds ignore-window-parameters to t will
    delete them.

but I digress...

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X 11.0.11103000
http://www.childpsy.net/ http://americancensorship.org http://memri.org
http://www.PetitionOnline.com/tap12009/ http://thereligionofpeace.com
I'm out of my mind, but feel free to leave a message...





  reply	other threads:[~2012-05-06  5:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 18:40 bug#11365: 24.1.50; quitting gdb does not restore window configuration Sam Steingold
2012-04-27 19:01 ` Eli Zaretskii
2012-04-27 19:34   ` Sam Steingold
2012-04-28  6:51     ` Eli Zaretskii
2012-04-28  8:25 ` martin rudalics
2012-04-30 22:14   ` Sam Steingold
2012-05-01  8:09     ` martin rudalics
2012-05-01 12:25       ` Sam Steingold
2012-05-02  9:39         ` martin rudalics
2012-05-02 14:16           ` Sam Steingold
2012-05-05  9:42             ` martin rudalics
2012-05-06  5:40               ` Sam Steingold [this message]
2012-05-06 10:25                 ` martin rudalics
2020-09-27 12:41         ` Lars Ingebrigtsen
2020-09-27 12:56           ` Eli Zaretskii
2020-09-27 13:00             ` Lars Ingebrigtsen
2020-09-27 13:02               ` Eli Zaretskii
2022-04-25 15:05               ` Lars Ingebrigtsen
2022-05-24 12:51                 ` Lars Ingebrigtsen
2012-05-01 15:54       ` Eli Zaretskii
2012-05-02  9:40         ` martin rudalics
2012-05-02 16:02           ` Eli Zaretskii
2012-05-05  9:42             ` martin rudalics
2012-05-05  9:49               ` Eli Zaretskii
2012-05-05 10:24                 ` martin rudalics

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=87y5p57tqe.fsf@gnu.org \
    --to=sds@gnu.org \
    --cc=11365@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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).