all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matt <nwzmattXX@XXnetscape.net>
Subject: Re: Opening *Calendar* in its own frame
Date: Tue, 21 Jan 2003 03:04:17 GMT	[thread overview]
Message-ID: <3E2CB8B1.7090309@XXnetscape.net> (raw)
In-Reply-To: uiswjfdef.fsf@hotpop.com



Galen Boyer wrote:
> On Mon, 20 Jan 2003, jonswid@umich.edu wrote:
> 
> 
>>I'd like to have the calendar be in its own frame.  How can I do this?
> 
> 
> I used my setting for the buffer *apropos*, so customize to your liking.
> 
> (setq special-display-buffer-names
>       '(("*Calendar*"
> 	 (top . 5)
> 	 (left . -75)
> 	 (width . 80)
> 	 (height . 50)
> 	 (menu-bar-lines . 0)
> 	 (font . "-outline-Courier New-normal-r-normal-normal-13-97-96-96-c-*-iso8859-15")
> 	 (foreground-color . "black")
> 	 (background-color . "light steel blue"))))
> 
> I love this special-display-buffer-names.  Buffers by the names, 
> 
> *info* *Help* *Apropos* *Backtrace* *Input History* *Occur*
> *grep* *Colors* *Shell Command Output* *compilation*
> 
> all show up in their own frames with each frame customized to my liking.
> Very slick functionality IMO.
> 

Cool stuff! One thing is driving me crazy though. If I set 
`menu-bar-lines' to anything other than 0 or remove the line all 
together, I get an annoying bell when the frame is created. It only 
happens with the Calendar. Any idea whay this is?

Matt
-- 
Remove the X's to reply directly.

  reply	other threads:[~2003-01-21  3:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20 20:16 Opening *Calendar* in its own frame Jonathon Isaac Swiderski
2003-01-20 21:17 ` Glenn Morris
2003-01-20 21:58   ` Matt
2003-01-20 23:01     ` Matt
2003-01-24 21:53     ` Jonathon Isaac Swiderski
2003-01-20 23:14 ` Galen Boyer
2003-01-21  3:04   ` Matt [this message]
2003-01-21  6:16     ` Eli Zaretskii

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=3E2CB8B1.7090309@XXnetscape.net \
    --to=nwzmattxx@xxnetscape.net \
    /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.