unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: ChangeLog fontifications
Date: Sun, 16 May 2004 18:52:50 +0200	[thread overview]
Message-ID: <2914-Sun16May2004185250+0300-eliz@gnu.org> (raw)
In-Reply-To: <200405161714.17062.bruno@clisp.org> (message from Bruno Haible on Sun, 16 May 2004 17:14:16 +0200)

> From: Bruno Haible <bruno@clisp.org>
> Date: Sun, 16 May 2004 17:14:16 +0200
> 
> Yes, all GNU projects I work on use the style with a 15-year tradition.

What projects are those?

> After people have used to write things in a certain style for 10 years -
> following the example that was given by you, by GCC, glibc and other
> projects - it will be hard to explain what in this style is "wrong".

Actually, I found it rather easy to explain, in those cases where I
did.

And many code contributors write misformatted ChangeLog entries even
according to old conventions you are accustomed to.  So if a project
cares about its log formatting, maintainers typically need to watch
out for badly formatted entries anyway.  So it's not like the old
conventions are somehow automatically followed, except by those few
who are accustomed to them.

> I add that the new Emacs style is bad because it doesn't allow a newline
> to be inserted anywhere, i.e. it doesn't treat newline and space conceptually
> the same.

With suggested changes that will allow log entries to be correctly
formatted when they are refilled, this problem will go away, I think.

> What are the advantages/benefits of the new Emacs style that should
> convince me and others to use it?

The advantages/benefits were already mentioned in this thread: the new
style makes it easier for line-oriented programs to find the names of
changed functions/macros.

  reply	other threads:[~2004-05-16 16:52 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 18:50 ChangeLog fontifications Bruno Haible
2004-05-13 19:26 ` Miles Bader
2004-05-13 19:43   ` Bruno Haible
2004-05-13 20:38     ` Miles Bader
2004-05-13 21:12       ` Sam Steingold
2004-05-13 21:15         ` Miles Bader
2004-05-13 20:13 ` Alan Shutko
2004-05-13 20:42   ` Miles Bader
2004-05-13 21:37   ` Werner LEMBERG
2004-05-13 21:56     ` Miles Bader
2004-05-13 22:25       ` Stefan Monnier
2004-05-14  3:00       ` Karl Eichwalder
2004-05-14  4:24         ` Miles Bader
2004-05-14 13:56         ` Robert J. Chassell
2004-05-14  6:24       ` Werner LEMBERG
2004-05-14  6:36         ` Werner LEMBERG
2004-05-14 15:31       ` Sam Steingold
2004-05-14 21:02 ` Richard Stallman
2004-05-16 15:14   ` Bruno Haible
2004-05-16 16:52     ` Eli Zaretskii [this message]
2004-05-16 20:52       ` Miles Bader
2004-05-17 22:57     ` Richard Stallman
2004-05-18  5:02       ` Karl Eichwalder
2004-05-19  1:32         ` Miles Bader
2004-05-19 13:08           ` Sam Steingold
2004-05-19 13:22             ` Miles Bader
2004-05-19 14:59               ` Stefan Monnier
2004-05-19 13:45         ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2004-05-11 17:15 Sam Steingold
2004-05-11 18:03 ` Juri Linkov
2004-05-11 22:54   ` Sam Steingold
2004-05-11 23:02     ` Miles Bader
2004-05-12  8:33       ` Werner LEMBERG
2004-05-12 10:10         ` Miles Bader
2004-05-12 12:36           ` Eli Zaretskii
2004-05-13 17:22           ` Sam Steingold
2004-05-14 21:01             ` Richard Stallman
2004-05-11 23:26     ` Stefan Monnier
2004-05-12  0:08       ` Juri Linkov
2004-05-12  5:48         ` Eli Zaretskii
2004-05-12 12:55           ` 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=2914-Sun16May2004185250+0300-eliz@gnu.org \
    --to=eliz@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).