emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Marco Wahl <marcowahlsoft@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Bug: Org line commands and visual-line mode bindings [9.3.7 (9.3.7-15-gc9abb4-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20200727/)]
Date: Tue, 22 Dec 2020 17:24:55 -0300	[thread overview]
Message-ID: <87pn31y4fc.fsf@gmail.com> (raw)
In-Reply-To: <87v9ctlhma.fsf@gmail.com>

On Tue, 22 Dec 2020 at 17:18, Gustavo Barros <gusbrs.2016@gmail.com> 
> Anyway, what I came up is a slight variation from Marco's approach, 
> which may
> be just general enough to be employed by Org.
> #+begin_src emacs-lisp
> (add-hook 'visual-line-mode-hook #'my/visual-line-mode-hook-for-org)
> (defun my/visual-line-mode-hook-for-org ()
>  (when (and (derived-mode-p 'org-mode)
>             visual-line-mode)
>    ;; Ensure 'visual-line-mode' does not shadow Org's line commands.
>    (local-set-key [remap move-beginning-of-line] nil)
>    (local-set-key [remap move-end-of-line] nil)
>    (local-set-key [remap kill-line] nil)))
> #+end_src
> I've lightly tested this here and it seems to be working.

Damn!  Sorry for the noise.  It *doesn't* work, and disables Org's own 
remappings, of course.  Just as I sent I realized I had something else 
enabled which was doing the actual job (my previous take on this 
thread).  Back on the deadlock. 

Sorry again.


  reply	other threads:[~2020-12-22 20:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28  1:18 Bug: Org line commands and visual-line mode bindings [9.3.7 (9.3.7-15-gc9abb4-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20200727/)] Gustavo Barros
2020-07-28 15:34 ` Marco Wahl
2020-07-28 16:38   ` Gustavo Barros
2020-09-04 15:20   ` Bastien
2020-09-04 15:44     ` Gustavo Barros
2020-09-04 17:37       ` Bastien
2020-09-04 18:24         ` Gustavo Barros
2020-12-22 20:18         ` Gustavo Barros
2020-12-22 20:24           ` Gustavo Barros [this message]
2020-12-22 21:28             ` Gustavo Barros
2021-05-01 20:28 ` Bastien
2021-05-01 20:50   ` Gustavo Barros

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:

  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=87pn31y4fc.fsf@gmail.com \
    --to=gusbrs.2016@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=marcowahlsoft@gmail.com \


* 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


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).