From: "seberino@spawar.navy.mil" <seberino@spawar.navy.mil>
To: help-gnu-emacs@gnu.org
Subject: best to have max width of 79 or 80 in source code?
Date: Sun, 30 Nov 2008 11:10:29 -0800 (PST) [thread overview]
Message-ID: <30ea20ec-ffcb-4ea1-a7d8-14e1caed696f@r36g2000prf.googlegroups.com> (raw)
Many try to keep their source code to a max width of around 80.
Someone recommended 79 for some reason but I can't remember why.
Is it because you need to allow another column for newline?
(I think there is a good reason for 79 but for the life of me I can't
remember
what it is.)
Chris
next reply other threads:[~2008-11-30 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 19:10 seberino [this message]
2008-11-30 20:25 ` best to have max width of 79 or 80 in source code? Drew Adams
2008-11-30 20:50 ` Xah Lee
2008-12-01 1:45 ` seberino
2008-12-01 2:54 ` Xah Lee
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=30ea20ec-ffcb-4ea1-a7d8-14e1caed696f@r36g2000prf.googlegroups.com \
--to=seberino@spawar.navy.mil \
--cc=help-gnu-emacs@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.
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).