From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Reitter Newsgroups: gmane.emacs.devel Subject: Re: Hl-line and visual-line Date: Sun, 23 May 2010 19:04:02 -0400 Message-ID: <4D3EC595-2FF1-42BC-8DB3-26F3A91501D4@gmail.com> References: <45790724-63FC-4B80-A70D-8CD49A92FEE3@gmail.com> <8339xmqob9.fsf@gnu.org> <94F28B33-A04E-4511-B93D-E5471EE4D0DE@gmail.com> <201005210834.28589.tassilo@member.fsf.org> <83wruxpt2z.fsf@gnu.org> <83r5l2o7fx.fsf@gnu.org> <47101594-5A7C-4FF1-8C58-C77AF33F35F2@gmai0l.com> <83ljbanytd.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1274655862 4242 80.91.229.12 (23 May 2010 23:04:22 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 23 May 2010 23:04:22 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 24 01:04:21 2010 connect(): No such file or directory Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OGKDU-0007L4-NJ for ged-emacs-devel@m.gmane.org; Mon, 24 May 2010 01:04:21 +0200 Original-Received: from localhost ([127.0.0.1]:56259 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OGKDU-0003hU-8r for ged-emacs-devel@m.gmane.org; Sun, 23 May 2010 19:04:20 -0400 Original-Received: from [140.186.70.92] (port=40929 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OGKDN-0003fB-Pu for emacs-devel@gnu.org; Sun, 23 May 2010 19:04:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OGKDI-0004NT-QD for emacs-devel@gnu.org; Sun, 23 May 2010 19:04:13 -0400 Original-Received: from mail-qy0-f187.google.com ([209.85.221.187]:43622) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OGKDG-0004N7-Fw; Sun, 23 May 2010 19:04:06 -0400 Original-Received: by qyk17 with SMTP id 17so3915614qyk.12 for ; Sun, 23 May 2010 16:04:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=SzRqCTNvXEbshCfAeF5tqhOePzLXnN2kBhbjbAnbxv4=; b=JUTIIQqAFWuj0L/2EZLVuZII23SfoieahqhIvR2ebD5ngRLFbkuNbsV15RiDVxlv2p q+VoX4viDB2scUEn8EzNNa5J6nmd/LRlDu9cBv3t38d3NN9sfAS4qYU0cQv7XBHs5wtt X97ZqBu6Q7+9Ka3Sr8h5qYSdIBhbEgl6AD2Mo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=xp/rYWyG5qSHpkLI8G9KfpbCIKQmOsSkNKGY+LEbSLq4zDiOMZUR7XWEsmS7lrOz2I IhpQdLiGfFz9yKR6JfmbT5jdZOkqYIEQ8pEcsMVGBLpIhDcA6/mo9bMfCutSsN/joXEk GlzTUkL6Jb09/NauidBZ4jGjctrJCa80euRN0= Original-Received: by 10.224.106.18 with SMTP id v18mr2650922qao.172.1274655845567; Sun, 23 May 2010 16:04:05 -0700 (PDT) Original-Received: from [192.168.1.17] (pool-96-235-7-98.pitbpa.east.verizon.net [96.235.7.98]) by mx.google.com with ESMTPS id 22sm2158675qyk.2.2010.05.23.16.04.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 23 May 2010 16:04:04 -0700 (PDT) In-Reply-To: <83ljbanytd.fsf@gnu.org> X-Mailer: Apple Mail (2.1078) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:125155 Archived-At: On May 23, 2010, at 4:33 PM, Eli Zaretskii wrote: >=20 >> The second use case would be to actually capture a whole line. I = have functions that kill the whole line (from left to right). They = would use `kill-region' from X to Y. The same goes for hl-line-mode, = where ONE overlay is drawn. >> So, these functions would need a new function such as = "regions-within-visual-line" or so, returning a list of (from . to) = regions, or some other means of identifying the region.=20 >=20 > Sorry, I don't get this part. Can you give an example that uses > kill-region and another one with one overlay for hl-line-mode, and > explain how the list of the form you mention would help? Back to your example, buffer text is "abcde ABCDE FGHIJ xyz", displayed = with word-wrap as 0) abcde JIHGF 1) EDCBA xyz Say, point is in line 0, at "c". Deleting the visual line should = delete line 0, which is two portions of text: "abcde" and "FGHIJ". =20 My reference to C-k assumed visual-line-mode semantics, as well, so C-k = would delete "de" and "FGHIJ". > Users expect logical-order regions. Logical-order regions may = surprise > the first time you see it, but are easy to get used to, since that's > the order you read the text you mark. Yes, that sounds good. I was just thinking about how marking a region = by mouse would work; I have seen this with bidirectional text in a = NS/Cocoa text edit view, and it seems reasonable. You're probably in a = much better position to tell what bidi users would expect. D=