From: Xue Fuqiao <xfq.free@gmail.com>
To: Shakthi Kannan <shakthimaan@gmail.com>
Cc: 9130@debbugs.gnu.org
Subject: bug#9130: Document Lisp mode fontification for strings after :documentation
Date: Thu, 31 Dec 2015 08:09:02 +0800 [thread overview]
Message-ID: <CAAF+z6Gca_dRsoxtYZzoYZpRtig5124tFEippp9mUSRLH+jO3g@mail.gmail.com> (raw)
In-Reply-To: <831ta3ddcl.fsf@gnu.org>
On Thu, Dec 31, 2015 at 2:02 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 30 Dec 2015 11:52:38 +0530
>> From: Shakthi Kannan <shakthimaan@gmail.com>
>> Cc: bug-gnu-emacs@gnu.org
>>
>> I have received the docstrings for the three functions from the
>> author, Robert Brown, and I am re-submitting the patch.
>
> Thanks, pushed with some changes. Please see how I changed the doc
> strings for conformance with Emacs coding style: the first line of the
> doc string must be a full sentence. If the first sentence is too long
> for that, make it shorter, omitting some details for the rest of the
> doc string.
Shakthi, please see (info "(elisp) Documentation Tips") for some tips
and conventions for writing/formatting doc strings.
next prev parent reply other threads:[~2015-12-31 0:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 16:50 bug#9130: 23.3; Lisp mode doc string enhancment Robert Brown
2011-08-02 20:01 ` Stefan Monnier
2014-03-25 17:54 ` Robert Brown
2014-06-19 14:04 ` bug#9130: 23.3; Lisp mode doc string enhancement Stefan Monnier
2015-12-16 17:10 ` bug#9130: Document Lisp mode fontification for strings after :documentation Shakthi Kannan
2015-12-16 17:53 ` Eli Zaretskii
2015-12-16 18:07 ` Shakthi Kannan
2015-12-16 18:47 ` Eli Zaretskii
2015-12-16 18:54 ` Shakthi Kannan
2015-12-16 18:56 ` Eli Zaretskii
2015-12-17 16:59 ` Shakthi Kannan
2015-12-18 15:35 ` Eli Zaretskii
2015-12-18 15:58 ` Shakthi Kannan
2015-12-18 16:10 ` Eli Zaretskii
2015-12-30 6:22 ` Shakthi Kannan
2015-12-30 18:02 ` Eli Zaretskii
2015-12-31 0:09 ` Xue Fuqiao [this message]
2015-12-31 5:32 ` Shakthi Kannan
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=CAAF+z6Gca_dRsoxtYZzoYZpRtig5124tFEippp9mUSRLH+jO3g@mail.gmail.com \
--to=xfq.free@gmail.com \
--cc=9130@debbugs.gnu.org \
--cc=shakthimaan@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).