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

Apache​Conf

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 85K
  • Win 36K
  • OS X 34K
  • Linux 16K
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 Mar 9
Windows 8 15 17 28 35 41 34 30 13 22 25 23 22 34 29 23 16 23 36 42 19 23 22 19 21 26 41 35 26 9 29 27 34 23 34 34 30 21 23 33 26 50 32 21 24 22
OS X 4 3 9 14 16 16 27 23 9 10 12 24 20 15 15 5 13 14 15 17 19 25 6 9 16 20 11 16 12 9 10 20 15 14 22 20 12 9 17 25 22 20 12 7 8 18
Linux 0 11 10 9 8 9 10 10 5 6 9 8 19 16 14 12 6 19 13 19 19 14 13 3 9 7 13 17 19 8 12 13 6 9 24 22 15 18 12 8 15 16 14 5 6 12

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.