![]() Github integration. Though literally no mathematicians I know use Github for anything related to research, I think that with the right features Github could become the “right” solution to paper management. They don’t support vim-style word-wrapping (gq), and they leave out things like backward search (? instead of /) and any : commands you tend to use. Vim commands. The problem is that they don’t go far enough here. ![]() Other than that, ShareLaTeX (like Overleaf) has tons of templates, all the usual libraries, great customer support, and great collaborative features for the once in a blue moon that someone else uses ShareLaTeX. This causes me to use a bunch of symbolic links that would be annoying to duplicate if I got a new machine. ![]() The only caveat is that ShareLaTeX only accesses Dropbox files that are in a specially-named folder. ShareLaTeX (unlike Overleaf) has seamless Dropbox integration. You cannot expect them to sign up for online services just to work with you.Īwesome features: Dropbox integration! This is crucial, because I (and everyone I know) does their big collaborative projects using Dropbox. I generally do not need collaboration services, because the de facto standard among everyone I’ve ever interacted with is that you can only expect people to have Dropbox. Basically I need a browser replacement for a desktop LaTeX setup. Needs support for figures, bibliographies, the whole shebang. Mindset: An editor I can use on my Chromebook or a public machine, yet still access my big papers and projects in progress. They’re both pretty solid, but a few features tip me toward ShareLaTeX. I’ve used a bunch of online TeX editors, most notably Overleaf (formerly WriteLaTeX). I would find the service significantly less useful if I could not export to pdf. Right now I embolden the Theorem and italicize the Proof., and end with a tombstone $ \square$ on a line by itself. I don’t see a simple way to make a theorem/proof environment with minimal typing, but it does occur to me as an inefficiency the less time I can spend highlighting and formatting things the better.Ĭaveats: Additional features, such as exporting from StackEdit to pdf requires you to become a donor ($5/year, a more than fair price for the amount I use it). Also some special support for (and shortcuts for) theorem/proof styling would be nice, but not necessary. Any other workflow besides Markdown with TeX support is just awfully slow, because the boilerplate of LaTeX proper involves so much typing (\begin, maybe?). In class notes: where I need to type fast and can sacrifice on prettiness.These are documents for which you have no figures, don’t want to keep track of sections and theorem numbering, and have no serious bibliography. Mindset: somewhere in between writing an email with one or two bits of notation (just write TeX source and hope they can read it) and writing a document that needs to look good. I haven’t found a better tool than StackEdit. At home I run OS X Mavericks (10.9.5), and I carry a Chromebook with me to campus and when I travel. Here’s what I use.įirst, my general setup. I’ve arrived at what I feel is a stable state. Be it lecture notes, papers, or blog posts, I think in the last two years I’ve typed vastly more dollar signs (TeX math mode delimiters) than in the rest of my life combined. As is the natural inclination for most programmers, I’ve tried lots of different ways to optimize my workflow and minimize the amount of typing, configuring, file duplicating, and compiler-wrestling I do in my day-to-day routine. Finally, change the text in step 4 to "".Over the last year or so I’ve gradually spent more and more of my time typing math. ![]() This means that the regex still "looks for" the but does not capture it in the $1-variable. I use " for my references and Marked.app and pandoc to view the notes (which I should maybe explain in a new thread).įor multimarkdown citekeys, change the regex in step 3 to ". The entry is written at the current cursor position.The entry is formatted using a regex-based search and replace under the assumption that citekeys do not contain spaces.The user is presented a list to choose one of those bib entries.bib file to JSON, which is parsed by jq to extract the author, the title and the citekey. pandoc-citeproc is used to convert the.The macro needs pandoc-citeproc and jq, both can be installed via homebrew. It feels a bit hacky and there are most definitely more elegant ways to do this. For now, I will post it only in this thread, since we might change it. No, seriously: This is one of the macros I wanted to have myself for quite some time, and since I had some time today and I knew it could be helpful to someone else, I tried to come up with a macro. ![]() Could I resist when you call me a wizard? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |