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