[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Emacs's --geometry argument vs default-frame-alist
From: |
Stefan Monnier |
Subject: |
Emacs's --geometry argument vs default-frame-alist |
Date: |
Tue, 24 Oct 2006 14:27:08 -0400 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
The interaction between the --geometry argument and the default-frame-alist
setting has recently changed.
It is rather inconvenient for me now:
I typically start my Emacs as follows:
emacs --geometry 256x1+0-0
and in my .emacs I do something like:
(setq initial-frame-alist '((minibuffer . only)))
(setq default-frame-alist
'((minibuffer . nil) (height . 40) (width . 80) (user-size . t)))
This used to result in the exact behavior I want: Emacs starts as a single-line
minibuffer-only frame, and other frames have the normal size.
But now, my default-frame-alist I set in .emacs gets overwritten by the
"256x1" geometry argument, so subsequent frames also have this weird 256x1
shape :-(
What was the reason for the change?
Stefan
- Emacs's --geometry argument vs default-frame-alist,
Stefan Monnier <=