summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMartin Rudalics <rudalics@gmx.at>2017-11-02 09:28:25 +0100
committerMartin Rudalics <rudalics@gmx.at>2017-11-02 09:28:25 +0100
commit27964af438c9a25dedd2e7bccb1a11ddfe679858 (patch)
tree9b8aa633c5d5aa158e4c41774ed1d98901caa455
parent1bd4e7c2437825af7d3ea0bee2498f0ea70b4314 (diff)
downloademacs-27964af438c9a25dedd2e7bccb1a11ddfe679858.tar.gz
In frame parameters documentation mention desktop saving/restoring
* doc/lispref/frames.texi (Frame Parameters): Mention that applications have to care about which parameters they want to get saved and restored by the desktop library.
-rw-r--r--doc/lispref/frames.texi7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/lispref/frames.texi b/doc/lispref/frames.texi
index 5ea7125882f..a146061c771 100644
--- a/doc/lispref/frames.texi
+++ b/doc/lispref/frames.texi
@@ -1210,6 +1210,13 @@ terminal supports colors, the parameters @code{foreground-color},
@code{display-type} are also meaningful. If the terminal supports
frame transparency, the parameter @code{alpha} is also meaningful.
+ By default, frame parameters are saved and restored by the desktop
+library functions (@pxref{Desktop Save Mode}) when the variable
+@code{desktop-restore-frames} is non-@code{nil}. It's the
+responsibility of applications that their parameters are included in
+@code{frameset-persistent-filter-alist} to avoid that they get
+meaningless or even harmful values in restored sessions.
+
@menu
* Parameter Access:: How to change a frame's parameters.
* Initial Parameters:: Specifying frame parameters when you make a frame.