From: martin rudalics <rudalics@gmx.at>
To: gottlieb@nyu.edu, "20552@debbugs.gnu.org" <20552@debbugs.gnu.org>
Subject: bug#20552: 24.4; cc
Date: Wed, 13 May 2015 09:37:03 +0200 [thread overview]
Message-ID: <5552FF1F.2010901@gmx.at> (raw)
In-Reply-To: <87zj5aq8ol.fsf@nyu.edu>
Please don't remove <20552@debbugs.gnu.org> from the list of recipients.
> I started with (left . 0). That moves the frame close to the left edge
> but not quite flush left. If I manually move the frame flush left and
> execute (modify-frame-parameters nil '( (width . 176) ( left . 0)))
> the frame moves *right* so that it is again about 1/8 inch away
Hmm... which window manager? Would
(modify-frame-parameters nil '((user-position . t) (width . 176) (left . 0)))
change anything?
>>> The weird part is if I execute the same command again (a second C-j in
>>> *scratch), the frame moves to the correct, flush left, position.
>>>
>>> (Since my screen is 2560 wide (left . -1300) should have the right edge
>>> a little left of center, instead it is very much right of center.)
>>
>> Maybe your window manager tries to keep the frame within the screen
>> boundaries.
>
> The weird part is that
>
> (modify-frame-parameters nil '( (width . 176) (left . -1300)))
>
> done once is not flush left but if done a second time to the same
> emacs -Q is flush left
My usual answer here is that eventually Jan will kick in and explain.
martin
next prev parent reply other threads:[~2015-05-13 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 20:10 bug#20552: 24.4; cc gottlieb
2015-05-12 9:36 ` martin rudalics
[not found] ` <87zj5aq8ol.fsf@nyu.edu>
2015-05-13 7:37 ` martin rudalics [this message]
2015-05-13 13:33 ` gottlieb
2015-05-13 13:40 ` gottlieb
2015-05-14 10:13 ` martin rudalics
2015-05-14 20:33 ` gottlieb
2015-05-15 16:44 ` martin rudalics
[not found] ` <87twvdn4tm.fsf@nyu.edu>
2015-05-19 9:42 ` martin rudalics
[not found] ` <87r3qcodz4.fsf@nyu.edu>
2015-05-20 9:50 ` martin rudalics
2015-05-14 20:58 ` gottlieb
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5552FF1F.2010901@gmx.at \
--to=rudalics@gmx.at \
--cc=20552@debbugs.gnu.org \
--cc=gottlieb@nyu.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.