base on A new way to see and navigate directory trees : https://dystroy.org/broot ## Broot [![Tests][s3]][l3] [![MIT][s2]][l2] [![Latest Version][s1]][l1] [![Chat on Miaou][s4]][l4] [![Packaging status][srep]][lrep] [s1]: https://img.shields.io/crates/v/broot.svg [l1]: https://crates.io/crates/broot [s2]: https://img.shields.io/badge/license-MIT-blue.svg [l2]: LICENSE [s3]: https://github.com/Canop/broot/actions/workflows/tests.yml/badge.svg [l3]: https://github.com/Canop/broot/actions/workflows/tests.yml [s4]: https://miaou.dystroy.org/static/shields/room.svg [l4]: https://miaou.dystroy.org/3490?broot [srep]: https://repology.org/badge/tiny-repos/broot.svg [lrep]: https://repology.org/project/broot/versions Broot is a better way to navigate directories, find files, and launch commands.  [**Complete Documentation**](https://dystroy.org/broot/) - [**Installation Instructions**](https://dystroy.org/broot/install/) - [**Contributing or Getting Help**](https://dystroy.org/blog/contributing/) ## Get an overview of a directory, even a big one Hit `br -s`  Notice the *unlisted*? That's what makes it usable where the old `tree` command would produce pages of output. `.gitignore` files are properly dealt with to put unwanted files out of your way. As you sometimes want to see gitignored files, or hidden ones, you'll soon get used to the <kbd>alt</kbd><kbd>i</kbd> and <kbd>alt</kbd><kbd>h</kbd> shortcuts to toggle those visibilities. (you can ignore them though, see [documentation](https://dystroy.org/broot/navigation/#toggles)). ## Find a directory then `cd` to it type a few letters  Hit <kbd>alt</kbd><kbd>enter</kbd> and you're back to the terminal in the desired location. This way, you can navigate to a directory with the minimum amount of keystrokes, even if you don't exactly remember where it is. Broot is fast and doesn't block (any keystroke interrupts the current search to start the next one). Most useful keys for this: * the letters of what you're looking for * <kbd>enter</kbd> on the root line to go up to the parent (staying in broot) * <kbd>enter</kbd> to focus a directory (staying in broot) * <kbd>esc</kbd> to get back to the previous state or clear your search * <kbd class=b>↓</kbd> and <kbd class=b>↑</kbd> may be used to move the selection * <kbd>alt</kbd><kbd>enter</kbd> to get back to the shell having `cd` to the selected directory * <kbd>alt</kbd><kbd>h</kbd> to toggle showing hidden files (the ones whose name starts with a dot) * <kbd>alt</kbd><kbd>i</kbd> to toggle showing gitignored files * `:q` if you just want to quit (you can use <kbd>ctrl</kbd><kbd>q</kbd> if you prefer) ## Never lose track of file hierarchy while you search  Broot tries to select the most relevant file. You can still go from one match to another one using <kbd>tab</kbd> or arrow keys. You may also search with a regular expression. To do this, add a `/` before the pattern. And you have [other types of searches](input/#the-filtering-pattern), for example searching on file content (start with `c/`):  You may also apply logical operators or combine patterns, for example searching `test` in all files except json ones could be `!/json$/&c/test` and searching `carg` both in file names and file contents would be `carg|c/carg`. Once the file you want is selected you can * hit <kbd>enter</kbd> (or double-click) to open it in your system's default program * hit <kbd>alt</kbd><kbd>enter</kbd> to open it in your system's default program and close broot * hit <kbd>ctrl</kbd><kbd>→</kbd> to preview it (and then a second time to go inside the preview) * type a verb. For example `:e` opens the file in your preferred editor (which may be a terminal one) [blog: a broot content search workflow](https://dystroy.org/blog/broot-c-search/) ## Manipulate your files Most often, when not using broot, you move your files in the blind. You do a few `ls` before, then your manipulation, and maybe you check after. You can instead do it without losing the view of the file hierarchy.  Move, copy, rm, mkdir, are built in and you can add your own shortcuts. Here's chmod:  ## Manage files with panels When a directory is selected, do <kbd>ctrl</kbd><kbd>→</kbd> and you open another panel (you may open other ones, or navigate between them, with <kbd>ctrl</kbd><kbd>←</kbd> and <kbd>ctrl</kbd><kbd>→</kbd>).  (yes, colors are fully customizable) You can for example copy or move elements between panels:  If you like you may do it Norton Commander style by binding `:copy_to_panel` to <kbd>F5</kbd> and `:move_to_panel` to <kbd>F6</kbd>. ## Preview files Hit <kbd>ctrl</kbd><kbd>→</kbd> when a file is selected and the preview panel appears.   The preview panel stays synchronized with the selection in tree panels. Broot displays images in high resolution when the terminal supports Kitty's graphics protocol (compatible terminals: [Kitty](https://sw.kovidgoyal.net/kitty/index.html), [WezTerm](https://wezfurlong.org/wezterm/)):  ## Apply a standard or personal command to a file  Just find the file you want to edit with a few keystrokes, type `:e`, then <kbd>enter</kbd>. You can add verbs or configure the existing ones; see [documentation](https://dystroy.org/broot/conf_file/#verbs-shortcuts-and-keys). And you can add shortcuts, for example a <kbd>ctrl</kbd> sequence or a function key ## Apply commands on several files Add files to the [staging area](staging-area) then execute any command on all of them.  ## Replace `ls` (and its clones): If you want to display *sizes*, *dates* and *permissions*, do `br -sdp` which gets you this:  You may also toggle options with a few keystrokes while inside broot. For example you could have typed this `-sdp` while in broot. Or hit <kbd>alt</kbd><kbd>h</kbd> and you see hidden files. ## Sort, see what takes space: You may sort by launching broot with `--sort-by-size` or `--sort-by-date`. Or you may, inside broot, type a space, then `sd`, and <kbd>enter</kbd> and you toggled the `:sort_by_date` mode. When sorting, the whole content of directories is taken into account. So if you want to find on Monday morning the most recently modified files, launch `br --sort-by-date ~`. If you start broot with the `--whale-spotting` option (or its shortcut `-w`), you get a mode tailored to "whale spotting" navigation, making it easy to determine what files or folders take space. Sizes, dates, files counts, are computed in the background, you don't have to wait for them when you navigate.  And you keep all broot tools, like filtering or the ability to delete or open files and directories. If you hit `:fs`, you can check the usage of all filesystems, so that you focus on cleaning the full ones.  ## Check git statuses: Use `:gf` to display the statuses of files (what are the new ones, the modified ones, etc.), the current branch name and the change statistics.  And if you want to see *only* the files which would be displayed by the `git status` command, do `:gs`. From there it's easy to edit, or diff, selected files.  From there it's easy to edit, diff, or revert selected files. [blog: use broot and meld to diff before commit](https://dystroy.org/blog/gg/) ## Further Reading See **[Broot's web site](https://dystroy.org/broot)** for instructions regarding installation and usage. ", Assign "at most 3 tags" to the expected json: {"id":"1277","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"