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

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 73247 <at> debbugs.gnu.org, stefankangas <at> gmail.com
Subject: bug#73247: Move Android frame parameter documentation to elisp manual
Date: Sat, 14 Sep 2024 17:26:37 +0300

> From: Po Lu <luangruo <at> yahoo.com>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  73247 <at> debbugs.gnu.org
> Date: Sat, 14 Sep 2024 22:19:01 +0800
> 
> Stefan Kangas <stefankangas <at> gmail.com> writes:
> 
> > Eli Zaretskii <eliz <at> gnu.org> writes:
> >
> >> 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?
> >
> > That's my question, indeed.
> 
> There's no Android appendix in the Lisp reference manual, and in any
> event, it appears to be established practice to place window-system
> specific Lisp facilities in the appendix in the Emacs manual for the
> window system in question, of which (emacs)Mac / GNUstep Events is one
> example.

You don't need an appendix, you can put this in the body of the ELisp
manual.  The text seems short enough, so maybe we don't even need a
separate subsection.  There's nothing wrong in principle with having
window-system specific text in the main manual.

Previous Next

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