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

Apache​Conf.​tm​Language

For htaccess and .conf files. By GreyWyvern, with assist by radiosilence. <http://www.sublimetext.com/forum/viewtopic.php?f=5&t=856>.

Details

Installs

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

Readme

Source
raw.​githubusercontent.​com

Apache Conf Syntax Highlighting

Supported filetypes

  • .conf
  • .htaccess
  • .htgroups
  • .htpasswd

Installation

  1. Using Package Control, install “ApacheConf”

Or:

  1. Open the Sublime Text Packages folder
- OS X: ~/Library/Application Support/Sublime Text 3/Packages/
- Windows: %APPDATA%/Sublime Text 3/Packages/
- Linux: ~/.Sublime Text 3/Packages/
  1. clone this repo

Sublime Text 2

  1. Open the Sublime Text 2 Packages folder
  2. clone this repo, but use the st2 branch

    git clone -b st2 git@github.com:colinta/ApacheConf.tmLanguage

Credits

I came across the ApacheConf plugin after a quick search for “Sublime Text Apache”, but only after first checking Package Control, which we all know is a stellar package manager by any standards.

The page I found is here: http://www.sublimetext.com/forum/viewtopic.php?f=5&t=856

GreyWyvern spearheaded the language grammar, with radiosilence jumping in with a quick whitespace fix. Or, that's what I gathered from the forum.

I grabbed the files, threw them into a git repo, and published them on my account, trying my dangdest to give credit where credit is due.

If there is an issue, yes of course do due diligence and add an issue, but PLEASE consider forking and submitting a pull request, since I'm not big on these language grammar deals. I'll do what I can, but I'm really hoping GreyWyvern takes over this package.