https://gitlab.com/christosangel/basht
This tui file manager bash script, provides image preview, theme selection, smooth directory navigation, opening files with default and other programs and easy configuring of keybindings. It uses fzf
to navigate to and select files and directories. Image rendering can be done with the use of ueberzug, kitty terminal or chafa.
The script also provides content preview for directories, and text files:
As one can see in the screenshots, thanks to Nerd Fonts, each type of selection (directory, text file, office document, image file etc) is represented with the respective symbol.
Configuring of preferences can be done through editing a psv file.
Any feedback / suggestion will be appreciated.
You still need a terminal emulator capable of displaying images, though, right? Like Kitty, Allacrity won’t do the trick.
Kitty supports images, not sure about alacritty, although there are many competing protocols for image display in a terminal emulator, so it could be that it just doesn’t support a particular program.
idk, i’ve heard that ranger works in alacritty with image previews, so this could too.
Is there a reason to use this over Ranger? Nice work still
Hey, curious why your themes need to be dot txt files?
Well, there is just one
themes.txt
file, created inside.config/basht/
directory. There is no particular reason why it should not be a.txt
. Would you suggest another solution?.txt would imply the file is just some prose. A theme file might be better named with a .theme extension, so as to better communicate the nature of the file.
Well, after a quick search, from that source, I found that :
…A .theme file is a .ini text file that is divided into sections, which specify visual elements that appear on a Windows desktop. Section names are wrapped in brackets ([]) in the .ini file.
I believe that the
themes.txt
file has not much to do with the above, furthermore, confusion between the two does not sound a good idea. What is more, one can say that file names such asthemes.txt
andcurrent_theme.txt
are quite descriptive and leave no doubts about their function. However, I think I understand your point of view. Perhaps I would consider renaming these in the future.which specify visual elements that appear on a Windows desktop
So that definition has no weight for Linux -case closed.
If you dev for Linux, you don’t need a file extension for text files!