From: Matt Swift <swift@alum.mit.edu>
Cc: emacs-devel@gnu.org
Subject: Re: proposed new variable `emacs-lisp-docstring-fill-column'
Date: Sat, 01 Mar 2003 16:32:49 -0500 [thread overview]
Message-ID: <m2ptpakc1q.fsf@beth.swift.xxx> (raw)
In-Reply-To: <200303012056.h21KuFt24965@rum.cs.yale.edu> ("Stefan Monnier"'s message of "Sat, 01 Mar 2003 15:56:15 -0500")
>> "S" == Stefan wrote:
>> I agree the wording below is not a requirement, but it is a
>> recommendation, and I was looking for a way to heed it while still
>> filling code and comments to a more practical, wider length.
S> Why can't they set fill-column in their emacs-lisp-mode-hook ?
They can, but it won't achieve my objective, which is to fill
docstrings to one length, and use another length to fill comments and
for auto-filling. Having context-dependent values for `fill-column'
can't be accomplished in a hook.
S> It looks to me like an unnecessary customization variable.
Of course that is a reasonable opinion, but I think not because the
variable is redundant.
There are other schemes.
One can define an alternative to `lisp-fill-paragraph' and elect that
function in the mode-hook. That is how I have done it at home.
One could avoid adding a customization variable by permitting
`fill-column' to have other forms, such as an alist of contexts and
values. But changing all the code that refers to `fill-column' would
be a big job that really doesn't seem worth it if it's not a widely
useful abstraction.
next prev parent reply other threads:[~2003-03-01 21:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 1:59 proposed new variable `emacs-lisp-docstring-fill-column' Matt Swift
2003-03-01 2:26 ` Richard Stallman
2003-03-01 4:05 ` Matt Swift
2003-03-01 20:38 ` Stefan Monnier
2003-03-01 20:54 ` Matt Swift
2003-03-01 20:56 ` Stefan Monnier
2003-03-01 21:32 ` Matt Swift [this message]
2003-03-02 15:07 ` Richard Stallman
2003-03-02 15:07 ` 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
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=m2ptpakc1q.fsf@beth.swift.xxx \
--to=swift@alum.mit.edu \
--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 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).