ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Git​Syntaxes

by vovkkk ST2/ST3

Highlighting for git files in Sublime Text

Details

Installs

  • Total 5K
  • Win 2K
  • OS X 2K
  • Linux 1K
Apr 23 Apr 22 Apr 21 Apr 20 Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 Apr 12 Apr 11 Apr 10 Apr 9 Apr 8 Apr 7 Apr 6 Apr 5 Apr 4 Apr 3 Apr 2 Apr 1 Mar 31 Mar 30 Mar 29 Mar 28 Mar 27 Mar 26 Mar 25 Mar 24 Mar 23 Mar 22 Mar 21 Mar 20 Mar 19 Mar 18 Mar 17 Mar 16 Mar 15 Mar 14 Mar 13 Mar 12 Mar 11 Mar 10
Windows 0 0 0 0 1 2 1 0 4 0 2 1 3 2 1 1 0 0 0 1 1 0 2 3 0 1 2 0 2 0 0 2 0 0 1 0 1 2 0 1 1 1 0 0 3
OS X 0 0 1 0 1 0 2 3 0 0 0 0 2 2 0 0 0 1 1 0 1 0 0 0 0 1 0 0 1 0 0 0 1 1 0 1 1 0 0 1 1 1 0 2 0
Linux 0 0 1 0 1 0 0 0 0 0 0 1 2 1 1 1 0 0 0 2 0 1 0 0 1 0 0 0 0 1 1 0 0 0 0 0 1 0 1 0 0 1 0 1 0

Readme

Source
raw.​githubusercontent.​com

Git Syntaxes

Syntax Highlighting for SublimeText

Features

  • Highlight all Git files (gitconfig, gitattributes, commit message, interactive rebase todo)
  • Toggle comments in all files above with default keystroke whatever it is (usually ctrl + /)
  • Many scopes, e.g. you can set separate colour for every command in rebase file (i.e. pick, fixup, etc.)

Customisation

Sublime Text supports per-syntax settings, for instance, you may want to enable spell check whenever write commit message, or make a font size bigger, or maybe even use completely different colour scheme — all these possible.

Create files:

  1. For commits Packages/User/commit-message.sublime-settings
  2. For rebase Packages/User/rebase.sublime-settings

Content of those files:

{
    "spell_check": true,
    "font_size": 22
}

For available settings look at Preferences → Settings — Default (note, some settings are global and cannot be syntax-specific, e.g. "font_options").

How to use ST as editor for Git

Note for Windows, you must have Build 3065 or later to have command line support, or just add the folder into PATH and call sublime_text instead of subl

  • Mac / Linux: subl -n -w
  • Windows: subl.exe -n -w

Preferred method: edit .bashrc

This will allow for more editing options than just the git commit, like editing diffs. This also leaves flexibility as it can be easily overridden, by the .gitconfig for example. Add the following to your .bashrc: On Mac and Linux:

export EDITOR="subl -n -w"

Alternate method: amend your .gitconfig

You can run the following command to let git update your .gitconfig

git config --global core.editor 'subl -n -w'

Or add the following line manually to your .gitconfig “ [core] editor = 'subl -n -w'

You also can hide menu (as on screenshot above) and tabs:

    editor = "sublime_text -n -w --command toggle_menu --command toggle_tabs"


## SFAQ
### Aren’t there similar packages for those syntaxes? Why another one? Why not contribute into existing one?
I’ve [tried](https://github.com/adambullmer/sublime_git_commit_syntax/pull/1) with no luck, or any feedback.
So this package is an attempt (the first one, in fact) to bring all related syntaxes in one place.

### But what about Git, GitSavvy and many others?
Those packages add integration in an IDE fashion — so you call git from-within Sublime Text.  
This package does an opposite thing — make stuff more readable whenever you call ST from-within git, so ST remains an editor with extra features rather than IDE.

### Are you interested in pull requests or collaboration in general?
Sure, absolutely.

### What is ‘s’ in SFAQ for?
<b>S</b>upposedly frequently asked questions.

### Do you even push-up?
Nope.

## Credits
* Commit definitions are provided by [Josh Goebel](https://github.com/yyyc514)
* Base for Config definitions is borrowed from <https://github.com/textmate/git.tmbundle>

<hr>

All sources under [MIT](LICENSE)