From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 47488@debbugs.gnu.org, dgutov@yandex.ru, rrt@sc3d.org
Subject: bug#47488: Treatment of # in js.el
Date: Wed, 12 May 2021 16:53:21 +0300 [thread overview]
Message-ID: <83sg2s2h4e.fsf@gnu.org> (raw)
In-Reply-To: <87sg2sjcxa.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 12 May 2021 15:32:01 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 12 May 2021 15:32:01 +0200
> Cc: 47488@debbugs.gnu.org, Reuben Thomas <rrt@sc3d.org>
>
> I've never heard of the #file directive, but:
>
> ;; `cpp-font-lock-keywords-source-directives' is calculated from:
> ;;
> ;; (regexp-opt
> ;; '("define" "elif" "else" "endif" "error" "file" "if" "ifdef"
> ;; "ifndef" "import" "include" "line" "pragma" "undef" "warning"))
>
> I spent 30 seconds googling, and I could find no list of directive that
> includes #file, so... Bug #warning is used, and so is #line, so perhaps
> it's an old thing?
The #file directive is emitted by the preprocessor, so that later
compiling the preprocessed source would yield the correct source line
numbers. Try preprocessing some .c file with "gcc -E" and you will
see these directives in the output.
next prev parent reply other threads:[~2021-05-12 13:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 21:28 bug#47488: Treatment of # in js.el Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-30 0:50 ` Dmitry Gutov
2021-05-08 12:43 ` Lars Ingebrigtsen
2021-05-09 11:18 ` Dmitry Gutov
2021-05-09 11:31 ` Dmitry Gutov
2021-05-10 8:29 ` Lars Ingebrigtsen
2021-05-10 12:12 ` Dmitry Gutov
2021-05-10 8:34 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-10 12:14 ` Dmitry Gutov
2021-05-11 12:21 ` Lars Ingebrigtsen
2021-05-11 12:45 ` Dmitry Gutov
2021-05-12 13:32 ` Lars Ingebrigtsen
2021-05-12 13:53 ` Eli Zaretskii [this message]
2021-05-12 13:56 ` Lars Ingebrigtsen
2021-05-12 14:39 ` Andreas Schwab
2021-05-12 14:49 ` Eli Zaretskii
2021-05-12 14:56 ` Dmitry Gutov
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=83sg2s2h4e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47488@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=larsi@gnus.org \
--cc=rrt@sc3d.org \
/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).