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: Sat, 29 May 2010 10:20:00 +0200	[thread overview]
Message-ID: <4C00CE30.1020609@gmx.at> (raw)
In-Reply-To: <0C40D97636E64B6D82C3D37C28F54878@us.oracle.com>

 > My value of `special-display-regexps' is ("[ ]?[*][^*]+[*]"), so buffers named
 > `*...*' are special.

In your original report you asked for

 > * a simple recipe for making all windows dedicated and
 >
 > * a simple recipe for making all windows for buffers in a certain mode
 > dedicated

I tried to answer these questions.

 >> I earlier mentioned how you can do what the OP wants.  Write
 >> a function that you _globally_ add to
 >> `window-configuration-change-hook'.  That function would have to
 >> scan `window-list', check for each window whether
 >> its buffer is in a mode that shall have dedicated windows,
 >> and, if that is the case, call `set-window-dedicated-p' for that
 >> window with some non-nil, non-t flag.  If someone can come up
 >> with a simpler solution I'll be all ears.
 >
 > Sigh.

Sorry.

martin





  reply	other threads:[~2010-05-29  8:20 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
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 [this message]
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=4C00CE30.1020609@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).