Bug 1536777 - Emacs opens with a full-screen wide window on HiDPI screens
Summary: Emacs opens with a full-screen wide window on HiDPI screens
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Synacek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-21 01:37 UTC by Scott Talbert
Modified: 2018-06-16 01:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-16 01:24:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Scott Talbert 2018-01-21 01:37:33 UTC
Description of problem:
When using emacs on a HiDPI screen, when opening a file, the window will take up the entire screen width.

Version-Release number of selected component (if applicable):
25.3-3

How reproducible:
100%

Steps to Reproduce:
1. Open emacs on a HiDPI screen
2.
3.

Actual results:
Window takes up the entire screen

Expected results:
Window is a standard 80 column width

Additional info:

Comment 1 Chris Siebenmann 2018-04-24 05:50:23 UTC
I have a hand-crafted X environment on a HiDPI display where I have the X
server DPI set accurately (in various places) and normally set GDK_SCALE=2
and GDK_DPI_SCALE=0.5. Un-setting both environment variables caused Emacs
to stop doing this maximization at startup, as does setting both of them to 1.

I'm using emacs-25.3-3.fc27.x86_64.

This maximization appears to override all other ways of setting Emacs'
initial size. I have X resources set, I have used -geometry on the
command line, and I have tried setting initial-frame-alist and so on in
my .emacs. None of them had any effect. Nor did starting Emacs with '-q
--no-site-file -nsl'.

Comment 2 Scott Talbert 2018-06-16 01:24:46 UTC
This appears to have been fixed in emacs 26.1, which is now in F28.  :)


Note You need to log in before you can comment on or make changes to this bug.