From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>, luangruo@yahoo.com
Cc: 73247@debbugs.gnu.org
Subject: bug#73247: Move Android frame parameter documentation to elisp manual
Date: Sat, 14 Sep 2024 16:52:56 +0300 [thread overview]
Message-ID: <86y13ufikn.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=C-0Tkm9w+moimWW=1JO34eMMbLep7OTeCkC92XkPdzw@mail.gmail.com> (message from Stefan Kangas on Sat, 14 Sep 2024 05:39:10 -0700)
> Cc: Po Lu <luangruo@yahoo.com>
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 14 Sep 2024 05:39:10 -0700
>
> Severity: wishlist
>
> The only index entry we have for "frame parameters" in the emacs manual
> is "frame parameters, android". Since frame parameters are documented
> in the elisp manual for other platforms, I think we should consider
> moving this part from (info "(emacs) Android Windowing"):
>
> > Emacs only supports a limited subset of GUI features on Android; the
> > limitations are as follows:
> >
> > • Scroll bars are not supported, as they are close to useless on
> > Android devices.
> >
> > • The ‘alpha’, ‘alpha-background’, ‘z-group’, ‘override-redirect’,
> > ‘mouse-color’, ‘title’, ‘wait-for-wm’, ‘sticky’, and ‘undecorated’
> > frame parameters (*note (elisp)Frame Parameters::) are unsupported.
> >
> > • On Android 4.0 and earlier, the ‘fullscreen’ frame parameter is
> > always ‘maximized’ for top-level frames; on later versions of
> > Android, it can also be ‘fullscreen’.
Why is this in the user manual? Frame parameters are Lisp-level
feature, and are fully documented in the ELisp manual. Are there any
reasons not to move this there, as a separate subsection?
next prev parent reply other threads:[~2024-09-14 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 12:39 bug#73247: Move Android frame parameter documentation to elisp manual Stefan Kangas
2024-09-14 13:52 ` Eli Zaretskii [this message]
2024-09-14 14:06 ` Stefan Kangas
2024-09-14 14:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-14 14:26 ` Eli Zaretskii
2024-09-14 13:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86y13ufikn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73247@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=stefankangas@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).