From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Bob Nnamtrop Newsgroups: gmane.emacs.devel Subject: Re: please make line-move-visual nil Date: Thu, 14 May 2009 11:14:43 -0600 Message-ID: <99750f710905141014w2b2c429etf4e15e4a4735eee0@mail.gmail.com> References: <23521879.post@talk.nabble.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=0016e64f51ae9e3c1d0469e27815 X-Trace: ger.gmane.org 1242325366 23285 80.91.229.12 (14 May 2009 18:22:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 14 May 2009 18:22:46 +0000 (UTC) To: Emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 14 20:22:40 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 1M4fZm-0005n7-HM for ged-emacs-devel@m.gmane.org; Thu, 14 May 2009 20:22:38 +0200 Original-Received: from localhost ([127.0.0.1]:38648 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M4fZl-0006oQ-Qc for ged-emacs-devel@m.gmane.org; Thu, 14 May 2009 14:22:37 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M4eWe-0008RC-GW for emacs-devel@gnu.org; Thu, 14 May 2009 13:15:20 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M4eWZ-0008OO-F0 for Emacs-devel@gnu.org; Thu, 14 May 2009 13:15:19 -0400 Original-Received: from [199.232.76.173] (port=49865 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M4eWZ-0008OF-94 for Emacs-devel@gnu.org; Thu, 14 May 2009 13:15:15 -0400 Original-Received: from mail-gx0-f176.google.com ([209.85.217.176]:36418) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M4eWY-0001xZ-Us for Emacs-devel@gnu.org; Thu, 14 May 2009 13:15:15 -0400 Original-Received: by gxk24 with SMTP id 24so2815451gxk.18 for ; Thu, 14 May 2009 10:15:14 -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:content-type; bh=uxsdnLaj2rqpoXm5VxBNSkBAROmxT3K907Q12RV7xgw=; b=JMJ1I9u/0Gi98zi3K353hB3sGpflA3tqnqTPbXsN3WGuDARMxLxyD2oAxGGvEcxCYc B33iGdRa9Dnrz041FsE0uvpW34XPAXxZfgIEd6Bl5BSXWElSqMBOFB7if60L6NTLXPIl uRYS9POdXJVEs6ozycD/Qcp/yktCT+HsIMII0= 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 :content-type; b=PV+VVGydv4gngv53a0+pfis5V0RsiLk8TwHEwdRXEFhC3Oo5Pl1le9AYh16nPfVKP5 +paL1Ij9EWqyS9qTPSZc9bkOMmQtekOCtoDxaYA7c9NK4vbv7X9tOS/RCeGgmmmmSNGM Tw/uqn6k2Sfn+C4PHMwEOqLEgycOvuf5HV9Ho= Original-Received: by 10.90.35.9 with SMTP id i9mr251491agi.64.1242321314003; Thu, 14 May 2009 10:15:14 -0700 (PDT) In-Reply-To: <23521879.post@talk.nabble.com> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-Mailman-Approved-At: Thu, 14 May 2009 14:21:30 -0400 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:110877 Archived-At: --0016e64f51ae9e3c1d0469e27815 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I somehow missed this. I have no opinion on the default but I have noticed an inconsistency with this variable. In viper-mode, line-move-visual is respected by down/up arrows but not by j/k. I would think they should BOTH respect the variable. These call the functions previous-line/next-line and viper-previous-line/viper-next-line, respectively. It would seem the viper version need to be corrected. Bob On Wed, May 13, 2009 at 7:35 AM, garyo wrote: > > > > Alfred M. Szmidt wrote: > > > > Please make line-move-visual nil, it is totally uninutive to have the > > point move to the same line, when you explicitly told it to move to > > the next line. > > > > I agree, this is very different behavior for such a core command! > > -- > View this message in context: > http://www.nabble.com/please-make-line-move-visual-nil-tp21640152p23521879.html > Sent from the Emacs - Dev mailing list archive at Nabble.com. > > > > --0016e64f51ae9e3c1d0469e27815 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I somehow missed this.=A0 I have no opinion on the default but I have notic= ed an inconsistency with this variable.=A0 In viper-mode, line-move-visual = is respected by down/up arrows but not by j/k.=A0 I would think they should= BOTH respect the variable.=A0 These call the functions previous-line/next-= line and viper-previous-line/viper-next-line, respectively.=A0 It would see= m the viper version need to be corrected.

Bob

On Wed, May 13, 2009 at 7:35 AM, = garyo <garyo@gena= rts.com> wrote:



Alfred M. Szmidt wrote:
>
> Please make line-move-visual nil, it is totally uninutive to have the<= br> > point move to the same line, when you explicitly told it to move to > the next line.
>

I agree, this is very different behavior for such a core command!

--
View this message in context: http://www= .nabble.com/please-make-line-move-visual-nil-tp21640152p23521879.html Sent from the Emacs - Dev mailing list archive at Nabble.com.




--0016e64f51ae9e3c1d0469e27815--