unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Docstring line length
Date: Wed, 21 Dec 2005 18:10:34 -0500	[thread overview]
Message-ID: <E1EpD6Q-0002gH-BQ@fencepost.gnu.org> (raw)
In-Reply-To: <877j9ybef4.fsf@olgas.newt.com> (message from Bill Wohler on Wed,  21 Dec 2005 08:30:55 -0800)

    > I'm sure most people do not do as I do, but I'm not sure that most people
    > use fixed 80-char frames. Do we have any user data to go on?

    Some people say that character-width standards are pretty much
    obsolete these days. I disagree.

I am with you on this--and my mind is firmly made up.
We will continue with the 80-column default, and continue
designing Emacs displays to work with it.

I'm not against making some displays adapt to other widths,
when someone wants to implement that, assuming the code is clean.
But let's not further consider any larger change.

  parent reply	other threads:[~2005-12-21 23:10 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-20 21:19 Docstring line length Bill Wohler
2005-12-20 23:32 ` Luc Teirlinck
2005-12-20 23:59   ` Drew Adams
2005-12-21  0:00     ` Luc Teirlinck
2005-12-21  0:05     ` Luc Teirlinck
2005-12-21  0:15       ` Drew Adams
2005-12-21  0:13     ` Luc Teirlinck
2005-12-21  0:20       ` Drew Adams
2005-12-21  0:54         ` Luc Teirlinck
2005-12-21  1:37           ` Drew Adams
2005-12-21  7:21             ` Henrik Enberg
2005-12-21 18:52             ` Richard M. Stallman
2005-12-21 20:24               ` Drew Adams
2005-12-21 21:44                 ` Lennart Borgman
2005-12-22  5:46                   ` Richard M. Stallman
2005-12-22 17:00                     ` Legal papers for Emacs contributions (was: Re: Docstring line length) Giorgos Keramidas
2005-12-22 22:21                       ` Richard M. Stallman
2005-12-23  2:13                         ` Giorgos Keramidas
2005-12-23  0:12                       ` Legal papers for Emacs contributions David Kastrup
2005-12-23  2:15                         ` Giorgos Keramidas
2005-12-24  2:36                         ` Richard M. Stallman
2005-12-22 20:43                   ` Docstring line length Juri Linkov
2005-12-22 21:15                     ` Lennart Borgman
2005-12-22 21:57                       ` Juri Linkov
2005-12-22 22:27                         ` link appearance (again) (was: RE: Docstring line length) Drew Adams
2005-12-22  5:47                 ` Docstring line length Richard M. Stallman
2005-12-21  3:12           ` Ken Raeburn
2005-12-21 18:51             ` Richard M. Stallman
2005-12-21  4:54           ` Johan Bockgård
2005-12-21  0:59         ` Luc Teirlinck
2005-12-21  1:06           ` Luc Teirlinck
2005-12-21 16:30         ` Bill Wohler
2005-12-21 18:32           ` Drew Adams
2005-12-21 19:18           ` Stefan Monnier
2005-12-21 19:57             ` David Kastrup
2005-12-21 23:10           ` Richard M. Stallman [this message]
2005-12-21  5:30 ` Richard M. 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=E1EpD6Q-0002gH-BQ@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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).