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: Mon, 08 Jul 2024 12:44:26 +0000 [thread overview]
Message-ID: <Q3GFRCc39POk4kvMi4Y0UpS6TyvWBNYP6lBN7Kp284i0hsZgcZ3EuaTVccCYRu-n_wuIbuTy1imXyETxtNV1ks1KIdIQmxeuyEu46P961nE=@protonmail.com> (raw)
In-Reply-To: <86ed841uux.fsf@gnu.org>
On Monday, July 8th, 2024 at 2:27 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sun, 07 Jul 2024 19:19:41 +0000
> > From: Heime heimeborgia@protonmail.com
> > Cc: 71985@debbugs.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.
>
>
> Then the ELisp manual provides this information, I think.
It could be there. But, where is it ?
next prev parent reply other threads:[~2024-07-08 12:44 UTC|newest]
Thread overview: 8+ 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
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 [this message]
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
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='Q3GFRCc39POk4kvMi4Y0UpS6TyvWBNYP6lBN7Kp284i0hsZgcZ3EuaTVccCYRu-n_wuIbuTy1imXyETxtNV1ks1KIdIQmxeuyEu46P961nE=@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.