GNU bug report logs - #73247
Move Android frame parameter documentation to elisp manual

Previous Next

Package: emacs;

Reported by: Stefan Kangas <stefankangas <at> gmail.com>

Date: Sat, 14 Sep 2024 12:40:01 UTC

Severity: wishlist

Tags: confirmed

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefankangas <at> gmail.com>, luangruo <at> yahoo.com
Cc: 73247 <at> debbugs.gnu.org
Subject: bug#73247: Move Android frame parameter documentation to elisp manual
Date: Sat, 14 Sep 2024 16:52:56 +0300
> Cc: Po Lu <luangruo <at> yahoo.com>
> From: Stefan Kangas <stefankangas <at> 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?




This bug report was last modified 224 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.