forked from SublimeText/LaTeXTools
-
Notifications
You must be signed in to change notification settings - Fork 0
/
LaTeXTools.default-settings
189 lines (154 loc) · 7.29 KB
/
LaTeXTools.default-settings
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
// LaTeXTools Preferences DEFAULT SETTINGS
//
// DO NOT EDIT THIS FILE!!! Open the Command Palette and run the "Reconfigure and migrate settings"
// command. Alternatively, select the "Reconfigure LaTeXTools and migrate settings" item from the
// Preferences, Package Settings, LaTeXTools menu, or open the ST console and type
// sublime.run_command("latextools_migrate")
// This will migrate your old settings and create a file "LaTeXTools.sublime-settings" in your
// User directory. You can also manually copy this file the User directory.
//
// Once the file is in the User directory, you can edit it at will.
{
// ------------------------------------------------------------------
// General settings
// ------------------------------------------------------------------
// Cite/ref autocompletion by default is triggered after e.g. \ref{. If you don't like this,
// set to false. You can also use toggles: C-l,t,a,c and C-l,t,a,r.
"cite_auto_trigger": true,
"ref_auto_trigger": true,
// Fill-helper autocompletion triggered for a wide range of references to external
// files. You can also use toggle: C-l,t,a,f
"fill_auto_trigger": true,
// Keep focus on Sublime Text after building (true) or switch to PDF viewer (false)
"keep_focus": true,
// Sync PDF to current editor position after building (true) or not
"forward_sync": true,
// level to hide the build panel after the build is finished
// Possible values are:
// "always" (hide the panel even if the build failed),
// "no_errors" (only hide the panel if the build was successful even with warnings),
// "no_warnings" (only hide the panel if no warnings occur) and
// "never" (never hide the build panel)
"hide_build_panel": "never",
// ------------------------------------------------------------------
// Platform settings: adapt as needed for your machine
// ------------------------------------------------------------------
"osx": {
// Path used when invoking tex & friends; MUST include $PATH
"texpath" : "$PATH:/Library/TeX/texbin:/usr/texbin:/usr/local/bin:/opt/local/bin"
// Path to PDF viewer, if needed
// TODO think about it. Also, maybe configure it here!
},
"windows": {
// Path used when invoking tex & friends; "" is fine for MiKTeX
// For TeXlive 2011 (or other years) use
// "texpath" : "C:\\texlive\\2011\\bin\\win32;$PATH",
"texpath" : "",
// TeX distro: "miktex" or "texlive"
"distro" : "miktex",
// Command to invoke Sumatra. If blank, "SumatraPDF.exe" is used (it has to be on your PATH)
"sumatra": ""
},
"linux" : {
// Path used when invoking tex & friends; MUST include $PATH
"texpath" : "$PATH:/usr/texbin",
// Command to invoke Python 2. Useful if you have both Python 2 and Python 3 on your system,
// and "python" by default is liked to Python 3. If blank, "python" is used
// Note: ST3 uses Python 3 internally, but the evince scripts need Python 2
"python2": "",
// The name of the ST2 or ST3 executable. On Ubuntu, both subl and sublime-text are
// available for ST2; adjust as needed for other platforms, and for ST3
"sublime": "sublime-text",
// How long to wait after evince has launched before sending a sync message
// in seconds, floating point; choose 2.0 or 3.0 on a slower machine, 0.5 on a fast one
// Note: only tweak this if sync after launching the PDF viewer does not seem to work,
// or if the PDF viewer opens instantly and you don't want to wait.
// Default: 1.5 (works on my MBP4,1...)
"sync_wait": 1.5
},
// ------------------------------------------------------------------
// Build engine settings
// ------------------------------------------------------------------
// OPTION: "builder"
// Specifies a build engine
// Possible values:
//
// "default" or "" the default built-in build engine; currently
// this is the same as "traditional"
//
// "simple" invokes pdflatex 1x or 2x as needed, then
// bibtex and pdflatex again if needed;
// intended mainly as a simple example for
// peoeple writing their own build engines.
//
// "traditional" replicates the 'old' system based on
// latexmk (TeXLive) / texify (MiKTeX)
//
// "script" external script: just invokes the script
// specified in "builder_settings"
//
// custom name you can also use third-party build engines;
// if so, set the "builder_path" option below
//
// NOTE: custom builders CANNOT have the same name as an existing
// built-in build engine (including "default")
"builder": "traditional",
// OPTION: "builder_path"
// If non-empty, specifies a path to a custom builder, relative to the
// Sublime Text Packages directory.
// For instance, "User/builders" (on Windows: "User\builders") is a good
// choice if you roll your own.
// (Note: if you choose "User", you may get a Python import error in the
// console, but things will still work).
// Leave empty ("") for a built-in builder.
"builder_path": "",
// OPTION: "builder_settings"
// Specify builder-dependent settings and preferences
// Possible values: see README or documentation provided with
// third-party build engine.
// Builder setting can be general or OS-dependent
"builder_settings" : {
// General settings:
// See README or third-party documentation
// (built-ins): true shows the log of each command in the output panel
"display_log" : false,
// Platform-specific settings:
"osx" : {
// See README or third-party documentation
},
"windows" : {
// See README or third-party documentation
},
"linux" : {
// See README or third-party documentation
}
},
// ------------------------------------------------------------------
// Formatting of bibliographic references in quick panel
// ------------------------------------------------------------------
/* This preference sets the format of the quick panel to select citations using wildcards.
The setting is a list with one or two string using wildcards for author, title, keyword etc.
Default setting: the traditional display, `["{title} ({keyword})","{author}"]`
Format:
Can quantum-mechanical description of physical reality be considered complete? This is an non-existing subtitle to illustrate (einstein1935quantum)
Albert Einstein and B Podolsky and N Rosen
Richer alternative: ["{author_short} {year} - {title_short} ({keyword})","{title}"]
Format:
Einstein et al. 1935 - Can quantum-mechanical description of physical reality be considered complete (einstein1935quantum)
Can quantum-mechanical description of physical reality be considered complete? This is an non-existing subtitle to illustrate
Another alternative: ["({keyword}) {author_short} - {year}","{title} - {journal}"]
Format:
(einstein1935quantum) Einstein et al. - 1935
Can quantum-mechanical description of physical reality be considered complete? - Physical Review
No-title alternative: ["{author_short} {year} ({keyword})"]
Format:
Einstein et al. 1935 (einstein1935quantum)
Valid wildcards: keyword, title, author, year, author_short, title_short, journal
*/
// Uncomment or modify at will
"cite_panel_format": ["{author_short} {year} - {title_short} ({keyword})","{title}"],
//"cite_panel_format": ["({keyword}) {author_short} - {year}","{title} - {journal}"],
//"cite_panel_format": ["{author_short} {year} ({keyword})"],
// Similarly, the formatting for the autocomplete panel:
"cite_autocomplete_format": "{keyword}: {title}"
}