51 karma · joined January 9, 2019
Any help with code review or additional features are welcome :)
I hacked it into a python package a couple of months ago in an ADHD hyperfocus induced frenzy. Sounds like you might like it. Still a long way to go, but it's out there and FOSS. Contributions are welcome.
``` set default-bg "#2E3440"
## Start in dark mode by default set recolor true
## Nord colors for dark more set recolor-darkcolor "#D8DEE9" set recolor-lightcolor "#2E3440" ```
I spent time understanding it, and getting it working, but it really doesn't work just universally. Once the install process becomes more like, say, miniconda -- where an unprivileged user can install it locally with ease -- nix will get a massive boost in my books. Until then, I can only yearn.
[0]: https://github.com/jesseduffield/lazygit [1]: https://github.com/kdheepak/lazygit.nvim
Previously I avoided creating messy commits simply because it was "tedious" to reorganize commits. And making overly atomic commits and typing out git commands more frequently didn't appeal to me either.
Once I got used to the above tools, life got so much easier. Lazygit makes it super easy to amend, reword, and even re-position commits in a TUI environment. Real life-changer for me. I can stage hunks super easily too, though that's even easier in neovim.
The only issue I face is my C-j/C-k keys are already bound to tmux, but are needed by lazygit to reposition commits.
[0]: https://github.com/jesseduffield/lazygit [1]: https://github.com/tpope/vim-fugitive
setxkbmap -option altwin:swap_lalt_lwin,caps:ctrl_modifier
xcape -e 'Caps_Lock=Escape;Alt_R=Control_L|space'
I know that there are better ways to do this. But I never get around to trying them out.A tip for those who may just be starting out: switch your LEFT-ALT and WIN keys. Also make caps lock act like ESC on tap and CTRL on long press. See xmodmap, setxkbmap and xcape for this.
The standard shell experience is decades old, and makes it cumbersome to keep up with the pace of today. The appeal of zsh/fish is the user experience and extensibility. I have a shell config using zinit [^1] that installs my dev environment for me (fzf, tmux, nvim, and my zsh-plugins) as long as zsh exists on the new machine. While one may argue that they prefer strictly standard bash so that everything is POSIX compliant, you just have to ensure that your scripts are run with bash or whatever shell the script was made for.
What is also fascinating is the marketing and advertisement influence in all this.
In villages here a couple of generations ago, they would dry coconuts and make the oils at home. No industrial refinement, heating, and deodorization. But a few years ago there was a huge push against coconut oil, probably from the other segments of the cooking oil industry. Now there are studies saying coconut oil is actually better than most seed oils.
It's the same thing with sugar/fat and cigarettes.
And that brings us to the underlying problem: How does the public form an informed opinion when industry-funded research skews results one way and also has the "propaganda" benefit?
How many software engineers does it take to change a lightbulb?
(None. It's a hardware problem)
I've been putting off looking for an audiobook reader for linux to improve my german. HN makes life easier ;)
1. It doesn't seem to work with when $TERM is set to some non-default setting. (panic: terminal entry not found) 2. When term is forced to xterm-256-color, aerc crashes when the window is resized.