![]() Shortcut for New Users Who Want To Test Drive TeX Who wants to upgrade everything should read the following sections. Older versions of TeXShop for earlier systems are available at the bottom of the page. Source Code for Version 5.12 (requires XCode 13 or later)īelow is a list of changes made in the latest version of TeXShop.Intel and Arm on High Sierra and higher fixes crucial bug for Ventura 13.1 (67.4 MB) I wanted to bring this idea for your consideration, and I can mail you my code if you like (although I haven’t implemented the fix above).If you just want to upgrade to the latest TeXShop, get bbl file in the completion, making for a prettier output. With a quick and dirty change to the latex_cite_completions.py I was able to use a. A simple fix is to continue processing bib files *after* the bbl file, discarding all keywords previously seen. bbl file but it doesn’t yet have your keyword, then the completion won’t work of course. The only catch is that if you haven’t generated the. bib files and superfluous bibliography entries to boot. bib files, and *only* those that are actually referenced in the tex file, so you can avoid the recursive search for. bbl file aggregates entries from all the included. But bibtex is already smart enough to get around formatting issues and produce a nice structured output in the form of a. bib file (which is usually generated by copy-pasting bibtex entries from the web). bbl files are much better structured than a typical. bbl files that bibtex generates, instead of using the. Also some entries in my bib file were commented out the plugin was still picking up the title and author list from those entries but missed picking up the keyword because the line didn’t start with Also, if the author list was split over multiple lines, sometimes the plugin wouldn’t pick it all up.Īnyway, I realized that an easy fix to this was to use the. So I was having trouble with completion in \cite, and on digging into the error messages I figured that the problem was some entries in my bib file with leading spaces before etc. Thanks for continuing to make your wonderful plugin even better!! The nice thing is that no other standard ST2 keyboard shortcut is affected.Īs an additional benefit, these bindings are consistent with the “nice” (or “compact”) on-screen keyboard in Windows 8, which only has a Ctrl key (no Windows key, no Alt key). Now, on ST2, the C-l shortcut is bound to “Extend selection to line”. I’ll try to reserve these for toggles and other less frequently used stuff. Finally, to toggle the focus from/to the PDF upon compilation, there is a three-key sequence: C-l,t,f. Reference and cite completion uses C-l,Ctrl-space (yes, even on OS X, that’s Command-ell, Control-space), but you can also use C-l,x (for cross-reference). Wrapping commands use the C- key twice: so, wrap in bold is C-l,C-b, etc. For instance: “j” for jump to PDF, “c” for LaTeX command based on the current word, etc. I have tried to use mostly C-l plus a single keystroke, with reasonable mnemonics. In fact, from now on, I shall write C-l to mean either ctrl-l or cmd-l, depending on the platform. This is abbreviated as ctrl-l,j (the same convention used by Sublime Text). jump to the point int he PDF file corresponding to the current cursor position) on Windows, enter Ctrl-l followed by j. That’s “ell” for LaTeX.Įxample: to do a forward search (i.e. All other plugin commands use ctrl-l or cmd-l followed by another key or key combination.For the time being, the Goto Anything functionality is also still bound to ctrl-r / cmd-r. The build command is still bound to ctrl-b on Windows and Linux, and cmd-b on OS X.Bottom line: things were getting unmanageable.Įnter the new keyboard shortcut scheme. However, different OS’s have slightly different conventions and expectations about what certain keys do. The other problem is actually due to ST2’s greatest feature: it’s a cross-platform editor, and the plugin must also work equally well on Windows and Mac, with full Linux support also coming soon (yes!). One was that, as I added features to the plugin, it became harder and harder to assign them to shortcuts that were not already used by Sublime Text 2 itself. However, this slowly led to an accumulation of problems. In particular, I tried to use the same keyboard shortcuts. Why change things? When I started working on this plugin, my objective was to emulate the functionality of the LaTeX bundle for TextMate. Make sure to read the README file for details: go to and scroll down (or click the “Read More” link near the project description). ![]() Heads-up: the keybindings for the LaTeXTools plugin have changed.
0 Comments
Leave a Reply. |