From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Emacs lisp coding conventions
Date: Fri, 13 Jul 2001 09:50:34 +0900 [thread overview]
Message-ID: <yosug0c1ps85.fsf@jpl.org> (raw)
In-Reply-To: <m366cxevwq.fsf@SnowWhite.SuSE.cz>
>>>>> In <m366cxevwq.fsf@SnowWhite.SuSE.cz>
>>>>> Pavel@Janik.cz (Pavel Janík) wrote:
Pavel> Hi,
Pavel> while doing a cleanup in GNU Emacs to follow the Emacs lisp
Pavel> coding conventions which you can read in both XEmacs and GNU
Pavel> Emacs Lisp Reference manuals, I have come up with this
Pavel> patch. It cleans the files in the current Gnus CVS to follow
Pavel> these conventions:
By the way, I am using font-lock to highlight some kind of garbages,
for instance, leading and trailing whitespaces, long lines, etc.
ftp://ftp.jpl.org/pub/elisp/develock.el.gz
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2001-07-13 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 20:26 Pavel Janík
2001-07-13 0:50 ` Katsumi Yamaoka [this message]
2001-07-13 6:12 ` Pavel Janík
2001-07-13 19:29 ` ShengHuo ZHU
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yosug0c1ps85.fsf@jpl.org \
--to=yamaoka@jpl.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.
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 NNTP newsgroup(s).