From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: lm-verify, long copyright line
Date: Fri, 23 Jun 2017 10:13:45 -0700 [thread overview]
Message-ID: <ec50ca6b-38d9-6366-8656-b95b2639ef18@cs.ucla.edu> (raw)
In-Reply-To: <jwvr2yar82v.fsf-monnier+gmane.emacs.devel@gnu.org>
On 06/23/2017 09:19 AM, Stefan Monnier wrote:
> Because all the lm-* thingies use leading spaces to distinguish line
> continuations (along the same lines as what RFC822 does).
> It doesn't look weird to me at all.
It's readable either way; all I was saying is that it's weird for
lm-verify to insist on extra indentation for the second line of a
copyright notice. The extra indentation isn't that common a style. For
example, src/emacs.c doesn't use it, nor does src/lisp.h, or
lisp/subr.el, or lots of other Emacs source files. So why insist on the
style for lisp/mh-e/mh-e.el?
next prev parent reply other threads:[~2017-06-23 17:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 22:51 lm-verify, long copyright line Mike Kupfer
2017-06-22 23:26 ` Paul Eggert
2017-06-22 23:57 ` Mike Kupfer
2017-06-23 0:07 ` Paul Eggert
2017-06-23 0:28 ` Mike Kupfer
2017-06-23 4:18 ` Paul Eggert
2017-06-23 16:19 ` Stefan Monnier
2017-06-23 17:13 ` Paul Eggert [this message]
2017-06-23 17:59 ` Glenn Morris
2017-06-23 18:33 ` Paul Eggert
2017-06-24 22:16 ` Mike Kupfer
2017-06-25 2:01 ` Paul Eggert
2017-06-25 2:59 ` Mike Kupfer
2017-06-25 15:10 ` Stefan Monnier
2017-06-25 16:59 ` Mike Kupfer
2017-06-25 20:45 ` Paul Eggert
2017-06-25 20:53 ` Mike Kupfer
2017-06-25 21:05 ` Paul Eggert
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=ec50ca6b-38d9-6366-8656-b95b2639ef18@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).