From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Source code formatting: line length limit?
Date: Sun, 26 Jan 2003 21:32:27 -0500 [thread overview]
Message-ID: <E18cz4V-0001sS-00@fencepost.gnu.org> (raw)
In-Reply-To: <m18cmai-000IeGC@localhost> (bob@rattlesnake.com)
I think that program code should usually have less than 40 characters
of real text on a line. But that is not counting the line's
indentation. Sometimes it is hard to avoid getting out towards
column 80.
next prev parent reply other threads:[~2003-01-27 2:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 12:39 Source code formatting: line length limit? Kai Großjohann
2003-01-25 13:26 ` Robert J. Chassell
2003-01-26 1:21 ` Stefan Monnier
2003-01-26 13:12 ` Robert J. Chassell
2003-01-27 2:32 ` Richard Stallman [this message]
2003-01-27 14:14 ` Stefan Monnier
2003-01-26 14:48 ` Kai Großjohann
2003-01-26 18:49 ` Robert J. Chassell
2003-01-27 2:32 ` Richard Stallman
2003-01-27 13:01 ` 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
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=E18cz4V-0001sS-00@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).