unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Roey Darwish Dror <roey.ghost@gmail.com>
Cc: 12205@debbugs.gnu.org
Subject: bug#12205: Problem in Emacs maximization in KDE
Date: Thu, 26 Sep 2019 17:03:31 +0200	[thread overview]
Message-ID: <CADwFkmnWoP67Q7+v76e7Eh4drhBvQE1CPkjbKph99fxi9k-3Fw@mail.gmail.com> (raw)
In-Reply-To: <CAKD89anRwrs6_LGOpRmMGBXVTvZ6rTeZUAcw1Y0uBWJs9RUvrw@mail.gmail.com>

oggRoey Darwish Dror <roey.ghost@gmail.com> writes:

> I'm Using KDE 4.8.5 in Fedora 17. My configuration removes the scroll
> bar, tool bar and menu bar. When I try to maximize Emacs, it occupies
> 99% of the screen, but I still see the desktop in the remaining
> edges. This bug doesn't seem to happen when the toolbar, scroll bar and
> menu bar are displayed.
>
> In GNU Emacs 24.1.1 (i686-redhat-linux-gnu, GTK+ Version 2.24.10)
>  of 2012-07-13 on x86-18.phx2.fedoraproject.org

I believe that this is no longer an issue since Emacs 24.4.  Quoting NEWS:

*** Emacs can now change frame sizes in units of pixels, rather than
text rows or columns.  When maximizing a frame or making it fullscreen,
remaining extra pixels are no longer given to the minibuffer, the rightmost
fringe, or other unusable space, but are distributed among the text
areas of the frame's windows.  If the new option `frame-resize-pixelwise'
is non-nil, all frame size changes happen pixelwise and set the
corresponding size hints for the window manager.

Could you please verify that this fixes your problem by testing on a
more recent version of Emacs?  If I don't hear back from you in a
couple of weeks, I'll assume that this has been resolved and close
this bug.

Best regards,
Stefan Kangas





  reply	other threads:[~2019-09-26 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 17:51 bug#12205: Problem in Emacs maximization in KDE Roey Darwish Dror
2019-09-26 15:03 ` Stefan Kangas [this message]
2019-10-29  4:40   ` Stefan Kangas

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=CADwFkmnWoP67Q7+v76e7Eh4drhBvQE1CPkjbKph99fxi9k-3Fw@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=12205@debbugs.gnu.org \
    --cc=roey.ghost@gmail.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.
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).