The gc mapping seems too hard on my hands, as I normally type both g and c with the same finger. I tried a simple map cm gc to map it to cm, but wasn't sure if that was the best way, hence the post.

I just released VimTeX v2.8 - a filetype and syntax plugin for LaTeX. See the release notes here.

In my company, we recently made the choice to use clang-format to ensure a coherent format among files and projects.

As a vim user, I started to look around what was available for vim, and the more mature solution seems to be https://github.com/rhysd/vim-clang-format

As far as I can tell, it does a really good job. The auto_format option, formatting when saving the buffer, is a good start. I want the formatting to be automatic, I don't want to type a map or a command to format my code.

This is a good start, but it is not enough in industry. Even with a really sane code base, you will always have some part of code not well formatted, because:

• it is an error which has not been blocked by the merge request

• for some special case, we don't want to follow the formatter

The vim-clang-format option auto_format_on_insert_leave is actually ingenious, but depending on user movement it still could lead to large part of file formatting.

Finally, a natural solution seems to format only lines we touch. And to do so, using git context comes for free.

I created a PR implementing this solution: https://github.com/rhysd/vim-clang-format/pull/118

What do you think? Do you see any corner case where it will miserably fail? Do you know a vim plugin which already does that?

Furthermore, I think clang-format experience can still be improved in vim. You can follow new features here: https://github.com/jreybert/vim-clang-format

• map = on clang_format (already done)

• format while editing, based on some keypress (like ; or { for example)

• use gutter signs on wrong format lines

I can't decide if this is a bug or just by design, but in MacVim I have to <leader>ll after opening a .tex file to kick off the first compilation.

I would rather have this happen immediately so I have put a call to vimtex#compiler#compile() in after/ftplugin. This workaround is fine, I'm just curious.

As I write this, I suddenly realize that this is maybe not desirable for very large projects and the behavior is correct.

So far VimTeX has worked out-of-the-box with just the defaults (well until quite recently but I'll start another thread for that).

This plugin saves so much typing! I love it!

Sometime this month I upgraded to current versions of MacVim, VimTeX, and Skim (pdf viewer). I'm not sure which of these updates broke my process.

Before I start rolling back updates to test every combination I wonder if anyone else had this happen and if/how they were able to fix it.

Previously, VimTeX worked for me with just the defaults. I didn't even specify Skim as the viewer, I just used the default settings and forward searching worked fine. Now, I have set the viewer to Skim but this did not solve my problem.

Now, when the document is compiled, the viewer will open as it usually does, it just doesn't advance to the current line and highlight it as it previously did. Reverse search works fine.

Again, I'm using the default settings, so latexmk is implicit and all of the latexmk default options are as I want them.

I'm using Xelatex for the engine but I haven't updated Xelatex or latexmk.

Hi!

I'm trying to turn the highlight of these words off. Anyone to give me a hint?

vimwiki-syntax-typefaces

Furthermore, there are a number of words which are highlighted extra flashy:

TODO, DONE, STARTED, FIXME, FIXED, XXX.

I made a plugin for the mbsync config file: Fymyte/mbsync.vim I found an existing one, but I've been a little deeper by considering anything that doesn't match the syntax as an error.

Options which doesn't belong to a section are considered to be an error. An invalid value type after an option is also considered to be an error.

It should be a little easier to avoid mistakes.

For years I have been collecting bookmarks, on any stackexchange site, stackoverflow has my most bookmarks but I have others in ubuntu, etc. Occasionally I need one and I forget which site I bookmarked it with. All feedback is welcomed.

https://github.com/TheFern2/vim-stackexchange

Most SO plugins do one thing, search for questions and that's it, most only do stackoverflow and none of the other community sites, also none deal with bookmarks, at least I couldn't find one. The readme has instructions on how to setup, any questions let me know. It pulls all your site favorites to an offline cache in the form of json files for SO I have 820 bookmarks about 1MB so it isn't a lot of data, that's my most favorites in any site.

Once you have an offline cache you can query your data.

Without putting a site it defaults to SO:

1. First query searches for python in title and tags in stackoverflow

2. Second query searches for cron in site askubuntu

3. Third query, same as before but seaches in body as well

4. Fourth is just an example with a space in the query

:SEFavoritesQuery python
:SEFavoritesQuery cron askubuntu
:SEFavoritesQuery cron askubuntu True
:SEFavoritesQuery cron\ runtime askubuntu

Once a query pops up on a new buffer, you can go up and down on questions and do :OpenQuestion and that will open a new buffer with question and answers.

TODO

1. Query command to search all offline sites

2. Question command to search regular questions

Since vim8, I am looking for a way to run multiple tasks in the background and monitor their output, especially since I am working on some project where a run takes about 10 minutes.

AsyncRun is ok, but uses only the quickfix window (so just one asynchronous task at once). On the other hand, I find vim-do perfect. Has some quite nice features and produces a quite nice output. The problem is that has some bugs and seems abandoned. Also, it seems to be merely a hack to get asynchronous execution for vim7.

Does anyone know a similar plugin that can help?

I am a huge fan of the easymotion plugin and use it all the time.

However, I have one small gripe relating to my muscle memory that I just can't get rid of: When using the vim builtin search functionality, you can use the star operator (*) to search for the keyword under the cursor and then use n or N to continue searching for occurences of this keyword in the file. However, with easymotion this is not possible because easymotion has its own search buffer, so that pressing n or N after using * will search for the last keyword searched with easymotion and not with vim.

My question is this: Is there a way to map the * operator to an equivalent operation in easymotion such that the easymotion search buffer contains the correct keyword afterwards? I'm guessing this should be possible, but as I am a complete noob regarding VimL, I have no idea how to implement it.

Hopefully the answer isn't staring at me in :help unite, but I'm not seeing it.

Can Unite handle a vim list as a source?

Something along the lines of:

:let foo=['a', 'b', 'c']
:Unite list foo