mirror/emacs
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/emacs.git synced 2025-01-23 18:47:57 +00:00
Code Issues Releases Activity

A few tiny doc/ copyedits.

Browse Source
This commit is contained in:
Glenn Morris 2014-10-03 08:26:26 -07:00
parent c799337f12
commit 3df14aa689
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/emacs/cmdargs.texi
View File

@ -989,7 +989,7 @@ tool bar when it processes the specified geometry.
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}
you 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

12
doc/lispref/frames.texi
View File

@ -971,7 +971,7 @@ variable do not take effect immediately, only when you specify the
A list of symbols, specifying the @dfn{font backends} to use for
drawing fonts in the frame, in order of priority. On X, there are
currently two available font backends: @code{x} (the X core font
driver) and @code{xft} (the Xft font driver). On Windows, there are
driver) and @code{xft} (the Xft font driver). On MS-Windows, there are
currently two available font backends: @code{gdi} and
@code{uniscribe} (@pxref{Windows Fonts,,, emacs, The GNU Emacs
Manual}). On other systems, there is only one available font backend,
@ -1163,12 +1163,12 @@ size hints to the window manager. This means that this variable should
be set only in a user's initial file; applications should never bind it
temporarily.
The precise semantics of a value of @code{nil} for this option depends
on the toolkit used: Dragging the frame border with the mouse is usually
always done character-wise. Calling @code{set-frame-size} (see below)
The precise meaning of a value of @code{nil} for this option depends
on the toolkit used. Dragging the frame border with the mouse is usually
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+) or get accepted (Lucid, Motif, Windows).
of its character size, however, may: be ignored, cause a
rounding (GTK+), or be accepted (Lucid, Motif, MS-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''.