all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Source code formatting: line length limit?
Date: Mon, 27 Jan 2003 08:01:08 -0500	[thread overview]
Message-ID: <200301271301.h0RD18X30158@rum.cs.yale.edu> (raw)
In-Reply-To: 84lm187ysa.fsf@lucy.is.informatik.uni-duisburg.de

> I think both of you implicitly imply that text *over* 80 columns is
> bad and should be avoided.
> 
> Could you make this explicit?

Yes, I think one or two lines slightly over 80 chars are OK as long as
there's a good justification for them and as long as they're not all
next to each other.

> To illustrate my problem:  I have just reformatted source code from
> something like 120 columns to something below 80.  Should I revert
> this change, making the lines longer again?  Some of the changes
> produced rather awful-looking code because the code is nested very
> deeply.

If it's nested too deeply, it's sometimes difficult to place
LF such that the indentation looks good and the code readable,
but most of the time, it's just difficult to read no matter what
and should thus be split out into a separate function.

120 is way over what I consider as acceptable: it's basically unreadable.


	Stefan

      parent reply	other threads:[~2003-01-27 13:01 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
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 [this message]

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=200301271301.h0RD18X30158@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.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 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.