unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: David Hansen <david.hansen@gmx.net>, emacs-devel@gnu.org
Subject: Re: gdb-ui, dedicated windows
Date: Wed, 09 Jul 2008 08:46:18 +0900	[thread overview]
Message-ID: <871w24ndmd.fsf@catnip.gol.com> (raw)
In-Reply-To: <18547.64152.956371.924404@kahikatea.snap.net.nz> (Nick Roberts's message of "Wed, 9 Jul 2008 11:39:04 +1200")

Nick Roberts <nickrob@snap.net.nz> writes:
>  >   (4) Switch back to the *gud...* buffer using "C-x b *gud...* RET"
>  > 
>  >   (5) Try to pop up the source buffer again using a gdb command, e.g.,
>  >       just "frame RET".
>  > 
>  > *bang*, *gdb...* buffer disappears, source buffer is only ting
>  > displayed... :-(
>
> OK.  When you do (4) you put the GUD buffer in the window that
> gdb-source-window points to.  So when you do 'f' gdb-ui thinks the source
> should go there.
>
> I'm not sure what I can do as commands like switch-to-buffer are built-in.
> Maybe some kind of hook in window-size-change-functions to keep gdb-ui
> up-to-date.  Or perhaps having window groups would make it impossible to switch
> the source buffer for the GUD buffer if they were assigned to different groups.

gud/gdb-ui shouldn't be storing window references like that and assuming
the associated buffer hasn't been changed by the user, because that's an
assumption that doesn't hold in emacs.

Perhaps that code is left over from the "old" gdb-ui which used
dedicated windows?

A possible fix would be to store the buffer gdb puts in that window,
and when deciding whether to re-use that window or, also verify that the
same buffer is there (and don't re-use the window if not).

-Miles

-- 
Acquaintance, n. A person whom we know well enough to borrow from, but not
well enough to lend to.




  reply	other threads:[~2008-07-08 23:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-05  7:58 gdb-ui, dedicated windows David Hansen
2008-07-05 10:02 ` Nick Roberts
2008-07-05 10:52   ` David Hansen
2008-07-07  4:38     ` Nick Roberts
2008-07-08  7:06       ` Miles Bader
2008-07-08  7:18         ` Miles Bader
2008-07-08 23:39           ` Nick Roberts
2008-07-08 23:46             ` Miles Bader [this message]
2008-07-09 10:47               ` Nick Roberts
2008-07-15 13:37                 ` Miles Bader
2008-07-15 21:50                   ` Nick Roberts
2008-07-15 23:43                     ` Miles Bader
2008-07-05 14:04   ` Miles Bader
2008-07-05 16:11   ` Tom Tromey
2008-07-07  5:20     ` Nick Roberts
2008-07-07 14:40       ` Tom Tromey
2008-07-07 16:14         ` tomas
2008-07-07 19:33         ` David Hansen
2008-07-07 19:47           ` Lennart Borgman (gmail)
2008-07-07 20:01           ` Tom Tromey
2008-07-07 20:09             ` Lennart Borgman (gmail)
2008-07-07 23:11           ` Stephen J. Turnbull
2008-07-07 23:03             ` Lennart Borgman (gmail)
2008-07-08 16:02         ` James Cloos

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=871w24ndmd.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=david.hansen@gmx.net \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@snap.net.nz \
    /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).