ApacheConf
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 126K
- Win 58K
- Mac 45K
- Linux 24K
| 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 | Dec 3 | Dec 2 | Dec 1 | Nov 30 | Nov 29 | Nov 28 | Nov 27 | Nov 26 | Nov 25 | Nov 24 | Nov 23 | Nov 22 | Nov 21 | Nov 20 | Nov 19 | Nov 18 | Nov 17 | Nov 16 | Nov 15 | Nov 14 | Nov 13 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 0 | 2 | 1 | 0 | 1 | 3 | 2 | 2 | 1 | 0 | 0 | 1 | 3 | 3 | 2 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 2 | 2 | 2 | 2 | 0 | 2 | 2 | 1 | 0 | 0 | 1 | 1 | 2 | 1 | 3 | 1 | 0 | 3 | 3 |
| Mac | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 2 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | 2 | 1 | 0 | 0 | 2 | 1 | 0 | 0 | 1 | 0 | 1 | 3 | 0 | 0 | 0 | 2 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | 2 |
| Linux | 0 | 0 | 1 | 2 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 3 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 2 | 3 |
Readme
- Source
- raw.githubusercontent.com
Apache Conf Syntax Highlighting
Supported filetypes
- .conf
- .htaccess
- .htgroups
- .htpasswd
Installation
Using Package Control, install “ApacheConf” or clone this repo in your packages folder.
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.