From: Marco Antoniotti <marco.antoniotti@unimib.it>
To: 47775@debbugs.gnu.org
Subject: bug#47775: First line length and GNU coding standards....
Date: Wed, 14 Apr 2021 16:46:09 +0200 [thread overview]
Message-ID: <CAG0Nw2=7Vmn8kWmkDD+Pc9LWLymZyKiF1gda7PHN__OyqzTusg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]
Hi
Many years ago we had 80 columns and that was a GOOD THING!
It is such a good thing that the GNU Coding Standards (and not only them),
unless I remember incorrectly, ask for 80 columns of code.
Also many years ago, and on this I may be wrong, it was also said that the
-*- Mode: ... -*-
line could appear within the first 10 (am I remembering right?) lines of a
file.
Now, in
https://www.gnu.org/software/emacs/manual/html_node/elisp/Library-Headers.html
it is said that the FIRST line of a elisp file must start like this:
;;; foo.el --- Support for the Foo programming language -*-
lexical-binding: t; -*-
especially if you want lexical binding, which is NOT turned on if the
setting is NOT in the first line.
Now, this is not exactly a bug, but for many years (I am an old guy), I
wrote code with a separate header line containing only Emacs local buffer
customizations. And the Lisp-Headers "suggestion" quickly runs afoul of
the 80 column coding standard. Moreover, things like checkdoc (and
therefore flycheck) become a bit annoying if you do not follow suit.
Bottom line, this is just a bit of a rant, but I really like my (and, I
believe, many other old geezers') style of having something like
;;; -*- Mode: Emacs-Lisp; lexical-binding: t; some-var-with-a-long-name: t
-*-
;;; foo.el --- The foo pkg, which also happens to have description 79 col
long.
I know it's 2021, but I still like the 80 columns.
Anything that can be done about it?
All the best
Marco
--
Marco Antoniotti, Associate Professor tel. +39 - 02 64 48 79 01
DISCo, Università Milano Bicocca U14 2043 http://dcb.disco.unimib.it
Viale Sarca 336
I-20126 Milan (MI) ITALY
[-- Attachment #2: Type: text/html, Size: 6528 bytes --]
next reply other threads:[~2021-04-14 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 14:46 Marco Antoniotti [this message]
2021-04-18 16:59 ` bug#47775: First line length and GNU coding standards Stefan Kangas
2021-04-19 12:18 ` Filipp Gunbin
2021-04-19 12:32 ` Marco Antoniotti
2021-04-19 13:18 ` Stefan Kangas
2021-04-19 13:18 ` Stefan Kangas
2021-04-19 14:11 ` Marco Antoniotti
2021-05-05 13:20 ` Lars Ingebrigtsen
2021-05-05 13:40 ` Marco Antoniotti
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='CAG0Nw2=7Vmn8kWmkDD+Pc9LWLymZyKiF1gda7PHN__OyqzTusg@mail.gmail.com' \
--to=marco.antoniotti@unimib.it \
--cc=47775@debbugs.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).