unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Leo <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: New features in windowing
Date: Tue, 20 Mar 2012 20:11:24 +0100	[thread overview]
Message-ID: <4F68D65C.5020309@gmx.at> (raw)
In-Reply-To: <m1limvilgv.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2048 bytes --]

 >>> I am playing with the new features in windows (as in emacs). I found
 >>> some window-parameters aren't documented such as window-side and
 >>> window-atom.
 >> Hopefully they will make it into Emacs 24.2.
 >
 > Do you mean those features are yet to be implemented? BTW, they were
 > mentioned in the elisp info file.

The features that have to be re-implemented are the routines to set up
the windows.  Currently, you have to do that manually which works for
cases like the one you describe but I want to handle multiple side
windows on each frame.

 > Let me use this for illustration:
 >           ______________________________________
 >          | ______  ____________________________ |
 >          ||      || __________________________ ||
 >          ||      |||                          |||
 >          ||      |||                          |||
 >          ||      |||                          |||
 >          ||      |||____________W4____________|||
 >          ||      || __________________________ ||
 >          ||      |||                          |||
 >          ||      |||                          |||
 >          ||      |||____________W5____________|||
 >          ||__W2__||_____________W3_____________ |
 >          |__________________W1__________________|
 >
 >
 > If I put speedbar buffer in W2, I want those window operations to think
 > as if W3 is the ``frame root window''. So for example, C-x 1 should not
 > delete W2. C-x 0 should never have W2 occupy the whole frame.
 >
 > Is this currently possible?

That's precisely what "making W2 a left side window" would stand for.

 > Unfortunately that would mean difficulty to try it out but I guess I can
 > wait until 24.1 is released.

I attach a simple file you can load from your .emacs.  You then should
be able to create W2 via something like

(display-buffer
  "SPEEDBAR"
  '(display-buffer-in-side-window (side . left) (slot . 0)))

and tell me how it works.  The sooner I get your feedback the sooner I
will be able to adapt the concept appropriately.

martin

[-- Attachment #2: display-buffer.el --]
[-- Type: application/emacs-lisp, Size: 41720 bytes --]

  reply	other threads:[~2012-03-20 19:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20  5:06 New features in windowing Leo
2012-03-20  7:56 ` martin rudalics
2012-03-20 11:02   ` Leo
2012-03-20 19:11     ` martin rudalics [this message]
2012-03-21  0:06       ` Leo
2012-03-21  0:16         ` Glenn Morris
2012-03-20 12:37   ` Stefan Monnier
2012-03-20 19:11     ` 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=4F68D65C.5020309@gmx.at \
    --to=rudalics@gmx.at \
    --cc=emacs-devel@gnu.org \
    --cc=sdl.web@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).