Linda_pp

コードをベースに話をしたほうが良いかなと思います． ## 1. import が例外を投げる時 ```vim try let s:Job = vital#some_plugin#import('System.Job') catch endtry " 処理を分けるところ if exists('s:Job') " job があるとき〜 else " ないとき… endif ``` ## 2. import が例外を投げない時 ```vim...

```vim try let s:Job = vital#some_plugin#import('System.Job') function! foo(...) " あるとき〜 endfunction catch function! foo(...) " ないとき… endfunction endtry ``` みたいに関数切り分けるとかはありかもですが，プラグインの処理によってはこういう実装は厳しそうな気も

> slow (overhead of import()) I was just curious but did someone measure this overhead?

ok. I'm not denying the point. I was just curious about how much overhead it causes as a user of vital.vim if anyone has already done some measurements.

XML やってます

OptionParser に下記を実装しました． - デフォルト値を指定する機能 - オプション名（`--hoge=huga` の `hoge` の部分）の補完 - オプション値（`--hoge=huga` の `huga` の部分）の補完をユーザ定義する機能

Could you describe exact steps to reproduce this (your environment, setup, command executed, expected output)

Thank you for the description. I'll look into this.

It seems that your 'Actual result' is not an invalid markdown. From [commonmark spec]() > In general, a setext heading need not be preceded or followed by a blank line....

Does this actually break some markdown parser?