From: Drew Adams <drew.adams@oracle.com>
To: 18635@debbugs.gnu.org
Subject: bug#18635: 24.4.50; doc string of `font-lock-keywords' - lines too long
Date: Sun, 5 Oct 2014 11:16:25 -0700 (PDT) [thread overview]
Message-ID: <0eac21f3-0b97-4c39-9ee8-2d9b068cdd02@default> (raw)
Please fill the paragraphs with a smaller `fill-column', in keeping with
the Emacs-Lisp conventions set forth in (elisp) `Documentation Tips'.
In particular:
Lines should generally not exceed 60 chars in length. Filled paragraphs
should generally respect `emacs-lisp-docstring-fill-column', whose
default value is 65.
In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
of 2014-09-15 on LEG570
Bzr revision: 117884 dancol@dancol.org-20140915050944-sqsajysnwef51f9m
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking 'CFLAGS=-O0 -g3' CPPFLAGS=-DGLYPH_DEBUG=1'
reply other threads:[~2014-10-05 18:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0eac21f3-0b97-4c39-9ee8-2d9b068cdd02@default \
--to=drew.adams@oracle.com \
--cc=18635@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).