Re: Announce: ECMAScript interface for Vim
Le 02/03/2019 à 16:42, Bob Pepin a écrit : Hi, This is to announce the release of an ECMAScript scripting interface for Vim. Why? Because it seemed like the right thing to do. The longer backstory is that I recently returned to using Vim as a programming editor, when I was left without a computer and it was by far the best editor on the iPad. The last time I used Vim for programming, “fe” still stood for “fileencoding”. I am aware that I missed around 20 years of Vim history and that Vim script is the way it is for good (historical) reasons. I soon discovered that Vim it had added control structures to ex scripts, then lists and dictionaries, then lambdas. It seemed on track to reinvent ECMAScript. Since at the time of writing, ECMAScript is by some measures the most popular programming language in the world, with an excellent free, embeddable and portable implementation (Duktape), it seems by far the best option to use the real thing for future Vim scripting. Therefore, a Vim fork with a Duktape interface integrated can be found at: https://github.com/bobpepin/vim/tree/duktape Thanks, I love and use Duktape myself! Very good choice. There is also extensive documentation and further examples under :help duktape, or in runtime/doc/if_duk.txt (https://github.com/bobpepin/vim/blob/duktape/runtime/doc/if_duk.txt). Given that ECMAScript use camelCase I'd suggest to rename the low level API. E.g. read_blob -> readBlob. Regards, -- David -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: vim should reset indent size settings when changing file types
Le 29/11/2018 à 11:37, Erik Christiansen a écrit : Then, runnin `vim foo.html` will set ts, sts and sw correctly. But then, if I open a new file different from html directly from vim, it keeps those settings. If you use setlocal instead of set, that should do it. Oh, that was so easy. I wonder how can I miss that. Thanks! -- David -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
vim should reset indent size settings when changing file types
Hello, I'm not sure if there is way to fix that, but I actually would like to use tabs of size 8 for every file except html. So basically I create a ~/.vim/ftplugin.html file with: set ts=4 set sts=4 set sw=4 set noet Then, runnin `vim foo.html` will set ts, sts and sw correctly. But then, if I open a new file different from html directly from vim, it keeps those settings. Example: vim foo.html :e CMakeLists.txt <- ts, sts and sw is still 4 However, starting vim directly to edit a CMake file will use the defaults a size of 8. This means that I should create a ftplugin file for *every* kind of filetype or to quit vim and re-open. Correct me if I'm wrong but I think all settings that came from a ~/.vim/ftplugin should be removed once you switch filetype. Or perhaps I miss an option that already does this? What are you recommendations? Regards -- David -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Is ANSI C support still needed?
On Sun, 2018-04-15 at 12:43 +0200, Bram Moolenaar wrote: > For a long time Vim code was made to be compiled with ANSI C (also > known > as C89 and ISO C90). This means it can also be compiled on very old > systems. And since it wasn't too much work to support it, that was > the > choice. > C99 being 19 years old should be the default for a while. To me, I don't see any reason to support C89 nowadays. Even MS has finally added C99 in recent VisualStudio versions ;) Regards, -- David -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
markdown 4 backticks fenced code blocks
Hello, In vim, all my markdown files used 4 backticks () to delimitate fenced code blocks. It does not renders correctly in vim because it looks like vim's markdown syntax only supports 3 backticks (which is valid in most markdown extensions too). I wonder if it's possible to update the markdown syntax to support both 3 and 4 backticks as fenced code blocks. I think the line 88 of syntax/markdown.vim syn·region·markdownCode·matchgroup=markdownCodeDelimiter·start="^\s*```.*$"·end="^\s*```\ze\s*$"·keepend could be updated like this: syn·region·markdownCode·matchgroup=markdownCodeDelimiter·start="^\s*?.*$"·end="^\s*```\ze\s*$"·keepend But I'm not an expert, What do you think? -- David -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
