Opening *Calendar* in its own frame

Opening *Calendar* in its own frame

[Jonathon Isaac Swiderski]

I'm using v20.7.  I've the following in my .emacs to start speedbar and
calendar when in a window system.  Since i was using X11 when I got it from
a classmate, that's what it checks for, although it seems to work just fine
under Solaris 8's CDE.

(if (eq window-system 'x) ; if we are running under X windows...
    (progn
      (calendar)
      (speedbar)))


I'd like to have the calendar be in its own frame.  How can I do this?  I
thought of (make-frame (calendar)), but when I just now did in emacs

M-x eval-expression (make-frame (calendar))

, I got two of them -- one in a new frame, and one in the old frame.  (Yes,
I know they're the same buffer, but that's beside the point.)  Is it
possible to have the calendar just be in the one (newly-created) frame,
somewhat like the speedbar?

And if someone knows of a better way to do the
if-there's-a-graphical-environment check, i'd appreciate tips on that, too,
although I recall reading here previously that there doesn't seem to be a
good way to do it.  Currently the only window-system i use on a regular
basis is Solaris 8's CDE.

Thanks.

-- 
Jonathon Isaac Swiderski \\ dangercat-20@dangercat.net
cs.oberlin.edu/~jswiders  \\  www.dangercat.net/resume

Reason number #103 to use Linux: Because Linux users
are the social 3l337.

Re: Opening *Calendar* in its own frame

[Glenn Morris]

Jonathon Isaac Swiderski wrote:

> I'm using v20.7.
[...]
> (if (eq window-system 'x) ; if we are running under X windows...
>     (progn
>       (calendar)
>       (speedbar)))
>
>
> I'd like to have the calendar be in its own frame. 

(require 'cal-x)
(setq calendar-setup 'calendar-only)

I think it's a bug that you have to require cal-x (same in Emacs-21.x, by
the way). There are some other options for calendar-setup you might like to
investigate.

> And if someone knows of a better way to do the
> if-there's-a-graphical-environment check, i'd appreciate tips on that,
> too, although I recall reading here previously that there doesn't seem to
> be a good way to do it.

(when (display-graphic-p)
  (calendar)
  (speedbar))

would be the recommended test in Emacs-21.x, but for 20.7 I'm not sure if
there is anything better than window-system.

Re: Opening *Calendar* in its own frame

[Matt]

Glenn Morris wrote:
> Jonathon Isaac Swiderski wrote:
> 
> 
>>I'm using v20.7.
> 
> [...]
> 
>>(if (eq window-system 'x) ; if we are running under X windows...
>>    (progn
>>      (calendar)
>>      (speedbar)))
>>
>>
>>I'd like to have the calendar be in its own frame. 
> 
> 
> (require 'cal-x)
> (setq calendar-setup 'calendar-only)
> 
> I think it's a bug that you have to require cal-x (same in Emacs-21.x, by
> the way). There are some other options for calendar-setup you might like to
> investigate.
> 

That works. I added
	
	(select-frame-by-name "*scratch*")

to return focus to the main frame.

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

Re: Opening *Calendar* in its own frame

[Matt]

Matt wrote:

> 
> That works. I added
>     
>     (select-frame-by-name "*scratch*")
> 
> to return focus to the main frame.
> 

Of course

	(other-frame 3)

works also.

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

Re: Opening *Calendar* in its own frame

[Galen Boyer]

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.

-- 
Galen deForest Boyer
Sweet dreams and flying machines in pieces on the ground.

Re: Opening *Calendar* in its own frame

[Matt]

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.

Re: Opening *Calendar* in its own frame

[Eli Zaretskii]

On Tue, 21 Jan 2003, Matt wrote:

> 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?

Sounds like a big in Calendar.  Perhaps it assumes that a menu is always 
available on a graphic display.

I suggest to report this as a bug.  Maybe set debug-on-error to t and see 
if you get any useful traceback; if so, include it in the bug report.

TIA

Re: Opening *Calendar* in its own frame

[Jonathon Isaac Swiderski]

On Mon, 20 Jan 2003, Matt wrote:
> > Jonathon Isaac Swiderski wrote:
> >
> >>I'm using v20.7.
> >
> > [...]
> >
> >>(if (eq window-system 'x) ; if we are running under X windows...
> >>    (progn
> >>      (calendar)
> >>      (speedbar)))
> >>
> >>
> >>I'd like to have the calendar be in its own frame.
> >
>
> I added  (select-frame-by-name "*scratch*")
> to return focus to the main frame.

I have 'focus-follows-mouse' in my CDE setup, but i did reverse the order
the two are created:   (speedbar) (calendar)
so that the speedbar doesn't associate itself with the calendar frame
(i.e., match the calendar's size and position on startup, try to find files
in the calendar frame, etc.).

thanks to galen et al. for your help.

-- 
Jonathon Isaac Swiderski \\ dangercat-20@dangercat.net
cs.oberlin.edu/~jswiders  \\  www.dangercat.net/resume

"Those are my principles. If you don't like them, I have others."
  -- Groucho Marx