From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Visual line movement inconsistency
Date: Fri, 29 Aug 2008 09:54:55 +0200 [thread overview]
Message-ID: <48B7AB4F.50709@gmail.com> (raw)
In-Reply-To: <87myiws30g.fsf@thinkpad.tsdh.de>
Tassilo Horn wrote:
> Miles Bader <miles@gnu.org> writes:
>
> Hi Miles,
>
>>> But is this inconsistent behavior of C-n/C-p and C-a/C-e really the
>>> intended default? I think it would be better if C-a/C-e respected
>>> the value of `line-move-visual', too. Then the default would be like
>>> visual-line-mode without word-wrapping.
>> It was discussed and the current behavior seemed to be the consensus
>> choice.
>>
>> I agree that it can be confusing, but I think it's much more dangerous
>> to change the default behavior of C-a/C-e, because people depend a lot
>> more on their precise behavior
>
> I see. But at least there should be some way to move to the
> beginning/end of a visual line. Maybe an option or simply some new
> binding.
I have been using something like this for a while
(defun ourcomments-move-beginning-of-line(arg)
"Move point to beginning of line or indentation.
See `beginning-of-line' for ARG.
If `physical-line-mode' is on then the visual line beginning is
first tried."
(interactive "p")
(let ((pos (point)))
(call-interactively 'beginning-of-line arg)
(when (= pos (point))
(if (= 0 (current-column))
(skip-chars-forward " \t")
(backward-char)
(beginning-of-line)))))
(put 'ourcomments-move-beginning-of-line 'CUA 'move)
next prev parent reply other threads:[~2008-08-29 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 13:45 Visual line movement inconsistency Tassilo Horn
2008-08-29 0:46 ` Miles Bader
2008-08-29 7:18 ` Tassilo Horn
2008-08-29 7:54 ` Lennart Borgman (gmail) [this message]
2008-08-29 12:02 ` Kim F. Storm
2008-08-29 14:59 ` Miles Bader
2008-08-29 18:13 ` Kim F. Storm
2008-08-29 23:53 ` Miles Bader
2008-08-30 15:35 ` Kim F. Storm
2008-08-30 23:53 ` Chong Yidong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48B7AB4F.50709@gmail.com \
--to=lennart.borgman@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.