From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: chad Newsgroups: gmane.emacs.devel Subject: Re: Bidirectional text and URLs Date: Mon, 1 Dec 2014 00:01:43 -0800 Message-ID: <4B2AE6F8-34AD-46B5-BFE4-B3A72A2EA75D@gmail.com> References: <87zjbbdt0u.fsf@igel.home> <833892aq3m.fsf@gnu.org> <83egskaf6c.fsf@gnu.org> <419C54B5-68C4-4880-B826-33AD30112EAE@gmail.com> <83h9xg81xu.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1417420959 31643 80.91.229.3 (1 Dec 2014 08:02:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 1 Dec 2014 08:02:39 +0000 (UTC) To: Eli Zaretskii , emacs Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 01 09:02:30 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XvLwE-0006eS-65 for ged-emacs-devel@m.gmane.org; Mon, 01 Dec 2014 09:02:30 +0100 Original-Received: from localhost ([::1]:53208 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvLwD-00013D-Qw for ged-emacs-devel@m.gmane.org; Mon, 01 Dec 2014 03:02:29 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57224) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvLvi-0000SX-8J for emacs-devel@gnu.org; Mon, 01 Dec 2014 03:02:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XvLvc-0005oj-Ik for emacs-devel@gnu.org; Mon, 01 Dec 2014 03:01:58 -0500 Original-Received: from mail-pd0-x229.google.com ([2607:f8b0:400e:c02::229]:47282) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvLvW-0005nb-OC; Mon, 01 Dec 2014 03:01:46 -0500 Original-Received: by mail-pd0-f169.google.com with SMTP id fp1so10312653pdb.28 for ; Mon, 01 Dec 2014 00:01:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=gCEJYflsdW+h29dGhKLD3BATfwsX/xYOh/Hrt90RPCY=; b=MosVWxog6Eb9H+xd7qdMOzzAaoNF82XNLSqS0YjfVM28VshoWhi34ZXHM/6kMVg2Vm D5y6IlqS5mwdnW3lkQqs/E6xVNKDEzQROG9ZgtL7NDBbpONZh57Sk439ekbSlw7zHaid Rx3kwXjHCufLM+ZybbXUKkcDQonwHfw3RGXYvVT2lxB9TzL+O6HlSXt+iM6j2Gqz/AR8 ppPgX3BcDIT6zq39KVU0045qKYsuLixqQHFVvtI6MK1YllvU8hU6Uv9nV26m8w5rH4LB +AfQWZML0z3pva6Fe3mGmEIz4COGXRntBeHnhiUmPVOwhGjELDtMEncyNAqsWhQUaWlI 8mqw== X-Received: by 10.66.147.102 with SMTP id tj6mr11205919pab.95.1417420905607; Mon, 01 Dec 2014 00:01:45 -0800 (PST) Original-Received: from [10.0.1.37] (75-165-99-219.tukw.qwest.net. [75.165.99.219]) by mx.google.com with ESMTPSA id d14sm4245919pdj.46.2014.12.01.00.01.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Dec 2014 00:01:45 -0800 (PST) In-Reply-To: <83h9xg81xu.fsf@gnu.org> X-Mailer: Apple Mail (2.1993) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c02::229 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:178569 Archived-At: > On 30 Nov 2014, at 19:49, Eli Zaretskii wrote: >> Given things we're already identifying the URL in text, is it >> possible/easy to check for a different directionality of any part >> of a URL text (including the entire url) compared to the text (not >> whitespace) before and after the URL? > > Yes, but this would only be a sign of trouble if the rest of buffer > text is strictly left to right. And even then, there are legitimate > URLs that have RTL characters, e.g. in Google queries. This is a great point. Does this happen often enough that it would be troublesome to add a warning or prompt about it? ~Chad