elder_launcher
tldr
Our great sponsors
| elder_launcher | tldr | |
|---|---|---|
| 9 | 261 | |
| 40 | 48,192 | |
| - | 1.1% | |
| 0.0 | 10.0 | |
| almost 2 years ago | 6 days ago | |
| Dart | Markdown | |
| MIT License | GNU General Public License v3.0 or later |
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.
elder_launcher
-
Ask HN: What small library or tool do you want that doesn’t exist?
You might be able to find a custom launcher that can accomplish this. One such launcher is https://github.com/itsarjunsinh/elder_launcher
-
⟳ 4 apps added, 9 updated at apt.izzysoft.de
Elder Launcher (version 12): a minimalistic launcher for seniors with large fonts & icons
tldr
- Serving my blog posts as Linux manual pages
- Tell HN: My Favorite Tools
-
Should you add screenshots to documentation?
Looks like bro pages is archived and they recommend https://github.com/tldr-pages/tldr or https://github.com/cheat/cheat
-
Have i made my own linux distro? ^_^
a very excellent tool to grab is TLDR https://tldr.sh/
-
The Thing About PHP
> ...from the comments section on php.net. The latter was a surprisingly good source but none of this was ever sustainable.
Honestly, I wish more documentation out there had comments/discussion at the bottom.
For example, reading about setting up Open is Connect and having the first (most upvoted) comments on the first page explain things that might not be clear in the docs, analogies that make things easier to understand, or code/configuration snippets for a particular technology.
Somehow the comments in PHP docs were usually like: "after reading the docs, here's what you might want to really know", a bit like those tl;dr apps for manpages: https://tldr.sh/
-
Making Hard Things Easy
I'm not a fan of man pages. Or any documentation that focuses on textual explanations rather than examples in code (looking at you aws).
I recently found https://tldr.sh/ and found it more convenient. I ended up writing myself a vscode extension to have a quick lookup at my fingertips, since I am at least 60% of the time looking at a terminal in vscode
There's also tldr: https://github.com/tldr-pages/tldr
It lets you check the most commonly used options from your terminal, for example "tldr badblocks".
-
The Case for Nushell
> Along those lines, a quick way to drive adoption could be a huge "how do i do x" or recipes page to Ctrl+F through. If I have to search the internet for how to do x in nushell/fish/etc, I might as well stick to arcane bash - at least you know someone has had the same problem before.
-
Why is DNS still hard to learn?
TIL that `dig` does not have TLDR page https://github.com/tldr-pages/tldr
What are some alternatives?
cheat - cheat allows you to create and view interactive cheatsheets on the command-line. It was designed to help remind *nix system administrators of options for commands that they use frequently, but not frequently enough to remember.
tealdeer - A very fast implementation of tldr in Rust.
cheat.sh - the only cheat sheet you need
zsh-autosuggestions - Fish-like autosuggestions for zsh
navi - An interactive cheatsheet tool for the command-line
fish-shell - The user-friendly command line shell.
fish-skim - fisher plugin
fzf - :cherry_blossom: A command-line fuzzy finder
thefuck - Magnificent app which corrects your previous console command.
httpie - 🥧 HTTPie CLI — modern, user-friendly command-line HTTP client for the API era. JSON support, colors, sessions, downloads, plugins & more.
bat - A cat(1) clone with wings.
fd - A simple, fast and user-friendly alternative to 'find'