From: Jesper Harder <harder@myrealbox.com>
Subject: Re: New frame position (FSF Emacs on Windows)
Date: Fri, 07 Feb 2003 23:04:42 +0100 [thread overview]
Message-ID: <m3of5n7nnp.fsf@defun.localdomain> (raw)
In-Reply-To: ptq3su7c.fsf@morpheus.demon.co.uk
Paul Moore <gustav@morpheus.demon.co.uk> writes:
> I currently use XEmacs 21.5.10 on Windows (2000 and XP), mainly for
> news/mail via Gnus and occasionally for general editing tasks.
>
> 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!
This doesn't help you, but on X this usually something you adjust in you
window manager. For me a new frame is placed slightly offset from the
previous one by default. There's also a plethora of other placement
algorithms I could select.
> How can I get the frame creation behaviour I want from FSF Emacs?
I'm not sure exactly which algorithm you want. But this should give you
an idea: It places a new frame offset by 15 pixels from the previous:
(defun my-frame-position ()
(let ((left (or (cdr (assq 'left default-frame-alist)) 0))
(top (or (cdr (assq 'top default-frame-alist)) 0)))
(setq default-frame-alist
(cons (cons 'left (+ left 15))
(assq-delete-all 'left default-frame-alist))
default-frame-alist
(cons (cons 'top (+ top 15))
(assq-delete-all 'top default-frame-alist)))))
(add-to-list 'default-frame-alist '(user-position . t))
(add-hook 'before-make-frame-hook 'my-frame-position)
next prev parent reply other threads:[~2003-02-07 22:04 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
2003-02-08 17:42 ` Paul Moore
2003-02-07 22:04 ` Jesper Harder [this message]
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=m3of5n7nnp.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).