trooper

Crates.iotrooper
lib.rstrooper
version0.5.0
sourcesrc
created_at2023-02-12 18:33:39.785133
updated_at2023-10-12 09:45:23.853519
descriptionAn EXPERIMENTAL file manager inspired by ranger.
homepage
repository
max_upload_size
id783381
size115,380
Vincent Uden (vincent-uden)

documentation

README

Trooper 0.4.0

Trooper is a tui file manager with VIM key bindings inspired by the great ranger.

screenshot

Features

The goal of trooper is to adhere to the unix philosophy. Do one thing and do it well, in this case that thing is managing files. Trooper is not supposed to edit files, preview files (might change my mind on this one), run files or anything which is does not aid in the goal of managing files and directories.

Implemented

  • Navigating the file system
  • Copy, cut & paste files across simultaneous running instances of trooper
  • Create bookmarks for quick access to directories
  • Renaming files
  • Persistence for bookmarks and files in the yank register
  • Cross-platform support (Linux, Windows and probably Mac)
  • Configuration file for keybindings
  • Visual mode for operating on multiple files at once

Planned

  • VIM-like repeats of commands (4dd would cut 4 files at once for example)
  • Changing the working directory of the shell when exiting trooper

Installation

Install the binary package from crates.io using Cargo with:

cargo install trooper

Configuration

Trooper will look for a config file located at .config/trooper/config.ini in your home directory. On Windows this is %USERPROFILE%\.config\trooper\config.ini with the equivalent on UNIX being ~/.config/trooper/config.ini.

The config format is a simple ini format with = accepted as the only delimiter. It maps sequences of keystrokes to actions in the program. The default configuration is located in the /assets directory. It is this configuration which is overwritten by bindings in the user condfig file.

Syntax

All keybindings are located under the two sections denoted [normal] and [visual] in the ini file. Each section specifies the actions which will be availible and through what keybinding they're accessed.

Most keys are mapped simply by the character on the keyboard. Some special keys instead have to be escaped with the same syntax as in a Vim config. The escaped versions follow below:

<lt> (<)
<gt> (>)
<Space>

Most keys can also be mapped with the ctrl modifier active. This is similarly done as in a Vim config:

<C-w> (Ctrl+w)

Dependencies

See Cargo.toml

Commit count: 0

cargo fmt