From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: RE: [drew.adams@oracle.com: RE: set-frame-position - is it a bug?]
Date: Sat, 28 Apr 2007 11:57:34 -0700 [thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMCEBNDBAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1G0glN-0002Vc-4P@fencepost.gnu.org>
This 2005 bug was never fixed. It is apparently a Windows-only bug. Could
this be fixed?
> From: Richard Stallman Sent: Wednesday, July 12, 2006 8:37 AM
> Would someone please try to debug this?
>
> To: "Emacs-Pretest-Bug" <emacs-pretest-bug@gnu.org>
> Date: Sat, 10 Jun 2006 09:56:26 -0700
>
> This bug was apparently never fixed. To reproduce, simply
> resize a frame horizontally so that the menu-bar wraps, then
> change the 'left frame parameter.
>
> (setq left-pos (cdr (assq 'left (frame-parameters))))
> (modify-frame-parameters (selected-frame)
> (list (cons 'left (+ 30 left-pos))))
>
> The frame moves down, as well as right.
>
> This is annoying if you have, for instance, a key bound to a
> command to move the frame right. Repeated use of this key
> sends the frame downward diagonally. Use of the complementary
> key to move the frame left sends it downward as well, so the
> two are not even inverses if the menu-bar wraps.
>
> Similarly, a command to move the frame up sends it down
> instead. So, if you have keys bound to commands that move it
> up and down, the up movement is
> down instead - the two are not inverses if the menu-bar wraps.
>
> Sent: Friday, August 05, 2005 7:39 AM
> To: help-gnu-emacs@gnu.org
> Cc: Emacs-Devel
> Subject: RE: set-frame-position - is it a bug?
>
> the intention of the following code
> (setq fpx (cdr (assoc 'left (frame-parameters))))
> (setq fpy (cdr (assoc 'top (frame-parameters))))
> (setq fpx (+ 1 fpx))
> (set-frame-position (next-frame) fpx fpy)
> is to move the frame honizontally 1 pixel right;
> but as a side-effect I get a vertical move as well.
> Is there something wrong with my code?
>
> The code looks OK to me.
>
> Is your menu-bar (or tool-bar) wider than your frame, so
> that it wraps around? That will cause the behavior you describe.
>
> Actually, now that I think of it, we should probably consider
> this an Emacs bug, so I'm cc'ing the emacs-devel list. Thanks for
> bringing this up - I've been aware of it for a long time, but it
> never occurred to me to file a bug.
>
> Bug: If menu-bar is wider than frame, so it wraps, then
> set-frame-position gets it wrong, in the manner described above.
prev parent reply other threads:[~2007-04-28 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 15:36 [drew.adams@oracle.com: RE: set-frame-position - is it a bug?] Richard Stallman
2006-07-12 16:07 ` Chong Yidong
2006-07-12 16:25 ` Drew Adams
2006-07-12 18:10 ` Eli Zaretskii
2006-07-12 18:22 ` Drew Adams
2006-07-13 3:13 ` Eli Zaretskii
2007-04-28 18:57 ` Drew Adams [this message]
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=EIENLHALHGIMHGDOLMIMCEBNDBAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).