From: CHENG Gao <chenggao@gmail.com>
Subject: Revised lisp/progmodes/flymake.el
Date: Fri, 19 Nov 2004 23:37:26 +0800 [thread overview]
Message-ID: <llcxluix.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
Reading FOR-RELEASE, I fuond it's desirable to revise flymake.el to
conform with Emacs Lisp Coding Conventions. Though my ELISP knowledge is
very limited, I think I can have a try for this too hard job.
Attached is a revised flymake.el. What I have done includes:
1. Removed XEmacs compatibility code. I think it does not make sense to
maintain XEmacs compatibility with Emacs bundled files.
2. Following Coding Conventions to remove close-parentheses on lines by
themselves.
3. Restructure and rewrite document strings to tips for documentation
strings.
But for some functions that I dont know their purposes, I just
capitalized the first letter and add period at the end.
4. Add eval-when-compile to one occurence or (require 'compile).
5. To accomodate documentation string, I changed function
flymake-get-common-path-prefix from
flymake-get-common-path-prefix (string-one string-two)
to
flymake-get-common-path-prefix (path1 path2)
and change the code to use new arg names.
Though as an ELISP newbie, I think flymake.el is coded badly. Just wish
my work can be help to real gurus to make a clean file.
At least there is no compilation errors/warnings for my revised file.
[-- Attachment #2: flymake.el --]
[-- Type: application/emacs-lisp, Size: 82715 bytes --]
[-- Attachment #3: Type: text/plain, Size: 39 bytes --]
--
这去者,不能见他的脸,背影模糊。
[-- Attachment #4: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2004-11-19 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 15:37 CHENG Gao [this message]
2004-11-19 15:51 ` Revised lisp/progmodes/flymake.el David Kastrup
2004-11-19 16:03 ` CHENG Gao
2004-11-20 10:05 ` Eli Zaretskii
2004-11-19 16:54 ` CHENG Gao
2004-11-21 1:10 ` Richard Stallman
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=llcxluix.fsf@gmail.com \
--to=chenggao@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.