unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: one file per frame  -- customization possible?
Date: Tue, 04 Nov 2003 15:47:20 GMT	[thread overview]
Message-ID: <jwvbrrsf8lx.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca> (raw)
In-Reply-To: BBCD47D9.1927C%r8@davids-welt.de

>> One way is to set the value of special-display-regexps to a regexp
>> that matches any buffer name.

> Unfortunately, this just pertains to buffers that are normally opened in an
> emacs window, but not the ones that are simply shown in the current frame.
> Buffers with standard files are absolutely not affected by
> special-display-regexps; that's what the manual says and that's what I found
> out when I tried it!

It's not even that simple.  It depends on the command you use to get to
that buffer.  Basically, most Emacs commands don't just mean "show me this
file/buffer", but they mean something more specific like "show me this
file/buffer in the current window".  So the best thing to do is to get used
to using C-x 5 f instead of C-x C-f, C-x 5 b instead of C-x b, etc...

As mentioned, you'll want to set special-display-regexps to a very liberal
regexp (something like "\\`\\*.*\\*\\'" or even just ".*").  Also you'll
want to set pop-up-windows and pop-up-frames and most importantly,
you'll need to be ready to report bugs, because a fair bit of code
breaks (it's improved since Emacs-20.1, among other things because I use
such a setup and have reported/fixed a number of bugs).

I've added recently (I think it's only in Emacs-CVS) code so you can put
(same-frame . t) in the special-display-regexps and
special-display-buffer-names parameters so as to override the default
for those few buffers that you want to keep in split windows.

After you tried the above, feel free to ask questions about specific
problems and circumstances.  I've switched to such a setup (together with
a separate minibuffer-only frame) a long time ago and can't remember which
part(s) of my .emacs is relevant so I might have missed some parts.


        Stefan

  reply	other threads:[~2003-11-04 15:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 21:36 one file per frame -- customization possible? David Reitter
2003-11-04  6:03 ` Eli Zaretskii
     [not found] ` <mailman.3087.1067925712.21628.help-gnu-emacs@gnu.org>
2003-11-04 12:11   ` David Reitter
2003-11-04 15:47     ` Stefan Monnier [this message]
2003-12-04 19:58 ` Kai Grossjohann
2003-12-04 23:38   ` Stefan Monnier
2003-12-05  0:26     ` Galen Boyer
2003-12-05 16:50       ` Kai Grossjohann
2003-12-08  1:52         ` Stefan Monnier
2003-12-05 16:46     ` Kai Grossjohann
2003-12-05  8:25 ` Thomas F. Burdick

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=jwvbrrsf8lx.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca \
    --to=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.
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).