From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 33531-done@debbugs.gnu.org
Subject: bug#33531: 26; Inappropriate single-quoting in (elisp) Frame Layout
Date: Wed, 28 Nov 2018 09:22:54 +0200 [thread overview]
Message-ID: <83ftvlfyy9.fsf@gnu.org> (raw)
In-Reply-To: <7e456de9-9254-45ff-8a30-58ae63a20170@default> (message from Drew Adams on Tue, 27 Nov 2018 13:08:14 -0800 (PST))
> Date: Tue, 27 Nov 2018 13:08:14 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
>
> The names used as headings ('Native Frame' etc.) should not be
> single-quoted, IMO. They are not Lisp objects of any kind. They are
> just doc terms.
Thanks, fixed.
next prev parent reply other threads:[~2018-11-28 7:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 21:08 bug#33531: 26; Inappropriate single-quoting in (elisp) Frame Layout Drew Adams
2018-11-28 7:22 ` Eli Zaretskii [this message]
2018-11-28 8:38 ` martin rudalics
2018-11-28 8:35 ` martin rudalics
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=83ftvlfyy9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33531-done@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).