unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Problems positioning and sizing Emacs frames
Date: Tue, 20 Dec 2022 18:50:08 +0100	[thread overview]
Message-ID: <25505.62928.514443.188767@tux.local> (raw)
In-Reply-To: Msg <87sfhachjg.fsf@yahoo.com> of 2022-12-20 21:48:35 +0800 from luangruo@yahoo.com

Po Lu,

On Tuesday, 2022-12-20 21:48:35 +0800, you wrote:

> ...
> Did you set `frame-resize-pixelwise' to t?

I didn't up to now.   However, setting it changed neither size nor posi-
tion of the initial frame,  but it slightly changed the window manager's
geometry information for the frames created via "C-x 5 Cf":  it returned
"1040x950+58+58"  for the first frame  and "1040x950+87+46" for the sec-
ond,  where the "1040x950" part  probably is the  "80x40" window size in
pixels, the difference between 58 and 87 still is 29 pixels to the right
while the difference between 58 and 46 is 12 pixels up,  which might not
have had any effect in my former tests because these frames were already
at "+xxx+0", and thus going farther up was just not possible.

I had set "frame-resize-pixelwise"  in my "init.el" file,  but according
to the documentation this file is only read  AFTER the initial frame has
been created.   Upon further reading  the documentation  I finally found
frame parameter "user-position",  and setting this to "t"  in both vari-
ables,  "default-frame-alist" and "initial-frame-alist"  at least solved
the positioning problems for the frames opened via "C-x 5 C-f".  Uff :-)

Another observation regarding the initial frame:  when I open a new file
in these frames and enter "C-u 90 O",  the gap in the uppermost line be-
tween the rightmost "O"  and the continuation symbol  in the fringe area
is roughly twice as wide in the "79x40" frame  as in the "80x40" frames.
Could this indicate some rounding effect  eventually causing the initial
frame becoming too wide and being cut off?

Sincerely,
  Rainer



      reply	other threads:[~2022-12-20 17:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 18:29 Problems positioning and sizing Emacs frames Dr Rainer Woitok
2022-12-20  1:41 ` Po Lu
2022-12-20 11:37   ` Dr Rainer Woitok
2022-12-20 12:32     ` Po Lu
2022-12-20 13:34       ` Dr Rainer Woitok
2022-12-20 13:48         ` Po Lu
2022-12-20 17:50           ` Dr Rainer Woitok [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=25505.62928.514443.188767@tux.local \
    --to=rainer.woitok@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=luangruo@yahoo.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).