SQLite has so far never let me down, and enabled some things that would be otherwise in the “almost impossible” category. Still come across some amazing new feature that I had no idea about regularly (like the session extension), as well as regularly releasing big new features while remaining 100% backwards compatible always. Upgrading SQLite is a real joy: just replace sqlite3.{c,h} with the latest one, and eh yeah, that’s about it…
fish is a pleasure to use as a daily shell - very thankful that someone has taken on the very thankless task of making a new shell and actually thinking about the ergonomics first (“Finally, a command line shell for the 90s” is the perfect slogan for this)
I love Fish ergonomics, but actually wish it was Bash-compatible. It’s just a bit pain when you need to integrate scripts that do not have a native Fish version, it’s slower and does often not quite work (even with Bass). Nu is another shell to look at, with even more radical choices.
I really like fish. Sadly I use reverse-incremental search very often in zsh and the lack of it makes fish too hard for me to use. fish has very good reverse-prefix-incremental search but since I commonly aim to resurrect commands from history from mid-line partial-match, it doesn’t work for my use-case.
I was using fish + Starship and now I use zsh + oh-my-zsh + Starship and it’s good enough.
I have been using bash with the vi editing mode for years and it was only last month that I learned that you can press / in command mode to search command history. That’s completely changed how I use the shell (I can never remember the normal history search shortcut).
FreeBSD 14 is replacing csh with sh as the default shell and the up-arrow behaviour from csh was the big feature that everyone insisted sh needed before it could replace csh (FreeBSD’s csh up-arrow searched for things in the history matching the typed prefix). I still wouldn’t choose to use either as a daily driver, but they’re now both fine for occasional use.
Impressed you are able to use bash vi mode. I find it rather unintuitive and prefer Emacs mode but with C-x C-e to get into nvim or when I’m in Neovim’s terminal, just going to Normal mode.
Strange because I have vim everywhere else. Just not here.
I’ve written four books, a PhD thesis, a dozen papers, and at least a couple of hundred thousand lines of code in vim. At this point, convincing my fingers that any text input field is not vim is probably a lost cause. I will probably end this post by typing :wq and then have to delete it and hit post. Even if I don’t have vim mode, I hit b to go back in the command line and then have to delete the ^B.
Yep, sqlite is the first thing that came to mind when reading this thread. I’ve done a lot of data wrangling over the past year, and sqlite has come in clutch so many times.
That pretty well sums up why I just block it entirely. A favorite local web site moved from a normal wordpress comment system to disqus a few years back, and that bothered me enough to stop participating even though i’d enjoyed it for 6 or 7 years up to that point. Even in the beginning, disqus felt slimy. Since the acquisition by the surveillance tech firm: it’s a hard “No.”
Rewriting my neovim configs in Lua — and I’m having a blast! It’s still somewhat rough around the edges (like the inevitable api.nvim_exec calls for Vim stuff that don’t have Lua interfaces yet) but gosh it’s so much better — and faster! — than Vimscript.
Both, really. Lua is a lot more performant than Vimscript, and syntactically a lot less mentally demanding. At the moment, it’s still quite “beta” — you need neovim-HEAD for this, and the Lua API isn’t fully done yet. I guess you could wait until Neovim 0.5 comes out and init.lua is a valid entrypoint. That should help you kickstart your Vimscript to Lua migration.
having to modify my config using vimscript was the main gripe that made me eventually switch to emacs. It’s good to see that there’s work being done on replacing the abomination with something more usable.
I have had pretty good experience so far using Starship. It doesn’t have any significant slowdown, and it offers a wide array of informational and formatting options.
highly recommend anyone doing Clojure development in neovim to check out Conjure: https://github.com/olical/conjure. Really nice integration all around for connecting to an nREPL, evaling forms, etc. - all based on localleader bindings.
What’s the history of Cisco having their own Scheme?
Cisco bought Kent Dybvig’s company, essentially to hire Kent I believe, and thus, with it, bought Chez.
There’s a bit of history here: https://beautifulracket.com/appendix/racket-and-chez-scheme.html
SQLite has so far never let me down, and enabled some things that would be otherwise in the “almost impossible” category. Still come across some amazing new feature that I had no idea about regularly (like the session extension), as well as regularly releasing big new features while remaining 100% backwards compatible always. Upgrading SQLite is a real joy: just replace sqlite3.{c,h} with the latest one, and eh yeah, that’s about it…
fish is a pleasure to use as a daily shell - very thankful that someone has taken on the very thankless task of making a new shell and actually thinking about the ergonomics first (“Finally, a command line shell for the 90s” is the perfect slogan for this)
I became a “fisher” past year and I haven’t had a reason to regret that move. Contributed some missing auto-completions to it as well.
I love Fish ergonomics, but actually wish it was Bash-compatible. It’s just a bit pain when you need to integrate scripts that do not have a native Fish version, it’s slower and does often not quite work (even with Bass). Nu is another shell to look at, with even more radical choices.
I installed Fish a few months ago and haven’t looked back, it is such a pleasure to use.
Fish was the big thing I missed when I moved from Linux to Windows.
As a daily WSL user, I’m wondering why make the move
AutoHotKey.
i was just about to write “you should write an article about how you use autohotkey” because it seems like it would be interesting
then i found https://www.hillelwayne.com/post/ahk/
I really like
fish. Sadly I use reverse-incremental search very often inzshand the lack of it makesfishtoo hard for me to use.fishhas very good reverse-prefix-incremental search but since I commonly aim to resurrect commands from history from mid-line partial-match, it doesn’t work for my use-case.I was using
fish+ Starship and now I usezsh+ oh-my-zsh + Starship and it’s good enough.I use
fzfto fill this hole in fish, via its ctrl-r bindingAbsolute game changer! Thank you!
I have been using
bashwith the vi editing mode for years and it was only last month that I learned that you can press / in command mode to search command history. That’s completely changed how I use the shell (I can never remember the normal history search shortcut).FreeBSD 14 is replacing csh with sh as the default shell and the up-arrow behaviour from csh was the big feature that everyone insisted sh needed before it could replace csh (FreeBSD’s csh up-arrow searched for things in the history matching the typed prefix). I still wouldn’t choose to use either as a daily driver, but they’re now both fine for occasional use.
Impressed you are able to use bash vi mode. I find it rather unintuitive and prefer Emacs mode but with C-x C-e to get into nvim or when I’m in Neovim’s terminal, just going to Normal mode.
Strange because I have vim everywhere else. Just not here.
I’ve written four books, a PhD thesis, a dozen papers, and at least a couple of hundred thousand lines of code in vim. At this point, convincing my fingers that any text input field is not vim is probably a lost cause. I will probably end this post by typing :wq and then have to delete it and hit post. Even if I don’t have vim mode, I hit b to go back in the command line and then have to delete the ^B.
Yep, sqlite is the first thing that came to mind when reading this thread. I’ve done a lot of data wrangling over the past year, and sqlite has come in clutch so many times.
It pairs well with pandas!
That pretty well sums up why I just block it entirely. A favorite local web site moved from a normal wordpress comment system to disqus a few years back, and that bothered me enough to stop participating even though i’d enjoyed it for 6 or 7 years up to that point. Even in the beginning, disqus felt slimy. Since the acquisition by the surveillance tech firm: it’s a hard “No.”
how do you go about blocking it?
I use the EFF’s privacy badger add-on.
umatrix is the way to get back control on the Web
Umatrix was one of my favourite extensions.
Too bad its repo has been “archived” now. Development has ceased.
Still works pretty darn well for me, so it’s still my favourite 😊
I blacklist it in my pihole install.
Rewriting my neovim configs in Lua — and I’m having a blast! It’s still somewhat rough around the edges (like the inevitable
api.nvim_execcalls for Vim stuff that don’t have Lua interfaces yet) but gosh it’s so much better — and faster! — than Vimscript.faster to write, or faster to execute? I’ve been tempted to migrate mine but wasn’t sure if the benefit outweighed the costs yet.
Both, really. Lua is a lot more performant than Vimscript, and syntactically a lot less mentally demanding. At the moment, it’s still quite “beta” — you need neovim-HEAD for this, and the Lua API isn’t fully done yet. I guess you could wait until Neovim 0.5 comes out and
init.luais a valid entrypoint. That should help you kickstart your Vimscript to Lua migration.having to modify my config using vimscript was the main gripe that made me eventually switch to emacs. It’s good to see that there’s work being done on replacing the abomination with something more usable.
nice post - I’ve supported light / dark colorschemes on my site for awhile, but didn’t know about the meta header. Added!
feedbin has a clean web interface, if you’re into that. Reeder.app syncs with it for a more native experience (iOS / macOS).
I think you meant
:Commits?But otherwise, looks fairly similar to how I use
fzf, nice write-up.Yes, my bad. I fixed it now, thanks.
I might do one post on fzf usage in the command-line, there are many mind-blowing things there.
I have had pretty good experience so far using Starship. It doesn’t have any significant slowdown, and it offers a wide array of informational and formatting options.
+1 to starship - it’s nice having the prompt character change color and shape when the previous command fails:
Changing shape is easy enough with the code from the article, no need for separate binaries:
good point! I have been tempted to ditch starship for some native
fishshell goodness … someday :)highly recommend anyone doing Clojure development in neovim to check out Conjure: https://github.com/olical/conjure. Really nice integration all around for connecting to an nREPL, evaling forms, etc. - all based on
localleaderbindings.That’s true! I can’t recomment it highly enough!