From: John Hutchinson <johnrhutchinson@att.net>
To: emacs-orgmode@gnu.org
Subject: Re: Interaction between org-special-ctrl-a/e and visual-line-mode in Org 9.2?
Date: Tue, 22 Jan 2019 16:42:41 -0500 [thread overview]
Message-ID: <332c4847-5de4-c036-bc4e-1b4f4c49efb1@att.net> (raw)
In-Reply-To: <87munthjjd.fsf@nicolasgoaziou.fr>
Thanks for helping me understand this.
For now, I think I'll just add a hook to "org-mode-hook" that rebinds
"C-a" and "C-e" to their "org-" instances.
I'm not sure that this is a totally satisfactory solution, but I think
it will work for me in the short-term at least.
Thanks again for your help,
=John
On 1/21/2019 14:56, Nicolas Goaziou wrote:
> Hello,
>
> John Hutchinson<johnrhutchinson@att.net> writes:
>
>> Under org 9.1 (which works as expected), C-e is bound to "org-end-of-line".
>>
>> In org 9.2 (which does not work as expected) it's bound to
>> "end-of-visual-line".
> In Org 9.1, `org-end-of-line' is mapped to `C-e' whereas in Org 9.2, it
> remaps [move-end-of-line], whatever its binding is. The issue is that
> `visual-line-mode' does the same, hence the conflict.
>
> Remapping [move-end-of-line] doesn't force `C-e' on the user, so the
> current way has its advantages.
>
>> Restarting org-mode, via "org-reload" or via "C-c C-c" in the initial
>> lines, does not change this behavior.
> I think `M-x org-mode' should be sufficient to bind `C-e' back to
> `org-end-of-line'. It is also possible to use `visual-line-mode-hook'
> to always set
>
> I'm not sure how to fix this from Org, tho.
>
> Thoughts?
>
> Regards,
>
--
John Hutchinson
JohnRHutchinson@att.net
prev parent reply other threads:[~2019-01-22 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 18:55 Interaction between org-special-ctrl-a/e and visual-line-mode in Org 9.2? John Hutchinson
2019-01-18 21:31 ` Nicolas Goaziou
2019-01-21 14:40 ` John Hutchinson
2019-01-21 19:56 ` Nicolas Goaziou
2019-01-22 21:42 ` John Hutchinson [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=332c4847-5de4-c036-bc4e-1b4f4c49efb1@att.net \
--to=johnrhutchinson@att.net \
--cc=emacs-orgmode@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/org-mode.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).