Skip to content
#

Command line interface

Before there were graphical user interfaces, command-line interfaces were used to issue commands to a computer. Programs that handle the user interface are called command language interpreters, often known as a shell. A CLI may give a user more control over the computer and programs they wish to execute.

Here are 19,167 public repositories matching this topic...

bat
MuratUrsavas
MuratUrsavas commented Sep 17, 2020

I'm using Git submodules for managing my libraries and they are generally nested. For committing a parent repo I generally need to enter three submodules individually and then enter same or similar commit messages. Normally I was copying the commit message and apply all other remaining repos while using other GUI's. But Lazygit does not allow me to do it. Shift + Arrow does not work. Mouse drag ju

sharkdp
sharkdp commented May 25, 2020

I see a lot of fd users that seem to think that they need to add "{}" to all commands. Some users also seem to think that the closing semicolon (which needs to be escaped) \; is required:

fd … -x command "{}" \;

In reality, 90% of the --exec use cases can be written without the "{}" part (which fd adds, if it is ommitted) because the file entry often comes last. The semic

fx
antonmedv
antonmedv commented Dec 11, 2019

Currently, each argument to fx treated as an anonymous function. Here is an example:

fx 'groupBy("commit.author.name")' 'mapValues(size)' toPairs 'sortBy(1)' reverse 'take(10)' fromPairs

But this requires a lot of ' quotes. My idea is to split the argument by whitespaces . So next will be possible to write:

fx 'groupBy("commit.author.name") mapValues(size) toPairs so

Created by Glenda Schroeder

Released 1965

Wikipedia
Wikipedia
You can’t perform that action at this time.