vim-pandoc
latex-snippets
Our great sponsors
vim-pandoc | latex-snippets | |
---|---|---|
11 | 9 | |
940 | 966 | |
0.4% | - | |
3.1 | 0.0 | |
about 1 month ago | almost 1 year ago | |
Vim Script | Vim Snippet | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vim-pandoc
-
Would you honestly recommend someone learning neovim as they begin their coding journey? Or would you suggest some other kind of IDE first?
With that, the only thing left to do was the make it as convenient as possible to export an MLA-formatted PDF from inside Neovim, so I wrote a custom function using the vim-pandoc plugin as a wrapper to make the command simpler:
-
Papyrus: Compile Markdown notes into Latex PDFs in Vim!
See also vim-pandoc, vim-latex, vimura
- Suggest me some plugins/setup for writing + previewing markdown.
-
Vim writing pdf plugins
vim-pandoc is a plugin that uses pandoc external program to convert documents between different formats.
-
Recommend a text editor that can do folding on markdown and that is not electron
I use vim-pandoc with neovim, it nests # headings as expected. If you install it, check :help vim-pandoc-folding for more info and other options.
- Does a Plugin to highlight Markdown syntax using conceal already exists?
-
[Update] Google docs integration for vim using gdoc.vim!
From that perspective, raw text might be okay--google drive is mostly treated as a cloud storage system and not really as a place for formatted documents. Markdown is still useful from a vim folding perspective; and generating formatted output (e.g., via pandoc) can be done outside of vim (or perhaps using vim-pandoc or simple script snippets).
-
Less than symbol breaks highlighting in vim when writing markdown
What about an alternative markdown syntax plugin? I'm using https://github.com/vim-pandoc/vim-pandoc alongside https://github.com/vim-pandoc/vim-pandoc-syntax (you can also use only the syntax plugin), which does support latex math.
-
How to check if you're in markdown math?
I was trying to use some of Gilles Castel's LaTeX snippets for my own notetaking, which I do on nvim with markdown, using pandoc to convert to pdf. The problem with this is that the tex snippets are designed to be activated only when in LaTeX math, but there's no function to directly check this in the plugin I'm using for pandoc markdown.
-
Table of contents/jumping between markdown headings?
I'm trying to cut back on some plugins that I'm not really getting that much out of and clean up my vimrc because it was getting a little bloated. Does anyone know if there is a good way to have a pop-up table of contents in a markdown document for jumping around a document like there is in 'vim-pandoc' (https://github.com/vim-pandoc/vim-pandoc.git) without all the other stuff in that plugin? I suppose I can just use marks but I really liked that one feature. Thanks!
latex-snippets
-
LaTeX3: Programming in LaTeX with Ease
Though I'm not the same commenter, I personally got over the curve by learning from the LaTeX-tutorial.com website recommended by my professor of a math course, and then by learning how to use the Vim text editor with LaTeX. I also took a math course that happened to required weekly problem sets to be submitted in LaTeX.
The first stage of learning was to learn LaTeX with from the website LaTeX-Tutorial.com, which includes a tutorial with no paywall [1]. I paid the closest attention to tutorials 00 to 05 for the core functionality, then skimmed the rest of the tutorial, as I would only rarely use the remaining features. (For tables, even after gaining a general familiarity with how the tabular environment work, I still found it faster to use the Tables Generator website [3], which was also recommended by my instructor).
I then gained practice using TeXstudio as I preferred an offline program, though my professor and most of my fellow students used Overleaf as an online editor. However, I found that I spent a lot of time transcribing handwritten problem sets into LaTeX documents on TeXstudio and Overleaf, and searched for a faster and more pleasant method (in particular, I found that there was a significant delay in my experience when compiling LaTeX code to a PDF with TeXstudio and Overleaf).
That was the source of my motivation for learning how to use Vim with LaTeX, though you should have enough knowledge for effectively writing LaTeX documents with just the information from the LaTeX tutorial website. I was also motivated due to my curiosity about Vim in general, from past discussions on the text editor in an xkcd comic and various forum discussions.
To begin the learning process for Vim, I completed the default-installed Vim tutorial (also motivated because I was curious about Vim in general, from past discussions on the text editor in an xkcd comic and various forum discussions) over a weekend day. Crucially, I followed most of the advice from a Hacker Noon article [4] about more efficient ways to scroll up and down. I then edited the .vimrc config file to allow for using the cursor to keep things simple, using most of the default configurations for Neovim.
Then, I roughly followed E.J. Mastnak's guide at [1] to get set up, over the course of another weekend day. After some troubleshooting with the configuration, I finally got the setup to work, and I’ve happily been using Vim with LaTeX since then. Since the process reduced the friction to compile LaTeX code to a PDF, I compiled my document more often, so I could catch errors early and often (I rarely spend time troubleshooting and debugging LaTeX code now, since I now fix errors shortly very after they appear, as I compile the document every few lines of code or so).
The main major drawback of using Vim and LaTeX was that I followed the advice to enable autocompletion with snippets (e.g. typing “AA” automatically types in “\forall”) via the the UltiSnips software, which would make substitutions without an audible notification (in contrast to other software that I use to make snippets outside of Vim, that would make an audible ping before a substitution). That led to some significant typos in an early assignment I submitted, and I since learned from my mistake to be far more careful when using Vim with LaTeX for enabling snippets. However, snippets also functioned as a nice learning tool, as I would learn through practice what some basic commands would be, through the auto-substitution (for example, I’ve now easily remembered through exposure that <= is written as `\leq`) in LaTeX.
To conclude, you can use free tutorials to learn the basics of LaTeX, and use Overleaf and TeXstudio to practice. For additional speed and pleasantness, you can spend a couple focused weekend days (or possibly more) to learn how to use Vim with LaTeX following another free guide. Then, you can reinforce your learning through regular practice (in my experience, my regular practice was necessary due to requirements of a math course—if your work or education similarly requires LaTeX, a real-life necessity is a great motivator for practicing document production with LaTeX).
[1] https://latex-tutorial.com/tutorials/
[2] https://www.ejmastnak.com/tutorials/vim-latex/intro/
[3] https://www.tablesgenerator.com
[4] https://hackernoon.com/learning-vim-what-i-wish-i-knew-b5dca...
[5] https://github.com/gillescastel/latex-snippets/blob/master/t...
-
Troubles to set up vimtex and ultisnips for latex
My ~/.vimrc configuration is just copied from this website https://github.com/gillescastel/latex-snippets
-
How to check if you're in markdown math?
I was trying to use some of Gilles Castel's LaTeX snippets for my own notetaking, which I do on nvim with markdown, using pandoc to convert to pdf. The problem with this is that the tex snippets are designed to be activated only when in LaTeX math, but there's no function to directly check this in the plugin I'm using for pandoc markdown.
- Emacs' org-mode gets citation support
- help with ultisnips and vimtex
- A place to learn LaTeX online (learnlatex.org)
-
Package vim-latex annoyingly inserts extra <++> after code completions
1) There's a different plugin based approach for LaTeX if you don't grow to like latex-suite (as I did): vimtex can be used to do the compiling, syntax highlighting, completion, navigating to the right spot in the code or pdf ect, and you can take care of the snippets yourself, either by simply not doing anything and typing everything out (completion aided), using :h :ab or using a snippet plugin (in the case of UltiSnips, a careful review of this would be a boost) 2) "just installing" vim plugins without reading about their features doesn't really add to anything other than the learning curve, because many vim plugins change the way vim works and can only be made useful by knowing about their features. If you just let them sit, many of them won't do anything other than slowing down the program. This might very well be different than in VSC
-
Need help with Ultisnips
tex.snippet file i use
What are some alternatives?
vim-markdown - Markdown Vim Mode
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
vim-polyglot - A solid language pack for Vim.
spacemacs - A community-driven Emacs distribution - The best editor is neither Emacs nor Vim, it's Emacs *and* Vim!
mkdx - A vim plugin that adds some nice extra's for working with markdown documents
dotfiles - My dotfiles for Bash/Zsh, Vim/Neovim, Doom Emacs, tmux, Git, terminal emulators, JupyterLab, aria2, mpv, Nix and Homebrew
vim-pandoc-syntax - pandoc markdown syntax, to be installed alongside vim-pandoc
chemacs2 - Emacs version switcher, improved
bullets.vim - 🔫 Bullets.vim is a Vim/NeoVim plugin for automated bullet lists.
inkscape-figures - Inkscape figure manager
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
github-orgmode-tests - This is a test project where you can explore how github interprets Org-mode files