nxes
broot
nxes | broot | |
---|---|---|
4 | 41 | |
11 | 10,179 | |
- | - | |
0.0 | 9.1 | |
over 2 years ago | 14 days ago | |
C | Rust | |
BSD Zero Clause License | 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.
nxes
-
plan9 inspired applications on linux
Neat! I'm also working on an extended version of es, it's been hard to work on it consistently, but I've torn out some old code, added a few useful primitives, and implemented a couple nice functions like pushd/popd in the shell itself.
-
How about set ZSH as default shell?
What value does that 10MB bring? 10MB in a vacuum is not a problem with modern storage capacities, but bash is already around 7MB larger than a shell needs to be to supply the benefits it does. Look at shells like ksh, rc, or es (or my own fork nxes) for great examples of significantly smaller shells. Hell, there's barely more utility in bash (~8.44MB) than in oksh (~374KB).
-
What is your cd system?
I don't actually see the need to jump around the filesystem that much, but I mostly use this, on many work systems I use the built-in pushd/popd utilities in bash, and on other shells, make use of cd - for quicker backtracking.
-
atom: Shell scripting that will knock your socks off.
Thanks for the link, I'll have to check it out! I've been hacking on an old, public domain shell called es in my spare time and have made some minor progess so far. One of my goals is to eliminate the reliance on a parser generator like Yacc and instead implement my own LALR or LR(1) parser, and was planning on trying to swap out the current Yacc file for something like lemon to start getting a better understanding of what's needed.
broot
-
Use Midnight Commander like a pro (2015)
Take a look at broot https://github.com/Canop/broot
-
Johnny Decimal: A System to Organize Projects
A past coworker implemented a system like this. It was awful. He was the gatekeeper because the numbers and names had to be "just so" to meet his approval, and he was the most senior person on the team. He was neurotic in general and a pain to work with.
The idea of limiting yourself to a few top-level categories in a directory hierarchy and then doing the same with subdirectories makes sense, but adding numbers is a bad idea. It just creates more work, and other people have to learn your idiosyncratic nomenclature. Just give the directories good names and get on with it. Search really isn't as bad as the article suggests, especially with something like broot [1].
[1]: https://github.com/Canop/broot
- Broot: A new way to look at file management written in Rust
-
Antonmedv/walk: Terminal file manager
I've used a lot of the tools mentioned here in comments, but I think just for finding a directory/file broot[1] is much faster and easier than others. Though it is also quite feature rich but mostly it's just write a fuzzy search term that could even be sub-sub-directory and open, extremely quickly.
[1] https://github.com/Canop/broot
-
Projectable: A TUI file manager built for projects
`broot` (https://github.com/Canop/broot) is another file manager with a curious interface that seems to fill a similar niche.
Of course, there are many other file managers to choose from (mc, ranger, nnn, lf, ....), but most of them don't show nested subdirectories by default.
-
Report on platform-compliance for cargo directories
As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.
-
erdtree v1.2.0, a modern multi-threaded alternative to `du` and `tree` now with support for globbing, icons, and more
You may be interested in broot
-
bsdutils: Alternative to GNU coreutils using software from FreeBSD
I think you’re conflating different projects.
There are projects that aim for a better user experience, with better command line interface, defaults, performance and UI. These are of course breaking changes and the programs can’t be used as drop in replacement. Some examples are
- ls => exa (https://github.com/ogham/exa)
- grep => ripgrep (https://github.com/BurntSushi/ripgrep)
- cat => bat (https://github.com/sharkdp/bat)
- tree => broot (https://github.com/Canop/broot)
The person you’re replying to was speaking of a different project - uutils (https://github.com/uutils/coreutils). These are drop in replacements with identical interfaces (modulo bugs).
-
Reading Ebooks on the Commandline
Even better broot, previously adding view verb to config:
-
Is possible to configure "micro" terminal text editor with "broot" tool, to open text file with micro?
Broot: https://github.com/Canop/broot
What are some alternatives?
lax - Locate Args and Execute
fzf - :cherry_blossom: A command-line fuzzy finder
voidrice - My dotfiles (deployed by LARBS)
nnn - n³ The unorthodox terminal file manager
ble.sh - Bash Line Editor―a line editor written in pure Bash with syntax highlighting, auto suggestions, vim modes, etc. for Bash interactive sessions.
xplr - A hackable, minimal, fast TUI file explorer
atom - Shell scripting that will knock your socks off
zoxide - A smarter cd command. Supports all major shells.
apparix - Command line directory bookmarks with jumping to bookmarks, subdirectory tab completion, distant listing etc
lf - Terminal file manager
ShellCheck - ShellCheck, a static analysis tool for shell scripts