diff options
author | Martin Rudalics <rudalics@gmx.at> | 2014-10-03 11:18:49 +0200 |
---|---|---|
committer | Martin Rudalics <rudalics@gmx.at> | 2014-10-03 11:18:49 +0200 |
commit | f63bd04be9c6a1a9b09749a86ac693726994bda2 (patch) | |
tree | 698c3b04654ee34bca1ef44f3474f320b40013cc /doc | |
parent | a81e5de3a34d27cea43d49ffdfd9755f0eddb262 (diff) | |
download | emacs-f63bd04be9c6a1a9b09749a86ac693726994bda2.tar.gz |
Mention `frame-resize-pixelwise' to make frames truly fullscreen or maximized.
* frame.el (toggle-frame-maximized, toggle-frame-fullscreen):
In doc-string mention need of setting `frame-resize-pixelwise'.
* frames.texi (Frame Commands):
* cmdargs.texi (Window Size X): Mention the use of
`frame-resize-pixelwise' to make frames truly fullscreen or
maximized.
* frames.texi (Size Parameters, Size and Position): Mention that
with some window managers you have to set
`frame-resize-pixelwise' in order make a frame truly fullscreen
or maximized.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/emacs/ChangeLog | 7 | ||||
-rw-r--r-- | doc/emacs/cmdargs.texi | 8 | ||||
-rw-r--r-- | doc/emacs/frames.texi | 4 | ||||
-rw-r--r-- | doc/lispref/ChangeLog | 7 | ||||
-rw-r--r-- | doc/lispref/frames.texi | 10 |
5 files changed, 31 insertions, 5 deletions
diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog index b4d13d24325..5d262c00c33 100644 --- a/doc/emacs/ChangeLog +++ b/doc/emacs/ChangeLog @@ -1,3 +1,10 @@ +2014-10-03 Martin Rudalics <rudalics@gmx.at> + + * frames.texi (Frame Commands): + * cmdargs.texi (Window Size X): Mention the use of + `frame-resize-pixelwise' to make frames truly fullscreen or + maximized. + 2014-10-01 Glenn Morris <rgm@gnu.org> * package.texi (Package Installation): Mention etc/package-keyring.gpg. diff --git a/doc/emacs/cmdargs.texi b/doc/emacs/cmdargs.texi index 8b3654dae68..56137272be6 100644 --- a/doc/emacs/cmdargs.texi +++ b/doc/emacs/cmdargs.texi @@ -987,10 +987,10 @@ size with no tool bar, use an X resource to specify ``no tool bar'' (@pxref{Table of Resources}); then Emacs will already know there's no tool bar when it processes the specified geometry. - When using one of @samp{--fullscreen}, @samp{--maximized}, @samp{--fullwidth} -or @samp{--fullheight} there may be some space around the frame -anyway. That is because Emacs rounds the sizes so they are an -even number of character heights and widths. + When using one of @samp{--fullscreen}, @samp{--maximized}, +@samp{--fullwidth} or @samp{--fullheight}, some window managers require +to set the variable @code{frame-resize-pixelwise} to a non-@code{nil} +value to make a frame appear truly ``maximized'' or ``fullscreen''. Some window managers have options that can make them ignore both program-specified and user-specified positions. If these are set, diff --git a/doc/emacs/frames.texi b/doc/emacs/frames.texi index 036e8cf65eb..8c2289b83de 100644 --- a/doc/emacs/frames.texi +++ b/doc/emacs/frames.texi @@ -469,6 +469,10 @@ hides window manager decorations, giving slightly more screen space to Emacs itself.) @end table + Note that with some window managers you may have to customize the +variable @code{frame-resize-pixelwise} to a non-@code{nil} value in +order to make a frame truly ``maximized'' or ``fullscreen''. + The @kbd{C-x 5 0} (@code{delete-frame}) command deletes the selected frame. However, it will refuse to delete the last frame in an Emacs session, to prevent you from losing the ability to interact with the diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index e8efcaa923c..1272e740745 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,10 @@ +2014-10-03 Martin Rudalics <rudalics@gmx.at> + + * frames.texi (Size Parameters, Size and Position): Mention that + with some window managers you have to set + `frame-resize-pixelwise' in order make a frame truly fullscreen + or maximized. + 2014-09-04 Stefan Monnier <monnier@iro.umontreal.ca> * functions.texi (Core Advising Primitives): Add a note about the diff --git a/doc/lispref/frames.texi b/doc/lispref/frames.texi index b6513426909..92b5791051b 100644 --- a/doc/lispref/frames.texi +++ b/doc/lispref/frames.texi @@ -686,6 +686,11 @@ difference between @code{maximized} and @code{fullboth} is that the former can still be resized by dragging window manager decorations with the mouse, while the latter really covers the whole screen and does not allow resizing by mouse dragging. + +With some window managers you may have to customize the variable +@code{frame-resize-pixelwise} to a non-@code{nil} value in order to make +a frame appear ``maximized'' or ``fullscreen''. + @end table @node Layout Parameters @@ -1163,7 +1168,10 @@ on the toolkit used: Dragging the frame border with the mouse is usually always done character-wise. Calling @code{set-frame-size} (see below) with arguments that do not specify the frame size as an integer multiple of its character size may be, however, either ignored or cause a -rounding (GTK+, Windows) or get accepted (Lucid, Motif). +rounding (GTK+) or get accepted (Lucid, Motif, Windows). + +With some window managers you may have to set this to non-@code{nil} in +order to make a frame appear truly ``maximized'' or ``fullscreen''. @end defopt @defun set-frame-size frame width height pixelwise |