Something went wrong. Try again.
dotfiles
Something went wrong. Try again.
8.1 kB · 205 lines
at main
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206// LaTeXTools Preferences//// Keep in the User directory. Personalize as needed{// ------------------------------------------------------------------// 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, // When to trigger cwl-command completion (requires the LaTeX-cwl package) // possible values are: // "always" (always show command completions) // "prefixed" (default, show command completions if the current word is prefixed with '\') // "never" (never show command completions) "command_completion": "prefixed", // 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" (default, never hide the build panel) "hide_build_panel": "no_warnings",// ------------------------------------------------------------------// Temporary file settings// ------------------------------------------------------------------ // Ends of the names of temporary files to be deleted "temp_files_exts": [ ".blg",".bbl",".aux",".log",".brf",".nlo",".out",".dvi",".ps", ".lof",".toc",".fls",".fdb_latexmk",".pdfsync",".synctex.gz", ".ind",".ilg",".idx", ".lol", ".glo", ".bcf", ".ist", ".run.xml", ".glg", ".gls", ".lot", ".vrb", ".nav", ".snm", ".acr", ".xdy", ".acn" ], // Folders that are not traversed when deleting temp files "temp_files_ignored_folders": [ ".git", ".svn", ".hg" ],// ------------------------------------------------------------------// 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" : "E:\\texlive\\2016\\bin\\win32;$PATH", // TeX distro: "miktex" or "texlive" "distro" : "texlive", // Command to invoke Sumatra. If blank, "SumatraPDF.exe" is used (it has to be on your PATH) "sumatra": "E:\\Program Files\\SumatraPDF\\SumatraPDF.exe" }, "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 linked to Python 3. If blank, "python" is used // Note: ST3 uses Python 3 internally, but the evince scripts need Python 2 "python2": "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": "subl3", // 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 // people 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 //"command": ["latexmk", "-cd", "-e", "-f", "-pdf", "-xelatex", "-interaction=nonstopmode", "-synctex=1"] } },// ------------------------------------------------------------------// 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}"}