Ben Schmidt wrote:
Well, I can see that you get the information, but this is not really a
useful real-world example. Think of a user that wants to get something
done for which v:operator is needed. And for which there is no other
solution.
Here's a somewhat naively implemented
David Fishburn wrote:
This is very useful for me, but I suspect other plugin developers will
also benefit since they can make smarter functions by looking at what
the user has keyed in.
Well, I can see that you get the information, but this is not really a
useful real-world
Matthew Wozniski wrote:
To reproduce, do the following in a newly started vim:
First enable 'h' moving between lines to give us a way to delete over
BOL, though left would work if you're using gvim
:set ww=h
then, ixCRC-odh
that is, insert a line containing x, then try to delete
I updated detectindent plugin, but the original author seems to be
unreachable
http://www.vim.org/scripts/script.php?script_id=1171
Can you re-assingn the plugin to me (theNeuron) so that I can continue
to work on it? Of course I'll be happy to return it to original
:echo expand(/a/b/c 'd)
:echo glob(a 'b/*)
Both seem to work fine for me. Maybe you'd have to tell more about
your environment check if this also occurs when running vanilla vim
(no plugins, no (g)vimrc).
You are using Windows, right ?
I checked the source and what is happening for Unix
On 30/10/2007, Ben Schmidt [EMAIL PROTECTED] wrote:
Very happy to modify the patch to document this. It does not include the
count;
that is what v:count is for. And it will be two characters for commands
that begin
with 'g' or 'z', and one character otherwise.
Happy to include an example
On 31/10/07 17:43 +0100, Vladimir Marek wrote:
os_unix.c:6652
/* file names are separated with Space */
if (shell_style == STYLE_ECHO)
{
buffer[len] = '\n'; /* make sure the buffer ends in NL */
p =
