From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 73247@debbugs.gnu.org
Subject: bug#73247: Move Android frame parameter documentation to elisp manual
Date: Sat, 14 Sep 2024 22:19:01 +0800 [thread overview]
Message-ID: <87v7yynwru.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmnPS2W-mz7-Lu1N2z2UGyaA1fx_r1LsXafKdh+2_zqhLw@mail.gmail.com> (Stefan Kangas's message of "Sat, 14 Sep 2024 07:06:24 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> Eli Zaretskii <eliz@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.
next prev parent reply other threads:[~2024-09-14 14:19 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
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 [this message]
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=87v7yynwru.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=73247@debbugs.gnu.org \
--cc=eliz@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).