Date: Mon, 23 Jul 2012 19:56:39 +0530 From: ashish@FreeBSD.org (Ashish SHUKLA) To: Jan Henrik Sylvester <me@janh.de> Cc: ports-list freebsd <freebsd-ports@freebsd.org> Subject: Re: [CFT] editors/emacs to 24.1 Message-ID: <867gtumu3k.fsf@chateau.d.if> References: <86vchenbsx.fsf@chateau.d.if> <500D3652.2000603@janh.de> <86r4s2n1uk.fsf@chateau.d.if> <500D419B.6070200@janh.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 23 Jul 2012 14:20:43 +0200, Jan Henrik Sylvester <me@janh.de> said: > On 07/23/2012 13:39, Ashish SHUKLA wrote: >> On Mon, 23 Jul 2012 13:32:34 +0200, Jan Henrik Sylvester <me@janh.de> sa= id: >>> Arabic, which is finally displayed from right-to-left, works in >>> windowed mode, but for me, it does not work correctly with "-nw": >>> While it is displayed correctly in a LANG=3Den_US.UTF-8 Konsole (KDE >>> terminal), the order of the letters is changed just by moving the >>> cursor through Arabic text. I do not think this is a problem with the >>> port, but either with my setup or with emacs-24.1 in general. >>=20 >> Did you try other terminal, like mrxvt ? I think it's problem with termi= nal, >> and not Emacs, but I might be wrong. > mrxvt and mrxvt-devel both do not display utf-8 at all. I tried > rxvt-unicode: While only some of the Arabic characters where displayed > correctly, the cursor was moving properly and it did not reorder the > characters. Emacs and the Emacs port seem to be fine. Finding and > setting up a terminal that works properly with Arabic seems to be the > problem. Sorry, I was talking about mlterm[1]. > My curiosity ends here. I cannot even read Arabic myself. I just > happen to know someone, who would like to use Arabic in Emacs with > auctex, but that person does not ever use "-nw". >>> For my use, I would be happy, if emacs-24.1 was the default in ports, s= oon. >>=20 >> Sure, it will be. I'd some personal issues over past weeks which are not >> rectified so less slacking, more hacking. s/not/now/ > Sorry, if my statement sounded demanding. It was not meant to be at > all. I just wanted to summarize that the issues I found are not with > the port, I consider them extremely minor, and I will use emacs-24.1 > from now on. I think my typo confused it, sorry. I'll commit it by this weekend hopefully. Also any issues with Emacs, should be reported to emacs-devel[2] for better resolution, unless it's something FreeBSD port specific. References: [1] http://mlterm.sourceforge.net/ [2] https://lists.gnu.org/mailman/listinfo/emacs-devel/ Thanks =2D-=20 Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 Sent from my Emacs --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQIcBAEBCgAGBQJQDV8fAAoJEMdGz6nnT6Sw1Z8P/RbUA1hI2wzxd51SMRlZRgyP 8UiVPmMv6sOBmAx+YNaTg+2TZuTn8gmgDiSMC3RJI7MEEToPTeXQUtBdJY8hAYMK 10mhT9kTcrj3oC/tZ4Ass0D/Hmm3MO3HikJNjbOHW/eBBWAhaC0eXSY/LD3evdzR DmNMZTh+i3vk+8fy9372RVN8ieaWB+SHoZBGKIXYZ4WjXH93HVCgYhq1zj0dlHhs s6zUtbW0Ah4uHogEQAbBEEb4QjUiPnTr2OsJ1ffSLMKo+NeL1clmlEYXi2bjAYg4 hCYdIPhrLDt94d1MTFAdo37cgCBt2i5cgWtXUJzjNrY0g+DQJwN8FBxpbx77JFhx LFwJwGC0E4CXVYp5G0/0HFwRtMNvC7ad74dbvGC9E0fOFVVZmD7qC6BLNbyn1y1P UeWfbTmeeqrGaUjyiy0AQI9nqpxbhft1njj7lkQba4A43Or2sXH9yBfsCif7sg6m JhjQ/Yd8NcWBMcRklcAaWbMWA2kO42HVGGkjSO+Pkc6spJSesqjUx01mZwBA0slx Klahv1wzdzfxr8xbfhHE8ecZrH6waoUwE8sWssLN9faNk5pVqBy41hDW/VkOzDnq OI2+yOsIaCFuhZgvHiioKzgI+Ru/k94TXJ1Mr5Q9a/epguw40htr2lLxCKZ5Vhhn HnomNaJpdoKmY/wYpCNt =SEUb -----END PGP SIGNATURE----- --=-=-=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?867gtumu3k.fsf>