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: Mon, 01 Nov 2021 19:25:55 -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="7886"; 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:3JLKpy9AIrNWreI7swFnEdYUrpw= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Nov 02 00:35:14 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 1mhgpc-0001oF-Qr for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 02 Nov 2021 00:35:12 +0100 Original-Received: from localhost ([::1]:47110 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mhgpb-0005Ul-3B for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 01 Nov 2021 19:35:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42036) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mhgh0-0004XA-0m for help-gnu-emacs@gnu.org; Mon, 01 Nov 2021 19:26:18 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:48502) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mhggj-0003Jn-M6 for help-gnu-emacs@gnu.org; Mon, 01 Nov 2021 19:26:17 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1mhggh-0000mm-KH for help-gnu-emacs@gnu.org; Tue, 02 Nov 2021 00:25:59 +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:134303 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 ;-) Stefan