unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: nick@nick.uklinux.net, emacs-devel@gnu.org
Subject: Re: Emacs mode for GDB - 2 questions
Date: Sat, 1 Jun 2002 20:51:42 -0600 (MDT)	[thread overview]
Message-ID: <200206020251.g522pga17894@aztec.santafe.edu> (raw)
In-Reply-To: <5xu1onrh5j.fsf@kfs2.cua.dk> (storm@cua.dk)

    Such modeline-less windows may be useful for other purposes, so
    we should try adding them to see what use people can find for them.

I believe we already support windows without mode-lines.

    > We would need to decide on the UI for selection of these special
    > windows.

    For the UI, just set mode-line-format to nil to remove the modeline.

That is already the way to remove the modeline.
I'm talking about a different issue: how to handle these windows
for window selection, change of window size, etc.
If we don't get that right, the feature will be inconvenient for users.

    A related issue:  I've always thought it would be nice if emacs had some
    way of `binding' windows together, so that, they could be treated as a
    unit in some respects (i.e., other windows couldn't pop up between them,
    and perhaps switching buffers using C-x C-b would switch the _whole_
    group of bound windows instead of just the current leaf window).

This is another thing we need to work out in order for this
mode-line-less-window approach to work well.

    My vague thought was that since windows area already arranged in a tree,
    that somehow non-leaf windows could be marked as the `root' of a set of
    bound windows, and certain operations (switch-to-buffer?) would walk up
    the tree and use such `bound roots' instead of the leaf window if it
    found one.

Would you like to try to flesh out this design?  Rather than jumping
straight to the writing of code, try to write pseudo-code to make the
meaning of these intermediate roots more clear.  That way we can see
if it really is a usable solution.

  parent reply	other threads:[~2002-06-02  2:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29 14:19 Emacs mode for GDB - 2 questions Nick Roberts
2002-05-30 17:05 ` Richard Stallman
2002-05-30 20:58   ` Nick Roberts
2002-05-31 21:27     ` Richard Stallman
2002-05-30 17:05 ` Richard Stallman
2002-05-30 17:33   ` Miles Bader
2002-05-30 20:56     ` Nick Roberts
2002-05-30 17:05 ` Richard Stallman
2002-05-30 21:16   ` Nick Roberts
2002-05-30 23:16     ` Kim F. Storm
2002-05-31  6:38       ` Eli Zaretskii
2002-06-01 20:44         ` Nick Roberts
2002-05-31 21:27     ` Richard Stallman
2002-05-31 23:21       ` Miles Bader
2002-06-01  0:12       ` Kim F. Storm
2002-05-31 23:43         ` Miles Bader
2002-06-01 19:44           ` Alex Schroeder
2002-06-02  2:52             ` Richard Stallman
2002-06-02  2:51         ` Richard Stallman [this message]
2002-06-13 21:38           ` Stefan Monnier
2002-06-03  8:57       ` Juanma Barranquero

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=200206020251.g522pga17894@aztec.santafe.edu \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=nick@nick.uklinux.net \
    /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).