From: Drew Adams <drew.adams@oracle.com>
To: Mickey Ferguson <mickey.ferguson@motorolasolutions.com>
Cc: "Help-Gnu-Emacs (help-gnu-emacs@gnu.org)" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : programmatically make window full length but not change width
Date: Mon, 1 Aug 2022 17:57:06 +0000 [thread overview]
Message-ID: <SJ0PR10MB54884F67B4546950558CDF36F39A9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CADi0pTDN-ZU-=ZgzRr0Fq5JSTLoj07v_eTVS259R6Ptz7o+kCg@mail.gmail.com>
> After downloading the frame-cmds.el, I also needed frame-fns.el to allow things to compile. One other tweak I needed, since my windows toolbar is at the bottom of the screen, I needed to add:
>
> (setq window-mgr-title-bar-pixel-height '175)
>
> This made it size correctly on my laptop. However, if I connect to my remote desktop computer, using either VNC or Remote Desktop Connection, then that sizing is incorrect. It seemed to be around 60 for that computer. Oh, and each of these computers have a 1920x1080 display setting, if that makes any difference.
>
> Is this a setting that needs to be set individually for each computer?
For each context where the title bar has a different height.
`C-h v window-mgr-title-bar-pixel-height':
Height of frame title bar provided by the window manager, in pixels.
You might alternatively call this constant the title-bar "width" or
"thickness". There is no way for Emacs to determine this, so you
must set it.
You can set it conditionally based on however you can
determine the context and the right height for it.
From the source file you see that the default value is
set using this:
(cond ((eq window-system 'mac) 22)
;; For older versions of macOS, 40 might be better.
((eq window-system 'ns) 50)
(t 27))
If the difference between the contexts you mention is
reflected in the value of `window-system' then you can
use a similar sexp to set it appropriately in your init
file:
(setq window-mgr-title-bar-pixel-height
(cond ((eq window-system 'FOO) N)
((eq window-system 'BAR) M)
...
(t 27)))
Where FOO, BAR, N, and M are whatever values you need.
> If so, that's getting outside of what I would know how to do, since my goal is to have a single .emacs file for all of the computers where I work. Maybe it would be a registry setting or environment variable, for which I could easily have each computer have its own customized setting, and then the .emacs would get that env var or reg value on startup?
See above.
next prev parent reply other threads:[~2022-08-01 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 23:56 programmatically make window full length but not change width Mickey Ferguson via Users list for the GNU Emacs text editor
2022-07-30 1:03 ` [External] : " Drew Adams
2022-07-31 23:42 ` Mickey Ferguson via Users list for the GNU Emacs text editor
2022-08-01 1:18 ` Drew Adams
2022-08-01 17:26 ` Mickey Ferguson via Users list for the GNU Emacs text editor
2022-08-01 17:57 ` Drew Adams [this message]
2022-08-01 19:14 ` Mickey Ferguson via Users list for the GNU Emacs text editor
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=SJ0PR10MB54884F67B4546950558CDF36F39A9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mickey.ferguson@motorolasolutions.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).