From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: please make line-move-visual nil Date: Tue, 26 May 2009 22:21:40 +0200 Message-ID: References: <54A5E41E3FD446F590AA580D90C5B518@us.oracle.com> <56DF3F5FED9445EAB0C666DE0904BAC2@us.oracle.com> <87fxes5p4n.fsf@thinkpad.tsdh.de> <7b501d5c0905260437l2a14fd21nd319f4eeb4e3d972@mail.gmail.com> <4A1BF4A0.3000609@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1243369320 5433 80.91.229.12 (26 May 2009 20:22:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 26 May 2009 20:22:00 +0000 (UTC) Cc: Tassilo Horn , emacs-devel@gnu.org, Stefan Monnier , Drew Adams , Deniz Dogan To: Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 26 22:21:57 2009 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.50) id 1M939m-0007nu-QR for ged-emacs-devel@m.gmane.org; Tue, 26 May 2009 22:21:55 +0200 Original-Received: from localhost ([127.0.0.1]:51304 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M939m-00013Z-1n for ged-emacs-devel@m.gmane.org; Tue, 26 May 2009 16:21:54 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M939h-00013L-3i for emacs-devel@gnu.org; Tue, 26 May 2009 16:21:49 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M939b-000135-Ma for emacs-devel@gnu.org; Tue, 26 May 2009 16:21:47 -0400 Original-Received: from [199.232.76.173] (port=52895 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M939b-000132-I1 for emacs-devel@gnu.org; Tue, 26 May 2009 16:21:43 -0400 Original-Received: from mail-fx0-f169.google.com ([209.85.220.169]:45563) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M939a-0004Ny-BJ; Tue, 26 May 2009 16:21:42 -0400 Original-Received: by fxm17 with SMTP id 17so4414794fxm.42 for ; Tue, 26 May 2009 13:21:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=N4aOZI+DhXTMEC6A4CiiOnHWYhTvGpkwScpYpxKfzuo=; b=nsMjgZKctz8QaLsMTPNKaAT9sxYUcPj3urSLcClx7kCXIZ62LBxm/C4klbLr2cvFy/ MmbYj3a2b87sCn+HM+kiOiYKZoHWY7quuOHBbVPfpDdjMDNheDKiTdn8H28F1+PzRirO MwkoGrJ8h7miwZ7VhRcF9ritGDOuUJYpyX/6A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=MXavc86UhZiIGTy3Ci1qPW5wAulXQ5NK5z7cSvU77Lgpe/P4J/noHwUx0lbZQusqKT TLzylVkOZfvvQRRaWxg8fwhDMYK8rLMbUum2fCZd+oL+SIR7ey5KnDQbTvr7Je7I3VEl gwkQW34+IIcks73fLoTgz17CifRMdoF2BbuUo= Original-Received: by 10.239.154.142 with SMTP id e14mr603419hbc.69.1243369300239; Tue, 26 May 2009 13:21:40 -0700 (PDT) In-Reply-To: <4A1BF4A0.3000609@gnu.org> X-detected-operating-system: by monty-python.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:111128 Archived-At: On Tue, May 26, 2009 at 3:54 PM, Jason Rumney wrote: > Lennart Borgman wrote: >> >> I believe it might be better to investigate more how certain features >> (like visual-line-move) should be handled under different >> circumstances. Such circumstances is (as is pointed out here) macros, >> but there are others two, like printing. > > line-movement is not involved in printing. But any non-interactive use > probably falls into the same category as macros. Eh, yes, but printing is quite closely related here due to that visual-line-move turns on word-wrap. It would be nice to be able to get print to use that too. It is of course another problem. However I suspect that thinking about those problems together might create opportunities for better solutions (as you suggested).