I liked the idea, but the implementatino was too flakey and didn’t actually let
me do what I wanted to do. The biggest issue was that ‘comment-dwim’ didn’t work
anymore and it got easily confused and screwed up the colors for my mode-line.
A lot of the time when capturing some task my cursor is at a random location and
it doesn’t actually mean what I’m looking at is at all related to what I’m
writing.
I think this will make me occasionally miss certain connections, but usually
will provide less noise.
‘eshell-mode-map’ isn’t a keymap until after ‘eshell-mode’ has run. It’s defined
as ‘nil’ in the top-level of the ‘esh-mode’ package. ‘nil’ is not a valid keymap
that new keys can be defined into.
This reverts commit cd067e3673.
On the build runner this ends up trying to build ‘oni-scheme.el’ as a multifile
package. It doesn’t seem to notice the distinction between the regular files and
directories.
At work I have to work with a lot of files that other people work on as well.
Other people don’t usually have their editor set up to remove all trailing
whitespace, and we’re not allowed to make a change that includes a lot of extra
whitespace changes[1]. So I end up having to revert a lot of whitespace changes
just before submitting. And if I then have to make more changes, for example
because something was pointed out in a code review, I have to do it again.
‘ws-butler’ promises that it will still prevent me from submitting extraneous
whitespace, but will not touch lines that I haven’t changed, so that would
prevent me from having to revert them all the time.
[1]: This is good, having a lot of whitespace changes can distract from or even
completely hide the actual change you’re trying to make.
