From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 31858@debbugs.gnu.org
Subject: bug#31858: 27.0; doc of `window-toggle-side-windows'
Date: Sat, 16 Jun 2018 19:28:02 +0300 [thread overview]
Message-ID: <837emyzofh.fsf@gnu.org> (raw)
In-Reply-To: <65951719-2046-44e9-8946-692a7a15d6d0@default> (message from Drew Adams on Sat, 16 Jun 2018 05:35:10 -0700 (PDT))
> Date: Sat, 16 Jun 2018 05:35:10 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> AFAICT, neither the doc string nor the manual says what toggling the
> side windows DOES or MEANS. Just what behavior or appearance is
> toggled? What happens when a side window is - or all side windows are -
> toggled?
That's strange. I found answers to those questions in the doc string:
If FRAME has at least one side window, save FRAME’s state in the
FRAME’s ‘window-state’ frame parameter and delete all side
windows on FRAME afterwards. Otherwise, if FRAME has a
‘window-state’ parameter, use that to restore any side windows on
FRAME leaving FRAME’s main window alone. Signal an error if
FRAME has no side window and no saved state is found.
So I don't understand what is missing there. Could you be more
specific regarding the problems you see in this text?
next prev parent reply other threads:[~2018-06-16 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 12:35 bug#31858: 27.0; doc of `window-toggle-side-windows' Drew Adams
2018-06-16 16:28 ` Eli Zaretskii [this message]
2018-06-16 23:11 ` Drew Adams
2018-06-16 23:18 ` Noam Postavsky
2018-06-17 0:14 ` Drew Adams
2018-06-17 3:46 ` Eli Zaretskii
[not found] <<65951719-2046-44e9-8946-692a7a15d6d0@default>
[not found] ` <<837emyzofh.fsf@gnu.org>
[not found] ` <<294e533a-0cd8-417f-b83c-f40c2ebb8ed9@default>
[not found] ` <<87in6itj6c.fsf@gmail.com>
[not found] ` <<1e768b88-46ea-4e55-9403-2ce27d1cc63c@default>
[not found] ` <<83wouyxegg.fsf@gnu.org>
2018-06-17 4:20 ` Drew Adams
2018-06-17 5:43 ` Eli Zaretskii
2018-06-17 7:53 ` martin rudalics
[not found] <<<65951719-2046-44e9-8946-692a7a15d6d0@default>
[not found] ` <<<837emyzofh.fsf@gnu.org>
[not found] ` <<<294e533a-0cd8-417f-b83c-f40c2ebb8ed9@default>
[not found] ` <<<87in6itj6c.fsf@gmail.com>
[not found] ` <<<1e768b88-46ea-4e55-9403-2ce27d1cc63c@default>
[not found] ` <<<83wouyxegg.fsf@gnu.org>
[not found] ` <<18382c51-ad2f-499a-a6d7-02e802abb908@default>
[not found] ` <<83po0qx915.fsf@gnu.org>
2018-06-17 14:22 ` Drew Adams
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=837emyzofh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31858@debbugs.gnu.org \
--cc=drew.adams@oracle.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).