From: Christopher Dimech <dimech@gmx.com>
To: monnier@iro.umontreal.ca
Cc: help-gnu-emacs@gnu.org
Subject: Re: Extending emacs convention for first line
Date: Thu, 20 Oct 2022 19:11:32 +0200 [thread overview]
Message-ID: <trinity-ff31bc1a-c10e-4a58-85e1-73be8b8a384d-1666285892179@3c-app-mailcom-bs08> (raw)
In-Reply-To: <jwva65tdimx.fsf-monnier+emacs@gnu.org>
> Sent: Tuesday, October 18, 2022 at 1:33 PM
> From: "Stefan Monnier via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Extending emacs convention for first line
>
> Christopher Dimech [2022-10-17 21:40:14] wrote:
> > Emacs convention states that the format for the first line is
> > ;;; filename --- description -*- lexical-binding: t; -*-
> >
> > Because at the times one does notice longer filenames and descriptions,
> > it would be favorable if the convention would be extended to handle longer
> > filenames and descriptions.
> >
> > For instance, using ;;; to distinguish, with "lexical-binding" still written first.
> >
> > ;;; -*- lexical-binding: t; -*-
> >
> > ;;; filename
> >
> > ;;; description
> >
> > Or some other way that would work nicely.
>
> I don't have a strong opinion on this, but I'll note that I hope we can
> get rid of the `-*- lexical-binding: t -*-` cookie in the not too
> distant future.
>
> I think we're slowly working our way up to the point where we can change
> the default to t such that the cookie will be needed only (in the form
> `-*- lexical-binding: nil -*-`) for those files still using the old
> dynbound dialect of ELisp.
>
>
> Stefan
The suggestion is more focused on allowing descriptions longer
than a single line. And which would avoid us long lines.
next prev parent reply other threads:[~2022-10-20 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 19:40 Extending emacs convention for first line Christopher Dimech
2022-10-18 1:33 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-18 1:53 ` Emanuel Berg
2022-10-20 17:11 ` Christopher Dimech [this message]
2022-10-20 18:06 ` Stefan Monnier
2022-10-20 20:11 ` Christopher Dimech
2022-10-20 22:57 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-21 17:34 ` Christopher Dimech
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=trinity-ff31bc1a-c10e-4a58-85e1-73be8b8a384d-1666285892179@3c-app-mailcom-bs08 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@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.
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).