Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

revert fenced code blocks in README

Reverts some of b063d38

The bash syntax highlighting isn't making these code blocks any more
readable and makes the raw text file much uglier. The highlighting is
more distracting than anything.
  • Loading branch information...
commit ed8a1ab7c47a0057efdac3e9c360396ce6a3069a 1 parent 185f98a
@rtomayko authored
Showing with 19 additions and 36 deletions.
  1. +19 −36 README.markdown
View
55 README.markdown
@@ -24,55 +24,42 @@ Installation
Install the most recent available version under `/usr/local`:
-```bash
-$ git clone git://github.com/rtomayko/git-sh.git
-$ cd git-sh
-$ make
-$ sudo make install
-```
+ $ git clone git://github.com/rtomayko/git-sh.git
+ $ cd git-sh
+ $ make
+ $ sudo make install
Start a shell with `git-sh`:
-```bash
-$ git-sh
-master!git-sh> help
-```
+ $ git-sh
+ master!git-sh> help
Use the `PREFIX` environment variable to specify a different install location.
For example, under `~/bin`:
-```bash
-$ make install PREFIX=~
-```
+ $ make install PREFIX=~
Basic Usage
-----------
Typical usage is to change into a git working copy and then start the shell:
-```bash
-$ cd mygreatrepo
-$ git sh
-master!mygreatrepo> help
-```
+ $ cd mygreatrepo
+ $ git sh
+ master!mygreatrepo> help
Core git commands and git command aliases defined in `~/.gitconfig` can be
used as top-level commands:
-```bash
-master!mygreatrepo> checkout -b new
-new!mygreatrepo> log -p
-new!mygreatrepo> rebase -i HEAD~10
-```
+ master!mygreatrepo> checkout -b new
+ new!mygreatrepo> log -p
+ new!mygreatrepo> rebase -i HEAD~10
It's really just a normal bash shell, though, so all commands on `PATH` and any
aliases defined in `~/.bashrc` are also available:
-```bash
-new!mygreatrepo> ls -l
-new!mygreatrepo> vim somefile
-```
-
+ new!mygreatrepo> ls -l
+ new!mygreatrepo> vim somefile
*IMPORTANT: `rm`, `mv`, and `diff` are aliased to their git counterparts. To use system versions,
run `command(1)` (e.g., `command rm`) or qualify the command (e.g. `/bin/rm`).*
@@ -89,18 +76,14 @@ The git-sh prompt includes ANSI colors when the git `color.ui` option is
enabled. To enable git-sh's prompt colors explicitly, set the `color.sh` config
value to `auto`:
-```bash
-$ git config --global color.sh auto
-```
+ $ git config --global color.sh auto
Customize prompt colors by setting the `color.sh.branch`, `color.sh.workdir`,
and `color.sh.dirty` git config values:
-```bash
-$ git config --global color.sh.branch 'yellow reverse'
-$ git config --global color.sh.workdir 'blue bold'
-$ git config --global color.sh.dirty 'red'
-```
+ $ git config --global color.sh.branch 'yellow reverse'
+ $ git config --global color.sh.workdir 'blue bold'
+ $ git config --global color.sh.dirty 'red'
See [colors in git](http://scie.nti.st/2007/5/2/colors-in-git) for information.
Please sign in to comment.
Something went wrong with that request. Please try again.