diff options
author | Aryadev Chavali <aryadev@aryadevchavali.com> | 2020-08-09 14:10:17 +0100 |
---|---|---|
committer | Aryadev Chavali <aryadev@aryadevchavali.com> | 2020-08-09 14:18:39 +0100 |
commit | 229647da08c6db68c7aba112ad8a5c4213cb5619 (patch) | |
tree | 9fdbc4736458441e43f39992b306eebc7425b540 /Polybar/.config/polybar | |
parent | 1f4e7245c943dbec1f8ff2571c0547f4f87cee3b (diff) | |
download | dotfiles-229647da08c6db68c7aba112ad8a5c4213cb5619.tar.gz dotfiles-229647da08c6db68c7aba112ad8a5c4213cb5619.tar.bz2 dotfiles-229647da08c6db68c7aba112ad8a5c4213cb5619.zip |
~long lines -> auto-fill-mode
In my config.org, and from now on in all text documents, auto fill
mode will be employed. I've added a text-mode-hook for auto-fill-mode.
I've found difficulty in handling long lines through truncate lines,
which doesn't have full control over movement in lines that run over
the terminal width. I've had to use '$' or move-end-of-line to move to
a point which visually should just require next-line to move to.
This inconsistency between visuals and movement is very frustrating
and abrupt when it occurs. Though auto fill mode has its own issues
(sets all text to 80 characters, which can be annoying in terms of
version control) it is far better than any other solution that I can
find.
Diffstat (limited to 'Polybar/.config/polybar')
0 files changed, 0 insertions, 0 deletions