From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Cc: 3438@emacsbugs.donarmstrong.com
Subject: bug#3438: please make line-move-visual nil
Date: Fri, 12 Jun 2009 10:16:57 -0700 [thread overview]
Message-ID: <8982B2CF70794451BE7693392E14AA2A__13248.1833258227$1244828257$gmane$org@us.oracle.com> (raw)
In-Reply-To: <jwvd49nzizc.fsf-monnier+emacs@gnu.org>
> > I proposed making the variable always buffer-local.
SM> There would be no benefit to it:
SM> (set (make-local-variable <foo>) <bar>)
SM> is the standard way for major modes to set variables.
Irrelevant. This is not about how to set the variable, but whether the variable
should always be buffer-local.
`truncate-lines', `word-wrap', and similar variables are all always
buffer-local. `line-move-visual' should be also, for the same reasons.
next prev parent reply other threads:[~2009-06-12 17:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1LQhf7-00080g-Ek@beryx.hq.kred>
[not found] ` <87eiue83i7.fsf@cyd.mit.edu>
[not found] ` <F91A5F0008874B7F8539F4E38C302A80@us.oracle.com>
[not found] ` <87my92dmdt.fsf@cyd.mit.edu>
[not found] ` <87eiudewtq.fsf@uwakimon.sk.tsukuba.ac.jp>
[not found] ` <831vqdubqy.fsf@gnu.org>
[not found] ` <E1M8Rbq-0003xe-NF@fencepost.gnu.org>
[not found] ` <6161f3180905270548t3012bc1ah161719ae01db0fb5@mail.gmail.com>
[not found] ` <E1MAjTy-0005aE-Iy@fencepost.gnu.org>
[not found] ` <jwvzlcsnkyy.fsf-monnier+emacs@gnu.org>
[not found] ` <5f0ff9220906010736paad9321td86fd52326ebe722@mail.gmail.com>
[not found] ` <F412767261564B7894552DF3D4CEFD16@us.oracle.com>
2009-06-01 17:56 ` bug#3438: please make line-move-visual nil Chong Yidong
[not found] ` <87oct7sur8.fsf@cyd.mit.edu>
2009-06-01 18:26 ` Drew Adams
[not found] ` <BC1A0392D51547EE8B5FB84DB20E25C6@us.oracle.com>
2009-06-01 20:11 ` Stefan Monnier
[not found] ` <jwvoct71zxc.fsf-monnier+emacs@gnu.org>
2009-06-01 21:00 ` Drew Adams
[not found] ` <31703F2EAE7D4CAF8E671B0C18916D01@us.oracle.com>
2009-06-01 21:25 ` Lennart Borgman
[not found] ` <e01d8a50906011425n486b00ack12eaf32dc4ea1e34@mail.gmail.com>
2009-06-01 21:33 ` Drew Adams
[not found] ` <2E369A57A535414C8193711D4740ACC5@us.oracle.com>
2009-06-01 21:56 ` Lennart Borgman
2009-06-01 22:33 ` Stefan Monnier
[not found] ` <jwvd49nzizc.fsf-monnier+emacs@gnu.org>
2009-06-01 22:52 ` Drew Adams
[not found] ` <C42F1A4E73DE4300868812F6A736BEBC@us.oracle.com>
2009-06-01 23:12 ` Lennart Borgman
2009-06-01 23:13 ` Eli Zaretskii
[not found] ` <E1MBGhJ-00032F-LR@fencepost.gnu.org>
2009-06-01 23:23 ` Drew Adams
[not found] ` <62BF90AF958B432AAEAC88ED045DE035@us.oracle.com>
2009-06-02 15:59 ` Eli Zaretskii
[not found] ` <e01d8a50906011612i13b27445k8155fb63ac3fd682@mail.gmail.com>
2009-06-01 23:57 ` Drew Adams
2009-06-12 17:16 ` Drew Adams [this message]
[not found] ` <8982B2CF70794451BE7693392E14AA2A@us.oracle.com>
2009-06-12 21:45 ` Stefan Monnier
[not found] ` <jwvvdn1dt40.fsf-monnier+emacs@gnu.org>
2009-06-13 0:19 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='8982B2CF70794451BE7693392E14AA2A__13248.1833258227$1244828257$gmane$org@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=3438@emacsbugs.donarmstrong.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).