tldr-sh-client
dotfiles
tldr-sh-client | dotfiles | |
---|---|---|
3 | 21 | |
701 | 45 | |
- | - | |
4.3 | 9.0 | |
4 months ago | 19 days ago | |
Shell | Shell | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tldr-sh-client
-
your favorite cheatsheet app ?
I like tldr with sh client. Simple and POSIX compliant.
-
Node.js packages don't deserve your trust
> While I find projects in those other languages to also have too many dependencies, it's no where near what happens in JS apps. I'm thinking of projects I've recently worked on in Rust, PHP, and Java.
My experience with these new languages is such that this feels a bit unfair. It's like insisting that a disaster with 1000 fatalities is "much worse" than one with "only". It's ... true ... I guess, but there's something uncomfortable about making the comparison. Something has gone badly wrong if the comparison even needs to happen in the first place.
What I'm getting at is that e.g. Rust has an enormous problem in this area. It's not uncommon for me to see Node projects with over a thousand transitive dependencies, but on the other hand, I very frequently see Rust projects with over a hundred. And the Node projects tend to be more complicated than the Rust ones; they do more.
Take the last Rust program I tried to use, tealdeer. [1] If you don't know, tldr is a project that provides alternative simplified man pages for commonly used programs that consist entirely of easy to understand examples for the program. [2] What a tldr client needs to do is simply to check a local cache for each lookup, and if necessary update the cache online. It's a trivial problem that can be, and has been! [3], solved in a few hundred lines of shell (if you're being extremely verbose). How many recursive dependencies would you guess tealdeer uses? Depends on how you count, of course, but as of today the answer is ~133 deduplicated dependencies! For a program that's a glorified wrapper around curl!
Or another Rust program I looked at recently, rua [4]. In Arch Linux, the AUR is a repository of user maintained scripts for building and installing software as native Arch packages. Official tools for the building and installing software already exist for Arch, but it is common for users to use a wrapper around these tools that makes fetching and updating the software from the AUR easier. It's a relatively simple task that (once again) can be done with shell scripts. rua is such a wrapper. As of today it uses 137 deduplicated dependencies!
These Rust programs are simple terminal tools to do tasks that are almost trivial in nature. And yet they require hundreds of constantly updating dependencies! The situation may well be better than what you'll find for Node, but it's undeniably disastrous compared to either simpler languages without a built in package manager (like C) or more complicated batteries-included languages where best practices continue to prevail (like Python).
[1] https://github.com/dbrgn/tealdeer
[2] https://tldr.sh/
[3] https://github.com/raylee/tldr-sh-client/blob/main/tldr
[4] https://github.com/vn971/rua
-
unlimited power
Bash https://github.com/raylee/tldr-sh-client
dotfiles
-
How do you organise your snippets?
You put your snippets in a lua file, like here (with syntax according to the luasnip documentation) and invoke such file somewhere in your configuration so that it's required (i. e. "loaded").
-
Function: Attempt to call global 'xxx' (a nil value)
Without knowing your precise folder structure and where you are requiring what is a little hard to understand. However, I do something similar but I have a functions file in my lua folder (without any nested subfolder) and I just require all the .lua stuff in my init.lua here.
-
Select filetype based on Filename?
Some examples here, but as other users suggested it's vim.filetype.add().
-
which snippet engine are you using?
You can find my snippets here: to be honest they are rather simple, so creating such doesn't take me too long. In general I would say either style is fine (or equally ugly :p).
-
I refactored my lua structure and have lost some UI styling ?
Whilst at the moment I do not have time to go through your config, this is my noice config and my lsp. You can copy&paste, I have borders set and normal highlight window. It works, so just copy it and then work back till you add yours.
-
lsp handlers textDocument issue after update Noice
If it can be of help this is my noice configuration and lsp setup. It is working fine for me and I tested updating everything right now.
-
TreeSitter Code Highlight
See examples here.
-
minimal config for sessions management
Here - it is just a config file with a few functions: use it as inspiration! The code is probably not optimised yet (I just got it working and I wanted to share, do let me know if you can make it better): mappings to operate
-
your favorite cheatsheet app ?
I use navi and I am very satisfied: it's very easy to create your own cheatsheets, see for instance what I do here.
-
...and now gh-i to search for issues interactively!
It is macOS with iTerm2 and zsh as shell. The DE is the standard one that comes pre-installed, I didn't make changes; you can find my configurations here
What are some alternatives?
opendrop - An open Apple AirDrop implementation written in Python
noice.nvim - 💥 Highly experimental plugin that completely replaces the UI for messages, cmdline and the popupmenu.
cheat.sh - the only cheat sheet you need
navi - An interactive cheatsheet tool for the command-line
proposal-ses - Draft proposal for SES (Secure EcmaScript)
indent-blankline.nvim - Indent guides for Neovim
rua - Build tool for Arch Linux providing control, review and jailed build options
vimspector - vimspector - A multi-language debugging system for Vim
navi-tldr-pages - tldr-pages for navi, an interactive cheatsheet tool for the command-line
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support
snapdrop - A Progressive Web App for local file sharing
dotfiles - My Dotfiles