From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier via Users list for the GNU Emacs text editor Newsgroups: gmane.emacs.help Subject: Re: Trojan Source detection/highlight in Emacs? Date: Tue, 02 Nov 2021 10:14:01 -0400 Message-ID: References: Reply-To: Stefan Monnier Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27075"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:1EC6c5MIhXd24mrlOhK4oNKR85g= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Nov 02 15:41:49 2021 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mhuyz-0006sz-5h for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 02 Nov 2021 15:41:49 +0100 Original-Received: from localhost ([::1]:35152 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mhuyx-0003bH-OZ for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 02 Nov 2021 10:41:47 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43032) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mhuYD-0003sv-Ud for help-gnu-emacs@gnu.org; Tue, 02 Nov 2021 10:14:09 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:42532) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mhuYB-0005P9-Sr for help-gnu-emacs@gnu.org; Tue, 02 Nov 2021 10:14:09 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1mhuY9-000AXv-Rt for help-gnu-emacs@gnu.org; Tue, 02 Nov 2021 15:14:05 +0100 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:134310 Archived-At: >> if access_level != "user{U+202E} {U+2066}// Check if admin{U+2069} >> {U+2066}" { >> >> ...would be rendered by bidirectional-aware tools as: >> >> if access_level != "user" { // Check if admin >> >> This would give the reader the mistaken impression that the program is >> comparing admin_level with the value "user". > > Clearly, Eli will know better, but I suspect that we may be able to > avoid most of those issues by (conceptually) treating comment delimiters > as bidi barriers. Of course, that leaves open the question of what > I mean by "bidi barrier" and of how to implement it ;-) Tho, actually, the problem is more pronounced since bidi can also be used within a string (as shown above already) as well as within identifiers (tho language may opt to disallow them there). So my suggestion above would have to be extended to treat string delimiters as barriers, and similarly for "identifier delimiters" (i.e. whitespace, infix operators/punctuation, ...) tho not when within comments or strings. And of course, the specifics are all language-dependent. Clearly non-trivial. Stefan