all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xah Lee <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: best to have max width of 79 or 80 in source code?
Date: Sun, 30 Nov 2008 12:50:40 -0800 (PST)	[thread overview]
Message-ID: <cc37f594-d29c-4676-9761-c70caf1d8154@r37g2000prr.googlegroups.com> (raw)
In-Reply-To: 30ea20ec-ffcb-4ea1-a7d8-14e1caed696f@r36g2000prf.googlegroups.com

On Nov 30, 11:10 am, "seber...@spawar.navy.mil"
<seber...@spawar.navy.mil> wrote:
> 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

in my opinion, hard wrappnig lines or in general any manual code
formatting is a major damage in computing, to the degree that
influenced bad tools and language design which forces humans to think
and do what dumb machines can easily automate. The line wrapping
convention largely spurred the perpetual time wasted on arguing about
code formatting and tools about it.

See:

• The Harm of Hard-wrapping Lines
  http://xahlee.org/UnixResource_dir/writ/hard-wrap.html

• A Simple Lisp Code Formatter
  http://xahlee.org/emacs/lisp_formatter.html

• A Text Editor Feature: Extend Selection By Semantic Unit
  http://xahlee.org/emacs/syntax_tree_walk.html

  Xah
∑ http://xahlee.org/

  parent reply	other threads:[~2008-11-30 20:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-30 19:10 best to have max width of 79 or 80 in source code? seberino
2008-11-30 20:25 ` Drew Adams
2008-11-30 20:50 ` Xah Lee [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cc37f594-d29c-4676-9761-c70caf1d8154@r37g2000prr.googlegroups.com \
    --to=xahlee@gmail.com \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.