From: Will Willis <will.willis@gmail.com>
To: Kevin Rodgers <kevin.d.rodgers@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: Version Control Log window destroys all frames on exit
Date: Wed, 26 Aug 2009 21:10:15 -0500 [thread overview]
Message-ID: <6ee1e6090908261910y79ca1f23yacd39ea3713286fe@mail.gmail.com> (raw)
In-Reply-To: <h74nvb$7k7$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
This is great!! Thanks so much. My window arrangements stay in tact and the
few popup frame works like a charm. Seriously, this is great.
One thing I noticed is that if I only have one buffer showing, after I C-c
C-c in the popup, the popup disappears then my single window is split
vertically into two (ala C-x 2). On odd behavior , but one I can live with.
Thanks again for the help!! This has made my day.
On Wed, Aug 26, 2009 at 8:36 PM, Kevin Rodgers <kevin.d.rodgers@gmail.com>wrote:
> Will Willis wrote:
>
>> Whenever I check in a file (with subversion), VC mode opens up a temporary
>> buffer for me to leave a checkin message. I generally have a frame or two
>> already open. VC mode will take a frame (I'm ok with that) but after I
>> commit the message (C-c C-c) I'm left with one buffer in the window - the
>> file that VC mode was checking in.
>>
>> I'd prefer to have all my frames still in tact after checking in the file.
>> Is this possible?
>>
>
> Give the *VC-log* buffer its own frame (which C-c C-c will delete):
>
> (setq special-display-buffer-names
> (cons "*VC-log*" special-display-buffer-names))
>
> --
> Kevin Rodgers
> Denver, Colorado, USA
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1733 bytes --]
prev parent reply other threads:[~2009-08-27 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 1:09 Version Control Log window destroys all frames on exit Will Willis
2009-08-27 1:36 ` Kevin Rodgers
2009-08-27 2:10 ` Will Willis [this message]
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=6ee1e6090908261910y79ca1f23yacd39ea3713286fe@mail.gmail.com \
--to=will.willis@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=kevin.d.rodgers@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 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.