From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: bidi-string-strip-control-characters
Date: Thu, 20 Jan 2022 15:02:38 +0200 [thread overview]
Message-ID: <83r192pnkh.fsf@gnu.org> (raw)
In-Reply-To: <87mtjq1sn7.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 20 Jan 2022 13:46:52 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: luangruo@yahoo.com, emacs-devel@gnu.org
> Date: Thu, 20 Jan 2022 13:46:52 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > But what are we going to do with the function in the Subject? Is it
> > still useful enough to have it, if we make that change?
>
> We're still using it in textsec-link-suspicious-p...
How about if, instead of filtering out these controls, the function
would replace them with their printed representation, like \u200e?
Removing them might leave the user wondering what and where is wrong
with the original text.
next prev parent reply other threads:[~2022-01-20 13:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 9:23 bidi-string-strip-control-characters Eli Zaretskii
2022-01-20 9:29 ` bidi-string-strip-control-characters Lars Ingebrigtsen
2022-01-20 10:14 ` bidi-string-strip-control-characters Eli Zaretskii
2022-01-20 12:47 ` bidi-string-strip-control-characters Lars Ingebrigtsen
2022-01-20 11:04 ` bidi-string-strip-control-characters Po Lu
2022-01-20 11:19 ` bidi-string-strip-control-characters Eli Zaretskii
2022-01-20 11:21 ` bidi-string-strip-control-characters Po Lu
2022-01-20 11:23 ` bidi-string-strip-control-characters Lars Ingebrigtsen
2022-01-20 11:33 ` bidi-string-strip-control-characters Eli Zaretskii
2022-01-20 12:46 ` bidi-string-strip-control-characters Lars Ingebrigtsen
2022-01-20 13:02 ` Eli Zaretskii [this message]
2022-01-20 13:36 ` bidi-string-strip-control-characters Lars Ingebrigtsen
2022-01-20 16:51 ` bidi-string-strip-control-characters Eli Zaretskii
2022-01-21 9:18 ` bidi-string-strip-control-characters Lars Ingebrigtsen
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=83r192pnkh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
/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.