Yawn... More than 2 years for a trivial patch like this.
https://github.com/Silex/vim/commit/de53ab72c89affa8ba77536ed8920751c037d127
Honestly, I'm disapointed. It's been a while I don't use vim anymore but I
think vim deserves a more reactive development model than the current one.
Bram: I
It's in the todo list. That list is very long, and bug fixes have
priority. Might take a while.
How long is that list? It's been more than 6 months now :/
Philippe
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
Which might be out of date. The latest version is always available at:
https://vim.googlecode.com/hg/runtime/doc/todo.txt
Thanks.
Philippe
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit
Do you maybe have a yankring-like plugin that makes use of the feature?
That could help people try it out in real-world scenarios.
Yes there is, see https://github.com/the-isz/MinYankRing.vim/tree/events
Philippe
--
You received this message from the vim_dev maillist.
Do not top-post! Type
It's in the todo list. That list is very long, and bug fixes have
priority. Might take a while.
Bump :)
Philippe
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit
Hum? Should I submit a patch? This is a bug right?
--
You received this message from the vim_dev 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
But you can still access the project page directly at:
https://sourceforge.net/projects/vim/
The advice re: how to get help is from:
https://sourceforge.net/projects/vim/support
Probably a default project setting.
Yes I'm talking about these pages.
I'm also concerned that the CVS/SVN
I'm pretty sure you nomally WANT to lock a file from being written,
while you are executing its contents as a script. It sounds like this
is what is happening. Is there some reason you want to write the file
while executing it?
This bug arised from a script that checked wether itself was
Assuming you don't want permissive sharing when doing actual
I/O (I argue above that you don't), I question the value of
changing mch_access() in the proposed way. The point of
mch_access() is to give you a predictor of what types of
access will likely work. If the access check tells
So, who has to authority on this? Should we allow multiple writers to
a file? Should we allow writers on currently read file? If no how
drastics are the changes to be made to the linux api?
Philippe
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below
After installing vim7.3 on a ubuntu system, I had again the problem that
import did not work for .so libraries in lib-dynload. I found that
sys.path was initialized with /usr/... instead of /usr/local/ On
ubuntu (and probably on other linux distros as well) python3 is
installed in
Hello,
What is the rationale for using old-style function declarations in vim
source? historical reasons?
I'm curious because to me old-style function declarations only have
disadvantages, but maybe there's something I'm missing about them
where they are actually useful in some situations.
I'm curious because to me old-style function declarations only have
disadvantages, but maybe there's something I'm missing about them
where they are actually useful in some situations.
They work with every C compiler.
Most C compilers accept the ANSI style, but it's not too much trouble
FWIW, you have my vote for making this happen. I think it's not that
hard to make everyone happy on this subject by the mean of .vimrc
settings, like we have between vi and vim for :set compatible.
Wether we use structures or the byte 80 for special key is
implementation detail, I mean wether
Yes. But what happens when you then edit that macro by putting the
register into a buffer, changing it, and yanking it again? This is not
uncommonly done. How should the registers be stored in .viminfo? How do
you write the input to the feedkeys function as a string in vimscript?
Etc.. These
This would be easier if we actually had a solid 'new design'. We don't.
We just have a bunch of rough ideas. One of those ideas had a drafted
structure and suggestion that it be used only in the input queue, where
the memory inefficiency would not be a concern. I have pointed out that
there
That said, I think there is a compromise. Vim has features, maybe the
new input mechanism could simply be a feature, something like
+enhanced_term_input (like we have for +python or +eval), and plugins
could simply check with stuffs like:
With an option like :set
So I would encourage you not to view this discussion as opposition to
the idea. Quite the reverse. This discussion is actually an important
part of making this idea happen. We need to discuss these things so we
can do it the best way possible, without *needlessly* breaking backward
Apparently answering on the webpage of google groups likes to set the
old subject back, I changed it again.
Philippe
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit
As long as the two triplets of keypresses I suggested originally can all
be represented uniquely, and without reference to timing information in
the Escape vs Alt+ case, then I'm happy with whatever internal
implementation makes it happen.
The two triplets in question being
Tab
This happened to me several times now so I think this probably happens
to other people too:
When writing a script, I often have to do a regex and match subparts,
but I always forget which function is. I easily fall on :h match()
but nowhere within match() is matchlist() or matchstr() mentionned,
TextDeleted * echom 'Deleted: ' . @
autocmd TextYanked * echom 'Yanked: ' . @
Tell me what you think.
Philippe
From f82fa9037bf6bd2013742e9502ffcdea903e8401 Mon Sep 17 00:00:00 2001
From: Philippe Vaucher philippe.vauc...@gmail.com
Date: Mon, 23 May 2011 17:08:51 +0200
Subject: [PATCH] Added
I think they should be called TextDeletePost and TextYankPost to be
consistent.
Ok, I can do that.
Try doing something weird in the autocommand, such as help and then
deleting something.
You probably need to disallow lots of things to avoid breaking stuff
(and perhaps even crashing Vim).
No because every delete/yank use the register even if a register was
explicitely specified. As a matter of completeness maybe it'd be nice
to know which register was intended yes but it's the first time I
fiddle with vim's source (with some pain) so I'm not too sure how much
work is
'YankPost: Register(' . v:register .
') Value(' . eval('@' . v:register) . ')'
Here's the (hopefully final) patch:
From 15a2f33bd2dd3d10d0f167e249546fcff8f7e9a0 Mon Sep 17 00:00:00 2001
From: Philippe Vaucher philippe.vauc...@gmail.com
Date: Tue, 24 May 2011 20:32:48 +0200
Subject: [PATCH] Add
Ah, the_isz found the first bug already :)
When yanking/deleting with a visual range, the autocmd is triggered
twice.
I'll fix it and report.
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit
SIDdel_or_yank_event('TextYankPost')
Tell me if there's an issue I forgot to address.
Here's the patch:
From de0dd46e90fd7c6587492d3d7f8878d9f57f42f2 Mon Sep 17 00:00:00 2001
From: Philippe Vaucher philippe.vauc...@gmail.com
Date: Wed, 25 May 2011 13:02:28 +0200
Subject: [PATCH] Add TextDeletePost
So, Bram is that ok? Do you want the patch on another medium? Are
there issues I didn't address?
Thanks,
Philippe
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit
I need to have a closer look. Bugs usually have a higher priority than
new features.
Hum, it's been a while now... should I create a ticket on
http://code.google.com/p/vim/issues/list so it's not forgotten?
In the meantime, we did some tests about potential problems with this
new feature:
Bram: this is just a message to bump this issue, to avoid that you
forget about it.
Thanks,
Philippe
--
You received this message from the vim_dev 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
On Monday, February 29, 2016 at 4:13:31 PM UTC+1, Björn Linse wrote:
> For the record, a version of this was merged into neovim:
> https://github.com/neovim/neovim/pull/4304
Hehe, I just noticed that!
Thanks :-)
So reguarding vim, 6 years ago this was put in the TODO in the "As soon as
31 matches
Mail list logo
