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,343 public repositories matching this topic...

bat
sharkdp
sharkdp commented Oct 3, 2020

With all the recent news about Hacktoberfest I thought it would be a good idea to point out good beginner issues that would be actually helpful for bat. In the past years, I have actually experienced Hacktoberfest as a really great event - both as a contributor as well as a maintainer.

As of recently, bat has a set of syntax highlighting regress

cli
tierninho
tierninho commented Sep 11, 2020

Describe the feature or problem you’d like to solve

When running gh pr checks the user is shown a bunch of urls for each check. It would be great to add a -w to see the checks tab ([repo/owner]/pull/[pr-number]/checks) in github.com. The user could then scroll through the various checks shown in the output of the gh pr checks.

Proposed solution

How will it benefit CLI and it

dpacbach
dpacbach commented Jun 13, 2020

Hello,

In the two menus containing "destructive" actions (d and D) can we have the "cancel" item first in the list? That way one doesn't accidentally hit enter and nuke their tree. Especially important since when you select one of those destructive actions there is not an "are you sure?" box that pops up. I think that the best solution which will keep the UI streamlined but make it a tad

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.