Permalink
Browse files

Merge branch 'development'

  • Loading branch information...
stephenfin committed Nov 7, 2015
2 parents 79e60a7 + 081fe3b commit 7c6077557ed0a85fa8af3582c0bb7d0ba469abab
View
@@ -1,2 +1,2 @@
-*.pyc
+*.pyc
View
@@ -2,11 +2,11 @@
# http://lint.travis-ci.org/
language: python
python:
- - "2.6" # sublime text 2
- - "3.3" # sublime text 3
+ - "2.6" # sublime text 2
+ - "3.3" # sublime text 3
before_install:
- - sudo apt-get install exuberant-ctags
- - if [[ $TRAVIS_PYTHON_VERSION == '2.6' ]]; then pip install unittest2; fi
+ - sudo apt-get install exuberant-ctags
+ - if [[ $TRAVIS_PYTHON_VERSION == '2.6' ]]; then pip install unittest2; fi
script:
- - if [[ $TRAVIS_PYTHON_VERSION == '2.6' ]]; then python -m unittest2.__main__ discover; fi
- - if [[ $TRAVIS_PYTHON_VERSION == '3.3' ]]; then python -m unittest discover; fi
+ - if [[ $TRAVIS_PYTHON_VERSION == '2.6' ]]; then python -m unittest2.__main__ discover; fi
+ - if [[ $TRAVIS_PYTHON_VERSION == '3.3' ]]; then python -m unittest discover; fi
View
@@ -1,77 +0,0 @@
-TAG FILE FORMAT
-===============
-
-When not running in etags mode, each entry in the tag file consists of a
-separate line, each looking like this in the most general case::
-
- tag_name<TAB>file_name<TAB>ex_cmd;"<TAB>extension_fields
-
-The fields and separators of these lines are specified as follows:
-
-#. Tag name
-#. Single tab character
-#. Name of the file in which the object associated with the tag is located
-#. Single tab character
-#. EX command used to locate the tag within the file; generally a search
- pattern (either ``/pattern/`` or ``?pattern?``) or line number (see
- ``−−excmd``).
- Tag file format 2 (see ``−−format``) extends this EX command under certain
- circumstances to include a set of extension fields (described below)
- embedded in an EX comment immediately appended to the EX command, which
- leaves it backward-compatible with original ``vi(1)`` implementations.
-
-A few special tags are written into the tag file for internal purposes. These
-tags are composed in such a way that they always sort to the top of the file.
-Therefore, the first two characters of these tags are used a magic number to
-detect a tag file for purposes of determining whether a valid tag file is
-being overwritten rather than a source file. Note that the name of each source
-file will be recorded in the tag file exactly as it appears on the command
-line.
-
-Therefore, if the path you specified on the command line was relative to the
-current directory, then it will be recorded in that same manner in the tag
-file. See, however, the ``−−tag−relative`` option for how this behavior can be
-modified.
-
-Extension fields are tab-separated key-value pairs appended to the end of the
-EX command as a comment, as described above. These key value pairs appear in
-the general form ``key:value``. Their presence in the lines of the tag file
-are controlled by the ``−−fields`` option. The possible keys and the meaning
-of their values are as follows:
-
-access
- Indicates the visibility of this class member, where value is specific to
- the language.
-
-file
- Indicates that the tag has file-limited visibility. This key has no
- corresponding value.
-
-kind
- Indicates the type, or kind, of tag. Its value is either one of the
- corresponding one-letter flags described under the various
- ``−−<LANG>−kinds`` options above, or a full name. It is permitted (and is,
- in fact, the default) for the key portion of this field to be omitted. The
- optional behaviors are controlled with the ``−−fields`` option.
-
-implementation
- When present, this indicates a limited implementation (abstract vs. concrete)
- of a routine or class, where value is specific to the language ("virtual" or
- "pure virtual" for C++; "abstract" for Java).
-
-inherits
- When present, value is a comma-separated list of classes from which this
- class is derived (i.e. inherits from).
-
-signature
- When present, value is a language-dependent representation of the
- signature of a routine. A routine signature in its complete form specifies
- the return type of a routine and its formal argument list. This extension
- field is presently supported only for C-based languages and does not
- include the return type.
-
-In addition, information on the scope of the tag definition may be available,
-with the key portion equal to some language-dependent construct name and its
-value the name declared for that construct in the program. This scope entry
-indicates the scope in which the tag was found. For example, a tag generated
-for a C structure member would have a scope looking like ``struct:myStruct``.
View
@@ -1,56 +1,167 @@
// Place your settings in the file "User/CTags.sublime-settings", which
// overrides the settings in here.
{
- // Enable debugging
+ // Enable debugging.
+ //
+ // When enabled, this will result in debug output being printed to the
+ // console. This can be useful for debugging issues.
"debug": false,
- // Enable autocomplete
+ // Enable auto-complete.
+ //
+ // When enabled, this turns on a basic "auto-complete" feature, similar to
+ // a very rudimentary "Intellisense(TM)". This is useful for providing
+ // better suggestions than stock Sublime Text could provide.
"autocomplete": false,
+ // Path to ctags executable.
+ //
// Alter this value if your ctags command is not in the PATH, or if using
// a different version of ctags to that in the path (i.e. for OSX).
//
// NOTE: You *should not* place entire commands here. These commands are
- // built automatically using the values below. For example:
- // GOOD: "command": "/usr/bin/ctags"
- // BAD: "command": "ctags -R -f .tags --exclude=some/path"
+ // built automatically using the values below. For example, this is OK:
+ //
+ // "command": "/usr/bin/ctags"
+ //
+ // This, on the other hand, won't work!
+ //
+ // "command": "ctags -R -f .tags --exclude=some/path"
+ //
"command": "",
- // Set to false to disable recursive search for ctag generation. This
- // translates the `-R` parameter
+ // Enable recursive searching of directories when building tag files.
+ //
+ // When enabled, this is equivalent to `-R` parameter. Set to true to
+ // enable recursive search of directories when generating tag files.
"recursive" : true,
- // Default read/write location of the tags file. This translates to the
- // `-f [FILENAME]` parameter
+ // Default read/write location of the tags file.
+ //
+ // This is equivalent to the `-f [FILENAME]` parameter. There is likely no
+ // reason to change this unless you have a large number of existing tags
+ // files you'd like to use that already have a different name. In this
+ // case perhaps consider using the 'extra_tag_files' setting instead.
"tag_file" : ".tags",
- // Additional options to pass to ctags, i.e.
- // ["--exclude=some/path", "--exclude=some/other/path", ...]
+ // Additional tag files names to search.
+ //
+ // These are searched in addition to the file name given in 'tag_file'
+ "extra_tag_files": [".gemtags", "tags"],
+
+ // Additional options to pass to ctags.
+ //
+ // Any addition options you may wish to pass to the ctags executable. For
+ // example:
+ //
+ // ["--exclude=some/path", "--exclude=some/other/path", ...]
"opts" : [],
+ // Tag "kind"s to ignore.
+ //
+ // A ctags tagfile describes a number of different "kind"s, described in
+ // tag FORMAT file found here:
+ //
+ // http://ctags.sourceforge.net/FORMAT
+ //
+ // These can be filtered (i.e. ignored). For example - 'import' statements
+ // should be ignored in Python. These are of kind "i", e.g.
+ //
+ // "type":"^i$"
//
"filters": {
"source.python": {"type":"^i$"}
},
+ // Definition "kind"s to ignore.
//
+ // This is very similar to the 'filters' option. However, this only
+ // applies to the process that is used to find a definition. All filters
+ // placed here will be used when the plugin is searching for a definition
+ // in the file.
"definition_filters": {
"source.php": {"type":"^v$"}
},
+ // Enable the ctags menu in the context menus.
+ "show_context_menus": true,
+
+ // Paths to additional tag files to include in tag search.
//
- "definition_current_first": true,
+ // This is a list of items in the following format:
+ //
+ // [["language", "platform"], "path"]
+ //
+ "extra_tag_paths": [
+ [["source.python", "windows"], "C:\\Python27\\Lib\\tags"]
+ ],
- // Show the ctags menu in the context menus
- "show_context_menus": true,
+ // Enable highlighting of selected symbol.
+ //
+ // When enabled, searched symbols will be highlighted when found. This
+ // can be irritating in some instances, e.g. when in Vintage mode. In
+ // these cases, setting this to false will disable this highlighting.
+ "select_searched_symbol": true,
- // Paths to additional tag files to include in tag search. This is a list
- // of items in the form [["language", "platform"], "path"]
- "extra_tag_paths": [[["source.python", "windows"], "C:\\Python27\\Lib\\tags"]],
+ // Set to false to not open an error dialog while tags are building
+ "display_rebuilding_message": true,
- // Additional tag files to search
- "extra_tag_files": [".gemtags", "tags"],
+ // Rank Manager language syntax regex and character sets
+ //
+ // Ex: Python 'and' ignore exp --> '\sand\s' - it must have whitespace
+ // around it so it is not part of real name: gates.Nand.evaluate()
+ "language_syntax": {
+ "splitters" : [".", "::", "->"],
+ "source.js": {
+ "member_exp": {
+ "chars": "[A-Za-z0-9_$]",
+ "splitters": ["\\."],
+ "open": ["\\{", "\\[", "\\("],
+ "close": ["\\}", "\\]" , "\\)"], //close[i] must match open[i]
+ "ignore": ["&", "\\|", "\\?", ":", "\\!", "'", "=", "\""],
+ "stop": ["\\s", ","],
+ "this": ["this", "me", "self", "that"]
+ },
+ "reference_types": {
+ "__symbol__(\\.call|\\.apply){0,1}\\s*?\\(": ["f", "fa"],
+ "\\.fire\\s*?\\(\\s*?\\[\\'\"]__symbol__\\[\\'\"\\]": [
+ "eventHandler"
+ ]
+ }
+ },
+ "source.python": {
+ //python settings inherit JavaScript, with some overrides
+ "inherit": "source.js",
+ "member_exp": {
+ "ignore": ["\\sand\\s", "\\sor\\s", "\\snot\\s", ":", "\\!",
+ "'", "=", "\""],
+ "this" : ["self"]
+ }
+ },
+ "source.java": {
+ "inherit": "source.js",
+ "member_exp": {
+ "this" : ["this"]
+ }
+ },
+ "source.cs": {
+ "inherit": "source.js",
+ "member_exp": {
+ "this" : ["this"]
+ }
+ }
+ },
- // Set to false so as not to select searched symbol (in Vintage mode)
- "select_searched_symbol": true
+ // Scope Filters
+ //
+ // Tags file may optionally contain tagfield for the scope of the tag. For
+ // example:
+ //
+ // item .\fileHelper.js 420;" vp lineno:420 scope:420:19-422:9
+ //
+ // The re is used to extract 'scope:/beginLine:beginCol-endLine:endCol/'
+ //
+ // Different tags generators may generate this non-standard field in
+ // different formats
+ "scope_re": "(\\d.*?):(\\d.*?)-(\\d.*?):(\\d.*?)"
}
View
@@ -1,15 +1,15 @@
[
- {
- "caption": "-"
- },
- {
- "command": "navigate_to_definition",
- "args": {},
- "caption": "Navigate to Definition"
- },
- {
- "command": "jump_prev",
- "args": {},
- "caption": "Jump Back"
- }
+ {
+ "caption": "-"
+ },
+ {
+ "command": "navigate_to_definition",
+ "args": {},
+ "caption": "Navigate to Definition"
+ },
+ {
+ "command": "jump_prev",
+ "args": {},
+ "caption": "Jump Back"
+ }
]
View
@@ -1,33 +1,33 @@
[
- {
- "caption": "CTags: Rebuild Tags",
- "command": "rebuild_tags"
- },
- {
- "caption": "CTags: Show Symbols (file)",
- "command": "show_symbols",
- "context": [
- {
- "key": "selector",
- "match_all": true,
- "operand": "source -source.css",
- "operator": "equal"
- }
- ]
- },
- {
- "caption": "CTags: Show Symbols (all)",
- "command": "show_symbols",
- "args": {
- "type": "multi"
+ {
+ "caption": "CTags: Rebuild Tags",
+ "command": "rebuild_tags"
},
- "context": [
- {
- "key": "selector",
- "match_all": true,
- "operand": "source -source.css",
- "operator": "equal"
- }
- ]
- }
+ {
+ "caption": "CTags: Show Symbols (file)",
+ "command": "show_symbols",
+ "context": [
+ {
+ "key": "selector",
+ "match_all": true,
+ "operand": "source -source.css",
+ "operator": "equal"
+ }
+ ]
+ },
+ {
+ "caption": "CTags: Show Symbols (all)",
+ "command": "show_symbols",
+ "args": {
+ "type": "multi"
+ },
+ "context": [
+ {
+ "key": "selector",
+ "match_all": true,
+ "operand": "source -source.css",
+ "operator": "equal"
+ }
+ ]
+ }
]
Oops, something went wrong.

0 comments on commit 7c60775

Please sign in to comment.