unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Marco Antoniotti <marco.antoniotti@unimib.it>
Cc: Stefan Kangas <stefan@marxist.se>,
	Filipp Gunbin <fgunbin@fastmail.fm>,
	47775@debbugs.gnu.org
Subject: bug#47775: First line length and GNU coding standards....
Date: Wed, 05 May 2021 15:20:41 +0200	[thread overview]
Message-ID: <87bl9p5nbq.fsf@gnus.org> (raw)
In-Reply-To: <CAG0Nw2nZS0U7qfRzic45NUZ3P0aq=d6LY4-PThh86ioQ77HU8Q@mail.gmail.com> (Marco Antoniotti's message of "Mon, 19 Apr 2021 16:11:14 +0200")

Marco Antoniotti <marco.antoniotti@unimib.it> writes:

> The issue is "buffer variables" vs "convention of 'name --- description'.
>
> TRT is to "fix" checkdoc to look for the 'name --- description' within the first (10)
> lines, AND/OR to revert to the old convention of having the '-*- ... -*-' line(s) within
> the first 10.
>
> Once that is done, the documentation can be amended accordingly, relaxing the
> mandate that the first line MUST start with ;;; foo --- bar. and no extra update in any
> files will be needed.

If I understand correctly, you want Emacs to recommend the following
style to start .el files:

;;; -*- 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.

This would break a lot of tooling that expects the first line to have
the package name (and description), so that's not a feasible change.

The local variable section is usually put at the end of the file, but
lexical-binding is special, in that it's not "really" a local variable,
but has other effects, and in that we're (at one point in the future)
going to remove all these cookies when we flip the defaults, and then
the first lines will be shorter than 79 characters again.

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-05-05 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 14:46 bug#47775: First line length and GNU coding standards Marco Antoniotti
2021-04-18 16:59 ` 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 [this message]
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=87bl9p5nbq.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=47775@debbugs.gnu.org \
    --cc=fgunbin@fastmail.fm \
    --cc=marco.antoniotti@unimib.it \
    --cc=stefan@marxist.se \
    /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).