unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Subject: Re: ChangeLog conventions: fill-column
Date: Tue, 16 May 2006 16:43:28 +0200	[thread overview]
Message-ID: <m3odxyvxm7.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <v9r72ub1oi.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Tue, 16 May 2006 14:21:17 +0200")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> Hi,
>
> recently some people (Stefan, Kim) reformatted my ChangeLog entries.
> My `fill-column' in ChangeLog buffers if 74 which is the default from
> `change-log-mode'[1].  Am I missing some coding convention for Emacs
> ChangeLog files?

I don't recall when this started, but we now allow max 79 characters
per line in Emacs ChangeLog files (I see a few lines of 80 chars,
but I'm not sure that is really ok).

IMO, we should have a file-local setting to reflect this.

>
> Bye, Reiner.
>
> [1]
>
> ,----[ <f1> f change-log-mode RET ]
> | change-log-mode is an interactive compiled Lisp function in `add-log.el'.
> | (change-log-mode)
> | 
> | Major mode for editing change logs; like Indented Text Mode.
> | Prevents numeric backups and sets `left-margin' to 8 and `fill-column' to 74.
> `----
> -- 
>        ,,,
>       (o o)
> ---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2006-05-16 14:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 12:21 ChangeLog conventions: fill-column Reiner Steib
2006-05-16 14:43 ` Kim F. Storm [this message]
2006-05-16 15:00   ` Michaël Cadilhac
2006-05-23 18:37     ` Michaël Cadilhac
2006-05-23 19:31       ` Michaël Cadilhac
2006-05-23 21:31       ` Robert J. Chassell
2006-05-23 22:46         ` Kim F. Storm
2006-05-24  0:24           ` Robert J. Chassell
2006-05-24  5:50       ` Richard Stallman
2006-05-24  9:13         ` Kim F. Storm
2006-05-25  0:36           ` Richard Stallman
2006-05-16 15:18   ` Reiner Steib
2006-05-17  2:10 ` Miles Bader

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=m3odxyvxm7.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    /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).