From: "FRC" <francois.de-campagnolle--NoSpAm--@wanadoo.fr>
Subject: Re: dedicated frames - not quite special-display
Date: Wed, 18 Sep 2002 20:06:49 +0200 [thread overview]
Message-ID: <amaf3d$k2f$1@wanadoo.fr> (raw)
In-Reply-To: m3d6rbcpni.fsf@localhost.localdomain
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
I like the idea too.
Windows that could not be modified would be nice too eg. to keep a one
fourth screen dedicated to eshell, which could not be buried/resized except
by some special cmd.
Maybe this one already exists ?
"Michael Slass" <miknrene@drizzle.com> a écrit dans le message de news:
m3d6rbcpni.fsf@localhost.localdomain...
> "Joe Casadonte" <jcasadonte@northbound-train.com> writes:
>
> >I'm looking for something like the special-display function, but with
> >a twist. I would like to dedicate a frame to a *list* of buffers
> >(preferably defined with a regexp), such that the frame can only
> >display those buffers. An example would be a gnus-only frame, where
> >it could display all gnus buffers within it (and bbdb and ispell), but
> >not be able to switch to a java file.
> >
> >Does such a creature exist? Thanks!
> >
>
> What a great idea! I wonder if you could develop a framework based on
> advising switch-to-buffer? Before jumping in to this, I'd wait to see
> if the gurus know of an easier way.
>
> --
> Mike Slass
next prev parent reply other threads:[~2002-09-18 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 14:25 dedicated frames - not quite special-display Joe Casadonte
2002-09-18 14:56 ` Michael Slass
2002-09-18 15:16 ` Joe Casadonte
2002-09-18 15:57 ` Stefan Monnier <foo@acm.com>
2002-09-18 18:54 ` Kevin Rodgers
2002-09-18 18:06 ` FRC [this message]
2002-09-18 18:46 ` Matthias Meulien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='amaf3d$k2f$1@wanadoo.fr' \
--to=francois.de-campagnolle--nospam--@wanadoo.fr \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.