unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, 6280@debbugs.gnu.org
Subject: bug#6280: 24.0.50; (elisp) Dedicated Windows
Date: Fri, 28 May 2010 11:19:24 +0200	[thread overview]
Message-ID: <4BFF8A9C.8060700@gmx.at> (raw)
In-Reply-To: <F50316FDFB274093B522BA76C1094C3E@us.oracle.com>

 >> Should users really control the dedicatedness of individual windows?
 >
 > Questions that start "Should users really control" are anti-GNU/Emacs. (Only
 > half-kidding.) Users are not losers.

Emacs is free software.  I don't intend to control each and every aspect
of it.

 > FYI, here is what the OP on help-gnu-emacs said, before his technical request:
 >
 > OP> I swear, if emacs "steals" a window to reuse for
 > OP> something else again, I'm going to swing an axe at it.

I doubt that would help much.

 > IMO, users should be able to make windows dedicated.
 > And they are able to, AFAICT.
 >
 > BTW, why do you specify "individual" windows here? Did you mean something
 > special by that?

ECB dedicates windows to compiler output, system messages, file lists,
tags, bookmarks ...  These are windows grouped around an undedicated
edit area and ECB takes care or assigning buffers to the dedicated
windows.  ECB doesn't support dedicating "individual" windows within the
editor area.

 > The OP wants to dedicate all windows for buffers in a certain
 > mode.

Suppose you are in a help buffer and want to follow a cross reference to
an Elisp source code buffer.  IIRC this usually calls `pop-to-buffer'.
Now should this action allow `display-buffer' to "steal" a window showing
another Elisp buffer?

 > * To dedicate all windows, can't you just
 >   set `special-display-regexps' to include ".*"?
 > * To dedicate all windows for buffers in a mode, can't you just
 >   add ".*" to `special-display-regexps' on the mode hook and
 >   make the var buffer-local?
 >
 > Those both seem to work OK. If you customize `emacs-lisp-mode-hook' to add this
 > function, doesn't it DTRT for you?
 >
 > (lambda ()
 >   (make-local-variable 'special-display-regexps)
 >   (add-to-list 'special-display-regexps ".*"))

I completely fail to understand how `special-display-regexps' would
enter here and how it could be used for the OP's purposes.  Also, making
`special-display-regexps' buffer-local doesn't make sense to me.  At the
time `display-buffer' is called _any_ buffer may be current.

Maybe Stefan can tell us more.  I suppose he's the only one using
(weakly) dedicated windows in some organized way.

martin





  reply	other threads:[~2010-05-28  9:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 15:51 bug#6280: 24.0.50; (elisp) Dedicated Windows Drew Adams
2010-05-27 17:24 ` martin rudalics
2010-05-27 17:51   ` Drew Adams
2010-05-28  9:19     ` martin rudalics [this message]
2010-05-28 14:13       ` Drew Adams
2010-05-28 15:10         ` martin rudalics
2010-05-28 16:16           ` Drew Adams
2010-05-29  8:20             ` martin rudalics
2014-02-10  3:19           ` Lars Ingebrigtsen
2014-02-10  3:32             ` Drew Adams
2014-02-10  8:15               ` martin rudalics
2014-02-10 16:52                 ` Stefan Monnier
2014-02-10 17:02                   ` Drew Adams

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=4BFF8A9C.8060700@gmx.at \
    --to=rudalics@gmx.at \
    --cc=6280@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=monnier@IRO.UMontreal.CA \
    /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).