What CLI Apps do you use?

elfprince

htop
nano
du/df
imagemagick/convert
ufw
youtube-dl
occasionally other stuff

johano

Two favourites:

`fzf` (in repo)

Command line fuzzy finder.

More information: https://github.com/junegunn/fzf.

`marker`

https://github.com/pindexis/marker

Marker is a command palette for the terminal. It lets you bookmark commands (or commands templates) and easily retreive them with the help of a real-time fuzzy matcher.

It's also shipped with many commands common usage (thanks to tldr).

New and interesting to me

Taken from your posts above. Thanks, folks!

micro - An excellent replacement for nano, which I didn't expect to be changing. Love it!

mdless - will check this out too

Girtablulu

micro
rsync
solt
git
youtube-dl

brent

@elfprince "occasionally other stuff"---yeah feel like I'm forgetting some things, too

brent

On and off-topic here, lo siento:

To add to discussion I love CLI for reading MAN pages. Love the documentation.
To subtract from subject: can man pages be read in any other applications?

seagle

brent the answer to your question is inside the man pages of man! 😃

       -P pager, --pager=pager
              Specify  which output pager to use.  By default, man uses less, falling back to cat if less is not found or is not executable.  This option overrides the $MANPAGER environment vari‐
              able, which in turn overrides the $PAGER environment variable.  It is not used in conjunction with -f or -k.

              The value may be a simple command name or a command with arguments, and may use shell quoting (backslashes, single quotes, or double quotes).  It may not use pipes to connect multi‐
              ple commands; if you need that, use a wrapper script, which may take the file to display either as an argument or on standard input.

polomi

ledger. I haven't found a GUI replacement that I was ever satisfied with. I use it for personal finance and budgeting.

brent

seagle Thank you. Man pages of man is too funny.

johano

A few more, all available from the Solus repo:

fd easier and way faster than find - https://github.com/sharkdp/fd
ripgrep easy and way faster than grep - https://github.com/BurntSushi/ripgrep
exa a very nice companion to ls - https://github.com/ogham/exa
autojump I've been using fzf for quick jumping around folders, but this utility is really excellent. (Bash users check the note about $PROMPT_COMMAND under Known Issues. Once .bashrc is sorted it works like a charm :-) - https://github.com/wting/autojump
bat a nice companion to cat - https://github.com/sharkdp/bat

johano

Came across this one today, and—have played around with it, excellent!—it's quickly going to be indispensable.

broot

broot for navigating directories, finding, opening files, etc.

https://dystroy.org/broot/

or on github at https://github.com/Canop/broot

You can use a static binary, I put it in ~/bin, it creates ~/.config/broot, so easy to manage.

(Not sure if I should have started a new post as this is old, but this seems a logical place for it?)

viyoriya

new one called bashtop 3.5k lines of bash script single file 😀 uses more memory still looks good in terminal.

https://github.com/aristocratos/bashtop

algent

viyoriya This app is getting popularity recently.

Juankz

thefuck is so useful, every time you write a command wrong you type fuck and it corrects it. Like

$ epogk up
command not found: epogk
$ fuck
eopkg up [enter/↑/↓/ctrl+c]

If you don't like the word, you can create an alias for it, like please

viyoriya

algent Brootas well... I used ranger

tomocafe

Editing
vim / view
sed - search/replace, especially on streams
pandoc - document converter

File management
ls - list files and directories
find - find files recursively
tar - compress/extract archives
df - check disk usage
du - check disk usage per file(s)
ln - create symbolic links

Searching text
ack / ag - better than grep for searching source code
My custom wrapper around the above: search
grep - simple searches not on source code
diff - compare files, create patches
vimdiff - compare files side by side

Process management
top - see system resource usage in real time
ps - detailed process information
kill - kill processes
pstree - print a process tree, showing parent/child relationships
xargs - tokenizes text, but I generally use it to parallelize tasks (xargs -P)

Password management
gopass

Development
git - revision control
gdb / cgdb - debugger
gcc et al - C/C++ compiler
make / m4 et al - GNU make tools
ninja - meson tools
python
rustc
perl

Network
ssh - connect to remote machines
nmcli - network manager CLI (e.g. connect to a Wi-Fi network)

Shell
My shell of choice is bash. Some builtins I commonly use:
which - get the path of a command in your $PATH
history - history of issued commands, use !n to repeat command n
pushd / popd - push/pop to directory stack
bg / fg / jobs / & - job control, move from foreground to background and vice-versa
&& / || - chain commands together based on last command's return value
!! - repeat last command, especially sudo !!
!$ - repeat last argument
Some custom commands I made:
dc - cd backwards, with tab completion up the directory tree
mcd - make and change to directory in one shot
hc - hard copy, replacing symbolic link

Solus-specific
eopkg
solbuild - for building packages
arc - arcanist (revision control)

Miscellaneous
man - RTFM
clear - clears the terminal (I am neurotic about this)

Justin

tomocafe

clear - clears the terminal (I am neurotic about this)

alias c='clear'
alias cdc='cd ~ && clear'

I'm also pretty neurotic about it 😀

tomocafe

Justin

If you use bash, setting this would avoid polluting your history with lots of clear (or c in your case) calls

export HISTIGNORE="clear" # colon separated list

Justin

tomocafe I do use bash but I'm not too worried about my history, thanks for the tip though.

brent

Justin tomocafe
Mildly anxietic about clutter and redundant bytes--when I'm in the mood😉. Shrewd about space and resources, too.
does CLEAR command therefore nullify (destroy) terminal HISTORY then?
Or what?
graci

tomocafe

brent No, it doesn’t really save you anything on resources. It just removes all the lines from previous commands and starts fresh. Try ls then clear and you’ll see what it does.

I only brought up history because it logs all the commands you issue, and I type clear like every 4 commands, so my history would be full of clear which is not really useful when searching through history.

brent

tomocafe gotcha---it clears out a long terminal session in front of your eyeballs so you don't have to kill it and open new terminal. doesn't kill history then. It's the visual/mental effect of always starting fresh, as it were were--a new palette. Thank you.

« Previous Page