On Friday, March 27, 2015 at 5:00:19 AM UTC+9, Bram Moolenaar wrote:
> Isn't there a way to clone only up to some time ago, e.g., the 7.4
> release? I rather leave this a decision on the user side than on the
> server side (meaning that history would be lost forever).
git clone --depth 1
--
--
I found a problematic behavior in xmlcomplete.vim a few years ago.
I wrote a patch to fix it and sent to the maintainer, but I've never
got any reply.
So that I send the patch to here.
-- Forwarded message --
From: Kana Natsuno
Date: Fri, Apr 9, 2010 at 11:33 PM
Subject:
On Saturday, April 20, 2013 6:50:58 AM UTC+9, glts wrote:
> On Fri, Apr 19, 2013 at 8:58 PM, Ingo Karkat wrote:
> > With v:motiontype, I'd expect that to be applicable to _every_ motion,
> > not just those few special ones. I would prefer v:forcedmotiontype. The
> > only saving grace for this unrea
On Wed, Mar 20, 2013 at 7:21 AM, Sung Pae wrote:
> On Sun, Mar 17, 2013 at 05:08:29AM -0700, Kana Natsuno wrote:
>
>> Especially, the "solution" posted in the discussion
>>
>> https://github.com/tpope/vim-repeat/issues/8#issuecomment-13951082
>>
>
On Sun, Mar 17, 2013 at 8:03 PM, glts wrote:
> The "repeat.vim" plugin was created to solve this problem but it doesn't
> work for omaps neither. I don't know if you saw it but there is some
> discussion here:
>
> https://github.com/tpope/vim-repeat/issues/8
I already saw the discussion, because s
On Thursday, November 29, 2012 11:35:08 PM UTC+9, Kana Natsuno wrote:
> I often define my own text objects. But I noticed that some of them are
> not correctly repeatable with the "." command. I investigated the cause
> of the problem, and found a strange behavior about re
I often define my own text objects. But I noticed that some of them are
not correctly repeatable with the "." command. I investigated the cause
of the problem, and found a strange behavior about repeating an operator
which is executed with a ":" command as a motion.
If an operator is executed wi
On Wednesday, August 1, 2012 7:03:48 AM UTC+9, Lech Lorens wrote:
> From ":help InsertLeave":
>
> *InsertLeave*
> InsertLeave When leaving Insert mode. Also when using
> CTRL-O |i_CTRL-O|. But n
According to the :help i_CTRL-O --
> The CTRL-O command takes you to Normal mode. If you then use a command enter
> Insert mode again it doesn't nest. Thus when typing "aa" and then
> takes you back to Normal mode, you do not need to type twice.
There are several commands to enter Insert mode
On Sun, Feb 12, 2012 at 8:19 AM, Bram Moolenaar wrote:
>
> Patch 7.3.438
> Problem: There is no way to avoid ":doautoall" reading modelines.
> Solution: Add the argument. Adjust documentation.
> Files: src/fileio.c, runtime/doc/autocmd.txt
Thank you for the fix. But this patch deals w
On Mon, Nov 28, 2011 at 4:40 AM, Bram Moolenaar wrote:
>
> Kana Natsuno wrote:
>
>> >From :help :doautocmd in Vim 7.3.353:
>>
>> > *:do* *:doau* *:doautocmd* *E217*
>>
On Fri, Nov 11, 2011 at 10:20 PM, Kana Natsuno
wrote:
> On Fri, Nov 11, 2011 at 10:04 PM, Andy Wokula wrote:
>> :h todo
>>
>> 7 Setting an option always sets "w_set_curswant", while this is only
>> required for a few options. Only do it for those o
On Fri, Nov 11, 2011 at 10:04 PM, Andy Wokula wrote:
> Am 11.11.2011 12:35, schrieb Kana Natsuno:
>>
>> I found that Vim unexpectedly resets "curswant" in some
>> context. Try the following steps to reproduce the problem:
>
> I think this one explains it:
On Tue, Nov 8, 2011 at 4:45 PM, Ingo Karkat wrote:
> You can group events, this makes it even clearer, and no need for :doautocmd:
> augroup MyConfig
> autocmd CursorHold,CursorHoldI * call s:save_stat()
> augroup END
Ah, I forgot about that syntax of :autocmd.
Thank you for the ti
I found that Vim unexpectedly resets "curswant" in some
context. Try the following steps to reproduce the problem:
$ cat foo
1234567890
12345
$ cat test.vim
edit foo
normal! ggf8j
echomsg 'before setting timeoutlen:' string(winsavevi
>From :help :doautocmd in Vim 7.3.353:
> *:do* *:doau* *:doautocmd* *E217*
> :do[autocmd] [group] {event} [fname]
> Apply the autocommands matching [fname] (default:
> current file name) for {event} to the curr
On Fri, Oct 28, 2011 at 6:07 AM, Anand Hariharan
wrote:
> Am using 7.3 with patches 1-46 32 bit Windows Big GUI version with OLE
> support downloaded from vim.org. I also have smartcase and ignorecase
> both set.
>From :help :vimgrep --
> 'ignorecase' applies. To overrule it put |/\c| in the
>
On Sun, 24 Oct 2010 01:28:15 +0900, Bram Moolenaar wrote:
> Suppose someone writes a complicated Vim script, that includes a mapping
> that moves the cursor around, but does not want folds to change. When
> "map" is included in 'foldopen' this would be very difficult.
> It would require the mappi
On Thu, 21 Oct 2010 05:28:53 +0900, Kana Natsuno
wrote:
> After observation on 'foldopen' in 2 years, many users stumbled and
> reported
> the behavior about 'foldopen' and key mappings to vim_dev/vim_use. I
> believe
> that it's not intuitive for mos
On Fri, 22 Oct 2010 02:34:22 +0900, Benjamin R. Haskell wrote:
> If you're starting out with Vim scripting, you'll need to figure out the
> terminology anyway (windows/buffers/tabs=tabpages/etc. which generally
> have names & numbers [but not ID's]), so I don't think the name should
> be changed.
On Thu, 21 Oct 2010 20:00:13 +0900, Chris Sutcliffe wrote:
>> We already use the term "window" to mean a viewport on a buffer.
>> So that the name "v:windowid" may lead to a misunderstanding.
>> It should be renamed "v:xwindowid" etc to express that it's not
>> related to "window" (as a viewport o
On Sep 11 2008, 11:36 am, "Kana Natsuno"
wrote:
> But that's not the problem I asked. The problem is why Vim also checks
> how {pattern} for '/' or '?' was inputted to determine whether folds
> should be opened or not.
After observation on 'foldo
On Thu, 21 Oct 2010 02:18:08 +0900, Bram Moolenaar wrote:
> Patch 7.3.031
> Problem:Can't pass the X window ID to another application.
> Solution: Add v:windowid. (Christian J. Robinson, Lech Lorens)
> Files:runtime/doc/eval.txt, src/eval.c, src/gui.c, src/vim.h,
> src/
On Fri, 08 Oct 2010 21:39:46 +0900, tyru wrote:
> I think syntax and ftplugin should have its own document, like "doc/
> ft_ada.txt", "doc/ft_sql.txt".
> Because almost syntax/ftplugin plugins have global variables to modify
> the behavior.
> But no help, I had to read its plugin file directly.
D
On Sun, 14 Mar 2010 22:53:57 +0900, mobi phil wrote:
> I think it would make enough sense to extend the "textobjects" with
> "af" that would select a function, that is its name, formal parameters
> and the body. One could write a script for it, I know, but the same
> time hundreds of mappings shou
On Tue, 23 Feb 2010 07:12:15 +0900, Marc Weber wrote:
> for vim-addon-manager I added missing metadata myself.
> Eg for the perl browser plugin I added meta data in
> vim-addon-known-repsoitories this way:
>
> " this is mainly used to add missing dependencies
> let s:missing_addon_infos["brows
On Tue, 23 Feb 2010 04:16:20 +0900, c9s wrote:
> beside that, I wish vim.org could provide other script type like
> autoload , class , plugin , ftplugin, compiler,
> ... etc value to "script type" field when uploading new scripts.
I agree with you on that matter, but what do "autoload" and "clas
On Tue, 19 Jan 2010 19:58:16 +0900, Bram Moolenaar wrote:
> I'm wondering if REMAP_NONE should be used for all calls to
> ins_typebuf(). For example, typing:
>
> :cmap hello hello there
> :echo "hello"
> @:
>
> The first hello results in "hello there" (expanded while typing).
>
"@:" - repeat last command-line - doesn't work if ":" is mapped to
something.
The following is a patch to fix this bug.
*** src/ops.c~ Mon Apr 27 17:06:58 2009
--- src/ops.c Tue Jan 19 12:08:41 2010
*** put_in_typebuf(s, esc, colon, silent)
*** 1327,1333
vim_free(p
On Mon, 23 Nov 2009 08:59:37 +0900, pepegnu wrote:
> Consider the following situation, you edit the text (underscore
> represents whitespace):
>
>blah-blah-blah_ here>___blah-blah-blah again
>
> Now, it seems that '_' (underscore) is a free token in the
On Sat, 21 Nov 2009 12:58:58 +0900, Wu, Yue wrote:
> Thanks for info, but I don't understand the logical.
Folded lines are treated as a single line. :help 28.3
> If I don't want this behavior, how to disable it temporaryly?
Use 'foldenable' as follows:
:setlocal nofoldenable
:" Do something
On Sat, 21 Nov 2009 09:53:33 +0900, Wu, Yue wrote:
> 5. Now you will see vim has deleted line 1 to line 5.
>
> When folding is unfolded, then :2,4d will work as expected.
It's an intentional behavior. See :help fold-behavior - it describes:
> For Ex commands the range is adjusted to always sta
On Mon, 12 Oct 2009 05:03:27 +0900, Bram Moolenaar wrote:
> Can you somehow simplify the way to reproduce this and send me the Vim
> script for this?
Sorry, I tried to simplify before reporting but failed. Because the
problem I encountered seems to depend on the number/order of operations,
and
Hello there.
I encountered a problem that Vim always crashes whenever I did some steps.
To reproduce the problem, please try the following command (see the
attached file "vim-crash-test.sh" for the details of the step I did):
/bin/bash vim-crash-test.sh
The crash is caused by a memory access
On Fri, 02 Oct 2009 06:46:13 +0900, Hari Krishna Dara
wrote:
> I went ahead and did a POC for this feature and am attaching the
> patch. This adds a new set of commands such as :dupmap (for "duplicate
> mapping") and it seems to work nicely for a few simple cases that I
> tried. The same do_map(
On Wed, 30 Sep 2009 02:50:25 +0900, Hari Krishna Dara
wrote:
>> Recently I need to copy a key mapping to enhance my plugin. It defines
>> another kind of key mappings which is expanded when multiple keys are
>> simultaneously pressed. These key mappings can coexist with ordinary
>> key mapping
On Wed, 30 Sep 2009 09:23:56 +0900, Charles E Campbell Jr
wrote:
> You could see if cecutil's SaveUserMaps() and RestoreUserMaps()
> functions that I wrote will help you.
It uses maparg() to get information on existing key mapping,
but with maparg(), it's impossible to cover all scenarios
to us
On Sun, 27 Sep 2009 14:58:25 +0900, Hari Krishna Dara
wrote:
> I need to be able to create an imap for when my plugin is
> toggled on, and unmap it when it is toggled off. What I would prefer
> is to restore the previous map of rather than simply unmap it,
> but there is no straight-forward wa
On Sun, 03 May 2009 08:06:13 +0900, Nico Weber wrote:
> Valgrind memory checker finds several errors in vim-7.2 (patches
> 1-148) with the reproduction steps described at
> http://groups.google.com/group/vim_mac/browse_thread/thread/4e0149ff4f84e3d3
> :
Thank you for the patch!
I encountered
On Thu, 16 Apr 2009 22:36:03 +0900, Ingo Karkat wrote:
> Oops, didn't know about that overload of 'a)'... So, any other suggestions?
> 'af'
> (for "file"), 'aB' (captial B for "big buffer")?
>
> As memorizable keys become scarce, maybe it would be best to just take the
> Vimscript implementation
On Sun, 29 Mar 2009 00:01:11 +0900, Lech Lorens wrote:
> The attached patch enhances the behaviour of CTRL-W_CTRL-_ in visual mode.
>
> If CTRL-W_CTRL-_ is pressed in visual mode, Vim will try to change the
> height of the current window to match the visual selection and scroll
> the text so that
On Sat, Dec 6, 2008 at 6:33 AM, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> I wonder if the name "v:motion_force" is the best choice. Does someone
> know a better name?
Though I also (and still) wonder about that, I chose the name from
the definition of struct oparg_S in src/structs.h which has
When I wrote some Vim scripts to implement new motions and new text objects,
I noticed that there is no way to check whether the type of a motion is forced
or not. (e.g. :help o_v is given or not)
I wrote a patch to add the variable v:motion_force which contains the
information about this problem.
On Sat, 29 Nov 2008 06:51:34 +0900, Marc Weber <[EMAIL PROTECTED]> wrote:
> I stumbled uppone one small but important issue:
> funcref('a#foo#Func') barks if the functions hasn't been loaded yet.
> Why is this bad? Because it's no longer lazy.
> Wether the function should be loaded if it doesn't e
Hello, Vimmers.
I wrote a patch[1] that provides Gauche[2] interface to Vim. It
allows to control Vim from Gauche side. For exmaple:
:gauche < 0
(vim-apply "append" '(1 (foo bar baz)))
(vim-eval "&l:modified") ;==> 1
END
Currently it provides very basic API and there is no us
On Thu, 11 Sep 2008 11:05:08 +0900, Tony Mechelynck <[EMAIL PROTECTED]> wrote:
>> noremap! ;
>> noremap! ;
>
> which swaps Enter and semicolon in Insert and Command-line mode. Strange
> idea. So you hit the Enter key to insert a semicolon into text, and you
> hit the semicolon key to b
Hello, Vimmers.
My friend and I noticed a strange behavior of Vim on foldings.
From :help 'foldopen':
> When the command is part of a mapping this option is not used.
For exmaple, with the following setting:
noremap g/ :set incsearch/
folds will be opened by '/' but not opened by 'g/
Hello, Vimmers.
I noticed that abbreviations are not expanded by a character
which are generated by key mappings which cannot be remapped.
There is no description on this behavior in :help as far as
I read. So that it should be noted in :help Abbreviations.
Anyway, I wish there were a pseudo key
Hello, Vimmers.
I noticed that Vim 7.2b.001 still cannot be compiled with with multi-byte
feature but without GUI or clipboard, because check_col() and check_row() are
missing. The following is a patch to fix this problem:
*** ../vim-7.2b.001/src/ui.cMon Jul 14 23:48:48 2008
--- src/ui.c
Hello, Vimmers.
I found a bug in getbufvar(). With {varname} == "", it returns
the dictionary of variables which are local to the current buffer
instead of the buffer specified by {expr}. It should return the
dictionary for the latter buffer.
I wrote a patch to fix this bug. See the attached f
On Jun 17, 1:17 pm, Ben Schmidt wrote:
> The runtime files are not included in the source patches. You need to
> download them separately to get the latest version. See
>
> http://www.vim.org/runtime.php
Oops, I didn't know that.
Thanks for your information.
--~--~-~--~~~-
On Tue, 17 Jun 2008 03:49:19 +0900, Bram Moolenaar wrote:
> The current version of this file doesn't set 'encoding' at all.
> Should work fine.
Really? I checked with the following steps and environment, it
does set 'encoding' to latin1.
$ vim -u NONE -U NONE --noplugin
:set nocompatible
:set en
Hello, Vimmers.
I noticed that runtime/doc/ada.txt contains "encoding=latin1" in its modelines.
It must change 'fileencoding' instead of 'encoding', because changing 'encoding'
is troublesome for most users who don't use Vim with encoding=latin1.
The following is a simple patch to fix the problem.
53 matches
Mail list logo
