3 ms·

I like it that the command line is a bit "realistic" but allowing to get the last command via arrow-up. Unfortunately, there is no tab autocompletion, which ma

by vog 12y ago

I like it that the command line is a bit "realistic" but allowing to get the last command via arrow-up. Unfortunately, there is no tab autocompletion, which makes it really a hassle to enter "git add [specific file]" and similar commands. I also like the idea of simulating the timing, such that the commands don't always return immediately. However, I'm a bit surprised about the exact timing values. For example, "git init" took quite some time while "git status" was really quick. In reality, it is the other way around.

Gazler 12y ago
I wrote something a few years ago that does a similar thing using a real command line. https://github.com/Gazler/githug https://github.com/Gazler/githug
blaze33 12y ago
> a hassle to enter "git add [specific file]" `git add .` worked as well and clicking the command autoenters it at the prompt.
insertnickname 12y ago
Maybe it's just slow... `git status` should be quick in an empty repo.
farnsworth 12y ago
It's all very slow for me right now - every command hits the server, which is disappointing.
tsm 12y ago
The truth is both are blazing fast, but at least on my machine git status is a hair faster: $ mkdir baz $ cd baz $ time git init Initialized empty Git repository in ~/src/tmp/baz/.git/ real 0m0.015s user 0m0.002s sys 0m0.008s $ time git status # On branch master # # Initial commit # nothing to commit (create/copy files and use "git add" to track) real 0m0.012s user 0m0.002s sys 0m0.003s
- joelg236 12y ago
  Interestingly, for me git init took 0.045s, while status took 0.005s. I wonder what factors into this.
  - TimWolla 12y ago
    For an existing repository: Size of the repository, as well as the number of files in the folder. A single git status on a 1.7GB git repository takes about 9 seconds with a warm disk cache on my workstation.

by vog 12y ago

Gazler 12y ago

I wrote something a few years ago that does a similar thing using a real command line. https://github.com/Gazler/githug https://github.com/Gazler/githug

blaze33 12y ago

> a hassle to enter "git add [specific file]" `git add .` worked as well and clicking the command autoenters it at the prompt.

insertnickname 12y ago

Maybe it's just slow... `git status` should be quick in an empty repo.

farnsworth 12y ago

It's all very slow for me right now - every command hits the server, which is disappointing.

tsm 12y ago

The truth is both are blazing fast, but at least on my machine git status is a hair faster: $ mkdir baz $ cd baz $ time git init Initialized empty Git repository in ~/src/tmp/baz/.git/ real 0m0.015s user 0m0.002s sys 0m0.008s $ time git status # On branch master # # Initial commit # nothing to commit (create/copy files and use "git add" to track) real 0m0.012s user 0m0.002s sys 0m0.003s

joelg236 12y ago
Interestingly, for me git init took 0.045s, while status took 0.005s. I wonder what factors into this.
- TimWolla 12y ago
  For an existing repository: Size of the repository, as well as the number of files in the folder. A single git status on a 1.7GB git repository takes about 9 seconds with a warm disk cache on my workstation.