Doom-emacs: evil-next-line or evil-next-visual-line

[xarthurx]

The moving bahivour at present for "j" is assigned to evil-next-line.
Does it make sense to assign it to evil-next-visual-line (which is now assigned to g j.

For programming, the switch should not make much difference as most of lines are not long.
But for text editing, it feels the evil-next-visual-line is more convenient and assign it to j would make things easier.

Just a suggestion.

[hlissner]

This was actually a bug, because evil-respect-visual-line-mode wasn't set early enough. It is now fixed, and thus j and k should be remapped to the visual line functions when visual-line-mode is active.

[adrianstaniec]

I am not sure, but have the impression that this bug is back.

[hlissner]

@adrianparvino Since https://github.com/hlissner/doom-emacs/commit/c733a6aa27a61763b65a4b868d0851fc5a361e47 and due to #2447, evil-respect-visual-line-mode is now set to nil.

To change it, add this to ~/.doom.d/init.el:

(setq evil-respect-visual-line-mode t)

[schloes]

I added (setq evil-respect-visual-line-mode t) to my configuration, but using "j" and "k" still skips the entire line. I can confirm with helpful-variable that evil-respect-visual-line-mode is non-nil, but the behavior is not working anyway. If I use regular next-line and previous-line it does work correctly. Any ideas?

[hlissner]

@schloes Did you add it to ~/.doom.d/init.el (not ~/.doom.d/config.el), as suggested? If you did, it's likely an issue with your config, because this setting works for me in vanilla Doom.

[betaprior]

Adding more information: it is not possible to toggle next-visual-line behavior in an ad hoc way since (setq evil-respect-visual-line-mode t) must be on before Evil is loaded, hence the requirement to put it in init.el.

The default value of nil becomes somewhat problematic when using org-mode; it is often useful to operate in visual line mode (e.g. if you are intending to paste the text somewhere), however gj/gk in org-mode are rebound to org navigation :(