From: Chetan <Chetan.xspam@xspam.sbcglobal.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Size of emacs window can't exceed 59 in height
Date: Wed, 08 Oct 2008 16:20:14 -0700 [thread overview]
Message-ID: <uk5cid68h.fsf@myhost.sbcglobal.net> (raw)
In-Reply-To: mailman.617.1223498497.25473.help-gnu-emacs@gnu.org
Peter Dyballa <Peter_Dyballa@Web.DE> writes:
> Am 08.10.2008 um 20:50 schrieb Chetan:
>
>> Value:
>> ((width . 120)
>> (height . 64)
>
>
> So you see the reason why GNU Emacs 22.x is always in "pole position." I think
> GNU Emacs 21.3 was not using *-frame-alist, so it follows the geometry as
> specified on invocation.
>
> To cure your GNU Emacs 22.x problem:
>
> (setq default-frame-alist
> (append (list
> (top . 200) (left . 300)
> ) default-frame-alist))
>
>
> --
> Greetings
>
> Pete
>
> I hope to die before I *have* to use Microsoft Word.
> - Donald E. Knuth, 2001-10-02 in Tübingen.
Thanks for the suggestion. It does seem to fix one problem, but creates
another. I like the default positioning provided for new frames. I
don't want to make all frames show up on top of each other.
I don't see the reason why this should happen. It seems to respect the
'left' value but not 'top'.
I do not set anything in the default-frame-alist except for the font.
The alist is initialized the way it is because of other functions I
call. The width and height are the values coming from the command
line.
I only mentioned it because somebody else had a similar problem.
I checked the NEWS file after I found this, but it seems to say that
the position values are used for the initial frame.
At first I thought it was a bug, but since it works from shell, there
is something else at play.
Chetan
next prev parent reply other threads:[~2008-10-08 23:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 8:32 Size of emacs window can't exceed 59 in height Torben Knudsen
2008-10-08 9:03 ` Peter Dyballa
2008-10-08 9:23 ` Torben Knudsen
2008-10-08 9:57 ` Peter Dyballa
2008-10-08 10:18 ` Torben Knudsen
2008-10-08 14:41 ` Peter Dyballa
2008-10-10 6:49 ` Torben Knudsen
2008-10-10 9:25 ` Peter Dyballa
2008-10-10 11:14 ` Torben Knudsen
2008-10-10 13:31 ` Peter Dyballa
2008-10-13 6:33 ` Torben Knudsen
2008-10-13 8:31 ` Peter Dyballa
[not found] ` <mailman.551.1223461110.25473.help-gnu-emacs@gnu.org>
2008-10-08 15:59 ` Chetan
2008-10-08 17:53 ` Peter Dyballa
[not found] ` <mailman.599.1223488487.25473.help-gnu-emacs@gnu.org>
2008-10-08 18:50 ` Chetan
2008-10-08 20:41 ` Peter Dyballa
[not found] ` <mailman.617.1223498497.25473.help-gnu-emacs@gnu.org>
2008-10-08 23:20 ` Chetan [this message]
2008-10-09 9:03 ` Peter Dyballa
[not found] ` <mailman.669.1223543046.25473.help-gnu-emacs@gnu.org>
2008-10-09 12:16 ` Chetan
2008-10-10 0:34 ` Tim X
2008-10-10 14:16 ` Chetan
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=uk5cid68h.fsf@myhost.sbcglobal.net \
--to=chetan.xspam@xspam.sbcglobal.net \
--cc=help-gnu-emacs@gnu.org \
/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).