this allows for better editing experience compared to the stringly mess
from before.
So now Emacs is good for modifying NeoVim config, with support for both
Nix and Lua, and NeoVim is capable of editing Emacs config via orgmode.
Nice :)
This is primarily there because quite a few language servers are written
using NodeJS (not that I still like that fact..) but since Neovim is my
'fallback' editor, supposed to help with quick edits/fix Emacs config,
LSP is very much out of scope.
Neovim is my fallback editor, when Emacs config is borked. It is nice
(and risky) to mess with this, but I expect Neovim plugins to be
slightly more stable than ball-of-mud that is Emacs runtime.
This gives a nice magit-like interface, a decent mode/statusline, and
enables tree-sitter for all languages, including a decent enough orgmode
plugin.
nvim still launches in less time than I can notice, and since it is
terminal only, I expect to use it much less often than Emacs. But, when
the need arises, it will be nicer than being completely barebones.
P.S. This commit was written from neovim itself, using the fancy neogit
plugin, and I must say, it is noice! Not quite the magit that I'm used
to, but close enough :)
shell history backed by sqlite database and spruced up with colorful
interface.
It is a direct replacement for fzf in that regard, and seems to work
quite well, albeit does not interact with fzf satisfactorily. So this is
an experiment to see how it goes.
It also provides syncing of shell history, with end-to-end encryption,
so that's something I'm looking forward to. Let's see how it goes.
Although aliases are enabled, I could not figure out a way to get them
to work with my current shell. I think this is because while
home-manager is trying to set aliases, they are set and controlled by
NixOS config, which doesn't have such option for fzf. I'll need to find
a way to set Fish as default shell via home-manager, but right now that
way does not work because home-manager cannot set fish plugins by using
nixpkgs derivation for it directly. :(
On NixOS the full path of binaries is long, obscures the flags/options given,
and is not very useful, since the nix store and hash are quite meaningless.
As such, it makes sense on NixOS to hide the full path of the program.
As for how to find the actual variable names for htop config, this file is
useful:
40104588f3/Settings.c
This allows easy config of few applications/services
- git
- htop
- fzf
- neovim
* syncthing is not enabled yet. During previous experimentation it did not work,
so need to look more into it
