From: MON KEY <monkey@sandpframing.com>
To: emacs-devel@gnu.org
Subject: Re: visual-line-mode and line wrapping
Date: Mon, 24 May 2010 22:52:21 -0400 [thread overview]
Message-ID: <AANLkTilG5f2wDwGIgsCWAZFt9du5NauX92bguJGU8UON@mail.gmail.com> (raw)
> You're preaching to the choir here (why do you think we have an "80
> columns max" limit on C and Elisp code?).
This limit has really been on my mind lately. FTMP I agree with the
rationale, its benefits, and am (in general) a strong advocate.
However, something I find really disconcerting (and biased) is that
there is a fundamental difference between (E)lisp code and C code, and
the 80 col limit is far more C centric. Moreover, the convention is
not particularly friendly to code that employs features from the CL
package. Likewise, in the absence of _real_ namespacing third party
fncns must extend by at least two extra tokens for each def* in order
not to step on Emacs' core fncns. In the aggregate these factors can
make it particularly difficult for third party code to meet with the
80 col rule. Following are examples of moderately sized lambda lists
(with IMHO unreasonably truncated arg names):
A conventional Elisp fncn from Emacs' lisp/* directory:
(defun elisp-fun (arg1 arg2 &optional arg3 &rest arg4)
^^^^^!^^^^^^^^^!^^^^^!^^^^!^^^^^^^^^^^^^^!^^^^^^^^^^^!
5 15 21 26 41 53
Same Elisp fncn from Emacs' lisp/* directory with CL features:
(defun* elisp-fun (arg1 arg2 &optional (arg3 arg3-dflt) &rest arg4)
^^^^^^!^^^^^^^^^!^^^^^!^^^^!^^^^^^^^^^^^^^^!^^^^^^^^^^!^^^^^^^^^^^!
6 16 22 27 44 54 66
Same(ish) but w/ CL packages keywords feature:
(defun* elisp-fun (arg1 arg2 &rest arg4 &key arg3 arg3-alt)
^^^^^^!^^^^^^^^^!^^^^^!^^^^!^^^^^^^^^^!^^^^^^^^^!^^^^^^^^^!
6 16 22 27 38 47 58
User function with four token textual namespace:
(defun usr-elisp-fun (arg1 arg2 &optional arg3 &rest arg4)
^^^^^!^^^^^^^^^^^^^!^^^^^!^^^^!^^^^^^^^^^^^^^!^^^^^^^^^^^!
5 15 25 30 45 57
It would be an interesting exercise to do a count of the number of defun,
defsubst,, defmacro forms in lisp/* which have their parameter
list split over two or more lines to accommodate the 80 limit.
--
/s_P\
next reply other threads:[~2010-05-25 2:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 2:52 MON KEY [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-24 14:09 visual-line-mode and line wrapping Leo
2010-05-24 14:12 ` Lennart Borgman
2010-05-24 15:08 ` Leo
2010-05-24 15:29 ` Lennart Borgman
2010-05-24 16:42 ` Leo
2010-05-24 17:41 ` Lennart Borgman
2010-05-24 17:34 ` Stefan Monnier
2010-05-24 19:18 ` Leo
2010-05-24 19:31 ` Chong Yidong
2010-05-24 19:53 ` Leo
2010-05-24 20:33 ` Lennart Borgman
2010-05-24 19:58 ` Lennart Borgman
2010-05-24 20:27 ` Leo
2010-05-24 20:36 ` Lennart Borgman
2010-05-25 1:05 ` Johan Bockgård
2010-05-24 20:26 ` Stefan Monnier
2010-05-24 21:26 ` Lennart Borgman
2010-05-25 12:59 ` Sean Sieger
2010-05-25 5:10 ` Leo
2010-05-25 7:37 ` Miles Bader
2010-05-25 10:05 ` João Távora
2010-05-25 11:11 ` Lennart Borgman
2010-05-25 13:27 ` João Távora
2010-05-25 11:09 ` Lennart Borgman
2010-05-25 14:04 ` Stefan Monnier
2010-05-25 14:18 ` Lennart Borgman
2010-05-25 15:06 ` Drew Adams
2010-05-25 14:49 ` Drew Adams
2010-05-25 16:33 ` Leo
2010-05-25 8:36 ` Uday S Reddy
2010-05-25 11:48 ` Stephen J. Turnbull
2010-05-25 13:16 ` Uday S Reddy
2010-05-25 14:40 ` Drew Adams
2010-06-05 9:21 ` Uday S Reddy
2010-06-07 20:34 ` Stefan Monnier
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=AANLkTilG5f2wDwGIgsCWAZFt9du5NauX92bguJGU8UON@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=emacs-devel@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 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.