Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Command line tools for productive programmers

earthly.dev

Post reply on HN
Print view View original

21–30 of 143 posts

Re: Command line tools for productive programmers

#21

Post by scns »

gonehome wrote: post #11
xrayarx wrote: post #3

6 tools: - broot - like tree - funky - like direnv - fzf - fuzzy finder - mcfly - cli completion - zoxide - like cd - gitupdate - auto commit and push The author references this discussion https://lobste.rs/s/yfgwjr/what_interesting_command_line_too...

I'd also add ncdu - which is really great when you need to easily see what's eating up disk space. jq is also super nice when you have to parse json data. I also like powerlevel10k: https://github.com/romkatv/powerlevel10k

powerlevel10k looks interesting with that builtin configuration wizard. I use https://starship.rs

You have to configure it yourself, but it works on bash, fish and zsh.

Re: Command line tools for productive programmers

#23

Post by sandreas »

scns wrote: post #8

For his usecase of funky i use ~/.bash_aliases, that way i can easily share them between machines. Eg to quickly add a new one: alias als="nvim $HOME/.bash_aliases && source $HOME/.bash_aliases" Be careful with quoting though, got myself into a situation where every new terminal asked for the root password. Shellcheck found the reason quickly. (edit) Another benefit is that those aliases abstract over differences of…

Instead of creating aliases for .., I use this:

  function ..() { 
    for i in $(seq 1 $1); do cd ..; done 
  }
which enables

  ..    # up 1 dir
  .. 2  # up 2 dirs
  .. 42 # up 42 dirs
Here are some more: https://pilabor.com/blog/2021/03/unix-shell-tricks/

Re: Command line tools for productive programmers

#24

Post by awestroke »

wruza wrote: post #20
indianboy42 wrote: post #16

Earlier quoted context omitted.

Use broot as tree is not necessary of course `tree | less` works for that but as hinted in the article broot contains a lot more features. Fuzzy finding, preview, multiwindow copy/paste, renaming, directory navigation etc

Does it contain emacs? That would be nice.

What would be nice about that?

Re: Command line tools for productive programmers

#26

Post by asicsp »

wruza wrote: post #19

Brains recently got underrated. The way mcfly works is cool, but it offloads your habits to some “neural network” that you can’t control. There is not many methods slower than looking at unpredictable line-by-line output and almost nothing more anxious than a possibility of false choice done without thinking. This tool basically replaces a deterministic mismatch with a non-deterministic one. Your brain is good at pre…

>history-search-{for,back}ward in their .inputrc for up-down keys

Once I found this, I rarely use Ctrl+R since most of the time I'm searching based on starting command name.

If I'm using something a lot of times, it gets added as alias/function. I also maintain a file with commands that I think may be useful later, easier to search that compared to online search.

Re: Command line tools for productive programmers

#27

Post by lostmsu »

mlang23 wrote: post #25

The one cli tool that saves me the most time is "gh", and its predecessor "hub". Not having to interact with a website to submit a PR, issue, or just fork a repo, is a blessing. I wish more sites would ship a cannonicla tool to use their APIs...

Re: forking a repo.

How do you type name into the terminal?

Re: Command line tools for productive programmers

#29

Post by lostmsu »

xrayarx wrote: post #3

6 tools: - broot - like tree - funky - like direnv - fzf - fuzzy finder - mcfly - cli completion - zoxide - like cd - gitupdate - auto commit and push The author references this discussion https://lobste.rs/s/yfgwjr/what_interesting_command_line_too...

I just read the description of funky, and it is like Windows 98 CD-ROM autorun.exe, but the next level. If you clone my repo and enter the directory - I own your system. Funky indeed.
Post reply on HN