From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: New frame position (FSF Emacs on Windows)
Date: Fri, 07 Feb 2003 22:25:47 +0100 [thread overview]
Message-ID: <84d6m3zstg.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: ptq3su7c.fsf@morpheus.demon.co.uk
Paul Moore <gustav@morpheus.demon.co.uk> writes:
> Anyway, one annoying feature in FSF Emacs is that when I open a new
> frame (for example, with C-X 5 f) it appears in *exactly* the same
> position on screen as the current frame. It therefore looks like I
> didn't open a new frame!
Do you have left and top in default-frame-alist? Does it help to
remove them?
--
A turnip curses Elvis
next prev parent reply other threads:[~2003-02-07 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 20:37 New frame position (FSF Emacs on Windows) Paul Moore
2003-02-07 21:25 ` Kai Großjohann [this message]
2003-02-08 17:42 ` Paul Moore
2003-02-07 22:04 ` Jesper Harder
2003-02-08 18:43 ` Paul Moore
2003-02-09 4:31 ` Jesper Harder
2003-02-09 11:52 ` Paul Moore
2003-02-08 2:30 ` Galen Boyer
2003-02-08 18:46 ` Paul Moore
2003-02-09 3:32 ` Galen Boyer
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=84d6m3zstg.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).