From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: larsi@gnus.org, dgutov@yandex.ru, 47488@debbugs.gnu.org, rrt@sc3d.org
Subject: bug#47488: Treatment of # in js.el
Date: Wed, 12 May 2021 17:49:13 +0300 [thread overview]
Message-ID: <83pmxw2eja.fsf@gnu.org> (raw)
In-Reply-To: <87h7j8nhim.fsf@igel.home> (message from Andreas Schwab on Wed, 12 May 2021 16:39:13 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 47488@debbugs.gnu.org,
> dgutov@yandex.ru, rrt@sc3d.org
> Date: Wed, 12 May 2021 16:39:13 +0200
>
> On Mai 12 2021, Eli Zaretskii wrote:
>
> > 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.
>
> Not by gcc. It uses # LINE FILE FLAGS for that purpose. The gcc
> preprocessor doesn't know anything about #file.
You are right, sorry. I confused this with #line, which can
optionally state the file.
next prev parent reply other threads:[~2021-05-12 14:49 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
2021-05-12 13:56 ` Lars Ingebrigtsen
2021-05-12 14:39 ` Andreas Schwab
2021-05-12 14:49 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pmxw2eja.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47488@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=larsi@gnus.org \
--cc=rrt@sc3d.org \
--cc=schwab@linux-m68k.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 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.