From: Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71985@debbugs.gnu.org
Subject: bug#71985: Lexical directives at start of file
Date: Sun, 07 Jul 2024 19:19:41 +0000 [thread overview]
Message-ID: <TYcqrwfgRclGCuwcQ1nZb116Ryyy4PoTSrL8Ack8vko55M8Jy99mZTB_gcxjyoDYmF0ItuIIoYFQk8FVius3qSx1M6aSJDmLguG4-FyzsNs=@protonmail.com> (raw)
In-Reply-To: <86frsl10vx.fsf@gnu.org>
On Sunday, July 7th, 2024 at 7:02 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sun, 07 Jul 2024 18:45:12 +0000
> > From: Heime via "Bug reports for GNU Emacs,
> > the Swiss army knife of text editors" bug-gnu-emacs@gnu.org
> >
> > I was curious whether the -- lexical-binding: t -- directive is effective
> > when there is an arbitrary number of comment characters before it.
>
>
> Why do you need to know this detail?
Because I use ;;; as highlight when using outlines.
> > For instance, in file.el:
> >
> > ;;; file.el -- lexical-binding: t --
> >
> > This is the first line from git-rebase.el in the Magit package:
> >
> > ;;; git-rebase.el --- Edit Git rebase files -- lexical-binding:t --
> >
> > This suggests that some characters can precede the variable list. However,
> > it's unclear if the number of characters can be arbitrary.
>
>
> Above you mention "comment characters". Here you are talking only
> about "characters" in general. I'm confused by what you are asking
> about.
Yes about the starting ;;;. But then I have also seen additional non-directive
descriptions before the -*- lexical-binding:t -*- directive.
As the lexical definition will be around a while, it would be good to know what
would be valid.
> > I couldn't find
> > a clear explanation in either the Emacs or Elisp manuals. The Emacs manual
> > mentions that it can be placed on the second line of a shell script, but
> > doesn't provide much detail on the format. The Elisp manual does not describe
> > the appearance of this directive at all.
>
>
> The above is incorrect. The ELisp manual shows how this line should
> look in the nose "selecting Lisp Dialect". I think that node answers
> your questions.
>
next prev parent reply other threads:[~2024-07-07 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 18:45 bug#71985: Lexical directives at start of file Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-07 19:02 ` Eli Zaretskii
2024-07-07 19:19 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-07-08 2:27 ` Eli Zaretskii
2024-07-08 12:44 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-08 13:21 ` Eli Zaretskii
2024-07-08 13:36 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-08 14:16 ` Eli Zaretskii
2024-09-30 1:43 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='TYcqrwfgRclGCuwcQ1nZb116Ryyy4PoTSrL8Ack8vko55M8Jy99mZTB_gcxjyoDYmF0ItuIIoYFQk8FVius3qSx1M6aSJDmLguG4-FyzsNs=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=71985@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=heimeborgia@protonmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.