From: Marco Antoniotti <marco.antoniotti@unimib.it>
To: Stefan Kangas <stefan@marxist.se>
Cc: Filipp Gunbin <fgunbin@fastmail.fm>, 47775@debbugs.gnu.org
Subject: bug#47775: First line length and GNU coding standards....
Date: Mon, 19 Apr 2021 16:11:14 +0200 [thread overview]
Message-ID: <CAG0Nw2nZS0U7qfRzic45NUZ3P0aq=d6LY4-PThh86ioQ77HU8Q@mail.gmail.com> (raw)
In-Reply-To: <CADwFkm=Afmy=iRM3CkGVATimUuu5d6t927i5E4WuRjNefTsE0g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
Hi
let me reiterate. The issue is *not *the lexical-binding t or nil.
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.
All the best
MA
On Mon, Apr 19, 2021 at 3:18 PM Stefan Kangas <stefan@marxist.se> wrote:
> Filipp Gunbin <fgunbin@fastmail.fm> writes:
>
> >> Within N years, we will hopefully flip the switch and enable
> >> lexical-binding by default, thereby (mostly) eliminating the problem.
> >
> > Will that be really possible? What about code in the wild?
>
> It's not an immediate proposal obviously, but yes after a long-ish
> deprecation period of `lexical-binding:nil' many of us hope that we will
> be able to flip the switch.
>
--
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
http://cdac2021.lakecomoschool.org
I-20126 Milan (MI) ITALY
[-- Attachment #2: Type: text/html, Size: 6436 bytes --]
next prev parent reply other threads:[~2021-04-19 14:11 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 [this message]
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='CAG0Nw2nZS0U7qfRzic45NUZ3P0aq=d6LY4-PThh86ioQ77HU8Q@mail.gmail.com' \
--to=marco.antoniotti@unimib.it \
--cc=47775@debbugs.gnu.org \
--cc=fgunbin@fastmail.fm \
--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).