unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Trojan Source detection/highlight in Emacs?
Date: Wed, 03 Nov 2021 15:03:18 +0200	[thread overview]
Message-ID: <83mtmlie7d.fsf@gnu.org> (raw)
In-Reply-To: <HE1PR0502MB3004DAE47FE22325DDDB6B67B48C9@HE1PR0502MB3004.eurprd05.prod.outlook.com> (message from Anders Munch on Wed, 3 Nov 2021 08:52:52 +0000)

> From: Anders Munch <ajm@flonidan.dk>
> Date: Wed, 3 Nov 2021 08:52:52 +0000
> Accept-Language: en-US
> 
> Eli Zaretskii wrote:
> > Stefan Monnier wrote: 
> >> A simple and straightforward way to do that is to highlight any 
> >> non-ASCII char, and to render all the "non printing" chars (such as 
> >> RIGHT-TO-LEFT OVERRIDE) as tofu or something like that (otherwise, the 
> >> highlighting applied to it wouldn't be visible).
> >
> > That's already available, no changes needed.
> 
> Can we get a recipe, please?

Customize the variable glyphless-char-display-control.

> I tried customising bidi-paragraph-direction, setting it to 'left-to-right, but I'm not seeing any effect, despite the docstring saying it /forces/ directionality.

The doc string says it forces the directionality of the paragraph.  If
you don't already know what that means, I suggest to read the
"Bidirectional Editing" node in the Emacs manual, it should explain
that.

> I guess it just sets a default, and explicit bidi control characters take precedence.

Not exactly, but something like that.

The paragraph direction is not relevant to this issue, since in
prog-mode descendants we already set the value to left-to-right.



  reply	other threads:[~2021-11-03 13:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03  8:52 Trojan Source detection/highlight in Emacs? Anders Munch
2021-11-03 13:03 ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-03 15:17 Anders Munch
2021-11-03 17:28 ` Eli Zaretskii
2021-11-01 22:19 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
2021-11-02 15:12   ` Stefan Monnier via Users list for the GNU Emacs text editor

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=83mtmlie7d.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).