Skip to content

Commit 458b4f8

Browse files
committed
Merge pull request #161 from stephenfin/python3-update
Python3 Update & General Refactoring of Codebase
2 parents a879f96 + c973327 commit 458b4f8

24 files changed

+1899
-3817
lines changed

CTAGS_README.rst

+77
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
TAG FILE FORMAT
2+
===============
3+
4+
When not running in etags mode, each entry in the tag file consists of a
5+
separate line, each looking like this in the most general case::
6+
7+
tag_name<TAB>file_name<TAB>ex_cmd;"<TAB>extension_fields
8+
9+
The fields and separators of these lines are specified as follows:
10+
11+
#. Tag name
12+
#. Single tab character
13+
#. Name of the file in which the object associated with the tag is located
14+
#. Single tab character
15+
#. EX command used to locate the tag within the file; generally a search
16+
pattern (either ``/pattern/`` or ``?pattern?``) or line number (see
17+
``−−excmd``).
18+
Tag file format 2 (see ``−−format``) extends this EX command under certain
19+
circumstances to include a set of extension fields (described below)
20+
embedded in an EX comment immediately appended to the EX command, which
21+
leaves it backward-compatible with original ``vi(1)`` implementations.
22+
23+
A few special tags are written into the tag file for internal purposes. These
24+
tags are composed in such a way that they always sort to the top of the file.
25+
Therefore, the first two characters of these tags are used a magic number to
26+
detect a tag file for purposes of determining whether a valid tag file is
27+
being overwritten rather than a source file. Note that the name of each source
28+
file will be recorded in the tag file exactly as it appears on the command
29+
line.
30+
31+
Therefore, if the path you specified on the command line was relative to the
32+
current directory, then it will be recorded in that same manner in the tag
33+
file. See, however, the ``−−tag−relative`` option for how this behavior can be
34+
modified.
35+
36+
Extension fields are tab-separated key-value pairs appended to the end of the
37+
EX command as a comment, as described above. These key value pairs appear in
38+
the general form ``key:value``. Their presence in the lines of the tag file
39+
are controlled by the ``−−fields`` option. The possible keys and the meaning
40+
of their values are as follows:
41+
42+
access
43+
Indicates the visibility of this class member, where value is specific to
44+
the language.
45+
46+
file
47+
Indicates that the tag has file-limited visibility. This key has no
48+
corresponding value.
49+
50+
kind
51+
Indicates the type, or kind, of tag. Its value is either one of the
52+
corresponding one-letter flags described under the various
53+
``−−<LANG>−kinds`` options above, or a full name. It is permitted (and is,
54+
in fact, the default) for the key portion of this field to be omitted. The
55+
optional behaviors are controlled with the ``−−fields`` option.
56+
57+
implementation
58+
When present, this indicates a limited implementation (abstract vs. concrete)
59+
of a routine or class, where value is specific to the language ("virtual" or
60+
"pure virtual" for C++; "abstract" for Java).
61+
62+
inherits
63+
When present, value is a comma-separated list of classes from which this
64+
class is derived (i.e. inherits from).
65+
66+
signature
67+
When present, value is a language-dependent representation of the
68+
signature of a routine. A routine signature in its complete form specifies
69+
the return type of a routine and its formal argument list. This extension
70+
field is presently supported only for C-based languages and does not
71+
include the return type.
72+
73+
In addition, information on the scope of the tag definition may be available,
74+
with the key portion equal to some language-dependent construct name and its
75+
value the name declared for that construct in the program. This scope entry
76+
indicates the scope in which the tag was found. For example, a tag generated
77+
for a C structure member would have a scope looking like ``struct:myStruct``.

CTags.sublime-settings

