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
| Mar 2 | Mar 1 | Feb 28 | Feb 27 | Feb 26 | Feb 25 | Feb 24 | Feb 23 | Feb 22 | Feb 21 | Feb 20 | Feb 19 | Feb 18 | Feb 17 | Feb 16 | Feb 15 | Feb 14 | Feb 13 | Feb 12 | Feb 11 | Feb 10 | Feb 9 | Feb 8 | Feb 7 | Feb 6 | Feb 5 | Feb 4 | Feb 3 | Feb 2 | Feb 1 | Jan 31 | Jan 30 | Jan 29 | Jan 28 | Jan 27 | Jan 26 | Jan 25 | Jan 24 | Jan 23 | Jan 22 | Jan 21 | Jan 20 | Jan 19 | Jan 18 | Jan 17 | Jan 16 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 0 | 2 | 0 | 2 | 1 | 0 | 2 | 6 | 1 | 2 | 2 | 3 | 2 | 4 | 2 | 2 | 2 | 1 | 1 | 2 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 2 | 4 | 0 | 5 | 0 | 2 | 3 | 2 | 1 | 1 | 1 | 0 | 2 | 1 | 3 |
| Mac | 0 | 2 | 1 | 1 | 1 | 5 | 2 | 0 | 3 | 0 | 0 | 0 | 1 | 0 | 4 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 2 | 0 | 2 | 2 | 2 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 |
| Linux | 0 | 2 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 2 | 3 | 0 | 1 | 1 | 5 | 2 | 3 | 2 | 2 | 2 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 3 | 0 | 0 | 2 | 1 | 0 | 1 | 1 | 1 | 0 | 3 | 1 | 0 | 1 | 0 | 0 | 2 | 1 |
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.