unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 15:54:56 -0500	[thread overview]
Message-ID: <m2wujikdsv.fsf@beth.swift.xxx> (raw)
In-Reply-To: <200303012038.h21KcGr24763@rum.cs.yale.edu> ("Stefan Monnier"'s message of "Sat, 01 Mar 2003 15:38:16 -0500")

>> "S" == Stefan wrote:

    S> I don't like this change because docstrings shouldn't be
    S> limted to 65 chars.  The doc only says that they should
    S> fit within 80 columns.  Only the first line should be shorter.

Is this an objection to the variable or to the default value?  If the
default value were t instead of 65, default behavior of Emacs would
not change.  Users who do like the feature could enable it with
customization.

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.

>From (elisp)Documentation Tips:

   * Format the documentation string so that it fits in an Emacs window
     on an 80-column screen.  It is a good idea for most lines to be no
                              ^^^^^^...
     wider than 60 characters.  The first line should not be wider than
     67 characters or it will look bad in the output of `apropos'.

  reply	other threads:[~2003-03-01 20:54 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 [this message]
2003-03-01 20:56         ` Stefan Monnier
2003-03-01 21:32           ` Matt Swift
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=m2wujikdsv.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).