From: Arun Isaac <arunisaac@systemreboot.net>
To: 32401@debbugs.gnu.org
Subject: bug#32401: Improving set-fontset-font docstring
Date: Wed, 08 Aug 2018 20:25:07 +0530 [thread overview]
Message-ID: <cu7eff87vsk.fsf@systemreboot.net> (raw)
There is a minor grammatical error in the following part of the
docstring of set-fontset-font.
"TARGET may be nil. In that case, use FONT-SPEC for any characters for
that no FONT-SPEC is specified."
It should be "for which no FONT-SPEC is specified" instead of "for that
no FONT-SPEC is specified". Replace "that" by "which".
Also, in an earlier part of the docstring, the description of "script
name symbol" and "charset" could be improved by adding a link to the
list of available scripts and charsets, or describing some means to find
the supported scripts and charsets.
next reply other threads:[~2018-08-08 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 14:55 Arun Isaac [this message]
2018-08-08 15:25 ` bug#32401: Improving set-fontset-font docstring Eli Zaretskii
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=cu7eff87vsk.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=32401@debbugs.gnu.org \
/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).