From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Trojan Source detection/highlight in Emacs?
Date: Tue, 02 Nov 2021 17:13:14 +0200 [thread overview]
Message-ID: <83r1byk2ut.fsf@gnu.org> (raw)
In-Reply-To: <CANc-5UyhgiZnPGtAOmc6YwEXOpa6iMV+Vu7=G76keeJZyjxQRA@mail.gmail.com> (message from Skip Montanaro on Tue, 2 Nov 2021 10:01:28 -0500)
> From: Skip Montanaro <skip.montanaro@gmail.com>
> Date: Tue, 2 Nov 2021 10:01:28 -0500
> Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
>
> I accept your belief that this will be difficult to handle in Emacs. Maybe lint tools are where the solution lies.
I didn't say I thought it would be hard. I invited motivated
individuals to use the existing infrastructure to detect and flag
such text as part of the usual Emacs display of code.
next prev parent reply other threads:[~2021-11-02 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 22:19 Trojan Source detection/highlight in Emacs? Skip Montanaro
2021-11-01 23:25 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-02 14:09 ` Eli Zaretskii
2021-11-02 14:56 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-02 15:19 ` Eli Zaretskii
2021-11-02 14:14 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-02 14:01 ` Eli Zaretskii
2021-11-02 15:01 ` Skip Montanaro
2021-11-02 15:13 ` Eli Zaretskii [this message]
2021-11-02 15:12 ` Stefan Monnier via Users list for the GNU Emacs text editor
-- strict thread matches above, loose matches on Subject: below --
2021-11-03 8:52 Anders Munch
2021-11-03 13:03 ` Eli Zaretskii
2021-11-03 15:17 Anders Munch
2021-11-03 17:28 ` 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
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=83r1byk2ut.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
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).