brandonwillard / vim-setup Goto Github PK

Currently, plugins are loosely organized by comment-groups; add them to a map/list like in this dotfile.

Does [neo]vim have any functionality in the direction of "virtual" buffers; where a virtual buffer is a [bi-directionally mapped] hidden view of a buffer--or parts thereof? I'm looking for a way to parse a buffer and produce these (view-only) virtual buffers so that only parts of the original, editable buffer can be treated--more or less--as independent buffers themselves. Changes to the original buffer should be reflected in these virtual buffers, as well.

More specifically, I would parse noweb documents into a--say--TeX-only virtual buffer and code chunks into a separate code-only virtual buffer. The intention is then to apply standard filetype actions to each virtual buffer for their respective [file]types.

If not all of this functionality exists in one plugin or set of features, how about parts of it? What's the closest we can get to the basic idea?

Hi,

I found your repo by looking for synctex command for qpdfview, after a few errors I found out that the command: vim --servername=VIM --remote +%2 %1 should be vim --servername VIM --remote +%2 %1. If the servername is actually VIM it does not make any difference because by default --remote looks for a server named VIM but for mine who's name is VIMTEX it was not working.

Bye,
David

Can we replace/improve some of the options switching mechanisms in our noweb functionality (i.e. noweb_more.vim) with views--using mkview, loadview.

Consider adding noweb delimiter functionality to delimMate, i.e. <<|>>=<CR>@, <%|%>. Perhaps this is best done by/within a snippet plugin, though.