+31-15
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,42 @@
1+
// Place your settings in the file "User/CTags.sublime-settings", which
2+
// overrides the settings in here.
13
{
2-
// All options in here can also be specified in your project settings
3-
// with a prepended "ctags_" for example if you have
4-
//
5-
// "settings":
6-
// {
7-
// "ctags_command": ""echo \":ctags .tags\" | ghci -v0 /path/to/Main.hs"
8-
// }
9-
//
10-
// in your project settings, this will override the settings specified
11-
// in this file and in your user settings.
4+
// Enable debugging
5+
"debug": false,
126

13-
"debug" : false,
7+
// Enable autocomplete
148
"autocomplete": false,
15-
"command" : "ctags -R -f .tags",
16-
"filters" : {
9+
10+
// Alter this value if your ctags command is not in the PATH, or if using
11+
// a different version of ctags to that in the path (i.e. for OSX)
12+
"command": "",
13+
14+
// Set to false to disable recursive search for ctag generation
15+
"recursive" : true,
16+
17+
// Default read/write location of the tags file
18+
"tag_file" : ".tags",
19+
20+
//
21+
"filters": {
1722
"source.python": {"type":"^i$"}
1823
},
24+
25+
//
1926
"definition_filters": {
2027
"source.php": {"type":"^v$"}
2128
},
29+
30+
//
2231
"definition_current_first": true,
32+
33+
// Show the ctags menu in the context menus
2334
"show_context_menus": true,
24-
"extra_tag_paths" : [ [["source.python", "windows"], "C:\\Python27\\Lib\\tags"]],
25-
"extra_tag_files" : [".gemtags", "tags"]
35+
36+
// Paths to additional tag files to include in tag search. This is a list
37+
// of items in the form [["language", "platform"], "path"]
38+
"extra_tag_paths": [[["source.python", "windows"], "C:\\Python27\\Lib\\tags"]],
39+
40+
// Additional tag files to search
41+
"extra_tag_files": [".gemtags", "tags"]
2642
}

Context.sublime-menu

+5-12
Original file line numberDiff line numberDiff line change
@@ -3,20 +3,13 @@
33
"caption": "-"
44
},
55
{
6-
"command": "navigate_to_definition",
7-
"args": {},
6+
"command": "navigate_to_definition",
7+
"args": {},
88
"caption": "Navigate to Definition"
9-
},
9+
},
1010
{
11-
"command": "jump_back",
12-
"args": {},
11+
"command": "jump_prev",
12+
"args": {},
1313
"caption": "Jump Back"
14-
},
15-
{
16-
"command": "jump_back",
17-
"args": {
18-
"to": "last_modification"
19-
},
20-
"caption": "Jump to Last Modification"
2114
}
2215
]

Default.sublime-keymap

+2-7
Original file line numberDiff line numberDiff line change
@@ -12,18 +12,13 @@
1212
"keys": ["ctrl+t", "ctrl+y"]
1313
},
1414
{
15-
"command": "jump_back",
15+
"command": "jump_prev",
1616
"keys": ["ctrl+t", "ctrl+b"]
1717
},
1818
{
19-
"command": "jump_back",
19+
"command": "jump_prev",
2020
"keys": ["ctrl+shift+comma"]
2121
},
22-
{
23-
"command": "jump_back",
24-
"args": {"to": "last_modification"},
25-
"keys": ["ctrl+t", "ctrl+m"]
26-
},
2722
{
2823
"command": "rebuild_tags",
2924
"keys": ["ctrl+t", "ctrl+r"]

Default.sublime-mousemap

+1-1
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,6 @@
1010
"button": "button2",
1111
"count": 1,
1212
"modifiers": ["ctrl","shift"],
13-
"command": "jump_back"
13+
"command": "jump_prev"
1414
}
1515
]

Main.sublime-menu

+2-2
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@
1616
"command": "navigate_to_definition"
1717
},
1818
{
19-
"command": "jump_back"
19+
"command": "jump_prev"
2020
},
2121
{
2222
"command": "rebuild_tags"
@@ -33,7 +33,7 @@
3333
]
3434
},
3535
{
36-
//"argr_comment": "TODO",
36+
//"arg_comment": "TODO",
3737
"args": {
3838
"type": "multi"
3939
},

README.creole

-141
This file was deleted.

0 commit comments

Comments
 (0)