On Monday, May 21, 2018 at 10:57:37 AM UTC-4, Bram Moolenaar wrote:
> Jason Franklin wrote:
>
> > Well, according to the most widely accepted conventions in English grammar,
> > quotes always come after the period, exclamation point, or question mark.
> > So,
> > the following:
> >
> > This
On 11/28/18 5:01 PM, Bram Moolenaar wrote:
This is the result of the poll for features needed for supporting plugins.
These functions are to be added to support highlighting text, as defined
with text properties and text property types.
A text property type defines the highlighting and further
On Wed, Feb 20, 2019, 6:10 AM Jason Franklin <
jrfrank...@georgiasouthern.edu wrote:
> Perhaps it is personal taste. However, I still maintain that these
> behaviors
> in Vim with gn/gN are bugs. To me, inconsistency is not a feature in a
> text
> editor (it's a bug). I don't mean to be rude,
On 3/5/19 4:07 PM, Bob Pepin wrote:
On 5 Mar 2019, at 20.15, Bob Pepin wrote:
On 5 Mar 2019, at 12.53, Bram Moolenaar wrote:
I wonder, is this also possible for Typescript? It's like a better
version of Javascript, and its popularity is growing.
How well this works in practice remains to
On 3/8/19 3:52 AM, Bram Moolenaar wrote:
Patch 8.1.0999
Problem:Use register one too often and not properly tested.
Solution: Do not always use register one when specifying a register.
(closes #4085) Add more tests.
Files: src/ops.c, src/testdir/test_registers.vim
On 2/7/19 9:58 AM, Christian Brabandt wrote:
Hi Rob,
the patch is still here:
https://github.com/chrisbra/vim-mq-patches/blob/master/tagfunc
It might still apply, I don't know. Last time I worked on it, was when
the refactoring of K C code happened and eval.c was split up.
However I am not
On 2/8/19 8:34 AM, Bram Moolenaar wrote:
Andy Massimino wrote:
FYI, updated patch:
https://github.com/andymass/vim/commit/7fc4025d33de5b160927bb582325fec01d373658
Thanks.
By the way, I stress that I translated the patch verbatim and a quick test
shows it crashes, so something got clearly
On 2/8/19 2:33 AM, Christian Brabandt wrote:
On Do, 07 Feb 2019, Andy Massimino wrote:
FYI, updated patch:
https://github.com/andymass/vim/commit/7fc4025d33de5b160927bb582325fec01d373658
Programmatic access is increasingly important as language servers become
more popular. Some kind
On 2/17/19 4:00 AM, Robert Webb wrote:
Andy,
No longer crashes, but doesn't seem to work at all. Either that or how
it works has changed since I wrote my scripts.
Rob,
Your example seems to work for me. Would you mind trying
On 2/19/19 12:16 PM, Christian Brabandt wrote:
Does that mean we can drop the patch in favor of a an existing LSP
integration with Vim?
I think a tagfunc (or some other programmatic hook into tags) is still
necessary to have proper LSP integration. Current LSP plugins do not
work
On 5/30/19 1:06 PM, Paul Jolly wrote:
Hi all,
As a follow up to a recent thread ("Plugins exposing events to other
plugins":
https://groups.google.com/d/msg/vim_dev/uiw6gHft-0g/i8qdfT8YBQAJ)
I'd like to ask whether there is an existing pattern of configuration
functions that plugin
It is better to check for a patch directly: has('patch-8.1.1518'). It's
plausible someone would build with a subset of patches (and neovim does
this).
On Thu, Jun 13, 2019, 12:26 PM Paul Jolly wrote:
> >> I'd like to propose a version() function (or variable I guess?) that
> >> returns a
Personally, I think unary * would be reserved for the splay operator, i.e.
f(*array) == call('f', array) and whatever equivalent for dicts.
What about %{}?
On Sat, Jul 13, 2019, 4:55 PM Bram Moolenaar wrote:
>
> I wrote:
>
> > Patch 8.1.1683
> > Problem:Dictionary with string keys is longer
On 8/3/19 4:29 PM, Bram Moolenaar wrote:
I wrote:
Patch 8.1.1803
Problem:All builtin functions are global.
Solution: Add the method call operator ->. Implemented for a limited number
of functions.
Files: runtime/doc/eval.txt, src/eval.c, src/structs.h, src/userfunc.c,
> For example, we might happen to call from govim -> Vim while Vim is in
the middle of handling a listener_add callback that itself calls
ch_evalexpr which results in a call Vim ->govim.
Can this actually happen? Is this considered a "safe" situation then?
I assume adding a zero tick timer
On 6/5/19 2:58 PM, Yegappan Lakshmanan wrote:
Hi all,
Based on the discussion threads in Vim reddit, it looks like users are trying
to use the Vim terminal support as a replacement for screen/tmux.
One of the key features that is currently missing in Vim is the ability
to detach and reattach
I also think this is a problem.. but can't think of any good way to solve
it. My best guess is to add a new scriptversion which would require the
lambda to take exactly two arguments. But this won't catch simply swapping
idx and val by accident.
On Thu, Aug 8, 2019, 10:29 AM 'Andy Wokula' via
It says a little further down "There is one exception:" that the whitespace
is optional if v is the first character on the line.
On Thu, Dec 5, 2019, 9:51 PM Gary Johnson wrote:
> ":help modeline" says:
>
> There are two forms of modelines. The first form:
>
Would this be vim 8.2, vim 9 or vim X?
On Thu, Oct 24, 2019, 7:53 AM Christian Brabandt wrote:
>
> On Mi, 23 Okt 2019, Bram Moolenaar wrote:
>
> > It's been a long time since a new Vim release was created.
> > Many features have been added, it's time to concentrate on reliablity.
> > I will
The timings are very encouraging. Is the primary speedup in the function
parsing or better argument passing?
We have lambdas to write filter and map statements but for performance
critical applications it's still much faster to use an eval string instead
due to the function call overhead. (I.e.
On 12/21/19 9:11 AM, Bram Moolenaar wrote:
Ken Takata wrote:
I found a missing feature which should have been added in the
*new-vimscript-8.2* section in the version8.txt.
|optional-function-argument| was added in 8.1.1310.
It's too late for the release notes, but it might be better to
Please don't change endfunction/endif/endwhile... it makes it hard for
plugins like match-up to make % work. Also complicates things for very
little benefit, at best saving a tiny amount of typing, at worst makes it
easy to lose track of scopes.
On Wed, Dec 18, 2019, 4:27 PM Bram Moolenaar
On 1/3/20 8:17 AM, Bram Moolenaar wrote:
Ken Takata wrote:
2020/1/3 Fri 19:02:13 UTC+9 Bram Moolenaar wrote:
Yasuhiro Matsumoto wrote:
Why you don't use { ?
I know this will trigger a discussion. Nearly all languages use blocks
ending with "}". It's much easier to see where a block ends
They are different languages, but why make it harder than necessary for
people to migrate their scripts (and most probably maintain two dialects of
their scripts due to non-adoption by neovim)? My finger still reaches for
double quote when I want a comment.
On Thu, Jul 16, 2020, 4:17 PM Bram
Thanks, I did not fully appreciate the thorniness of the problem until
you pointed it out again.
On 7/16/20 5:05 PM, Bram Moolenaar wrote:
> This leads to complications when adding line breaks.
vim script has never properly supported continuation line comments,
except for a recent patch with
25 matches
Mail list logo
