On May 11, 8:54 pm, Marc Weber wrote:
> ...copy pasting that code or running
> setlocal omnifunc=syntaxcomplete#Complete in any way is all you have to
> do to make c-x c-o work. Don't know exactly how the script_id 3172
> differs from that implementation (You may find out by looking at authors
> d
Hi Gary!
On Mo, 14 Mai 2012, Gary Johnson wrote:
> On 2012-05-14, Christian Brabandt wrote:
>
> > This patch fixes a data conversion error, that leads to a data loss.
> > Problem is, that open() is done, even though it is not clear, conversion
> > will work. So this patch runs buf_write_bytes(
Thanks.
I had come across DrawIt earlier while trying to find out
how to get the extended box drawing characters to render
with my Vim-xterm combination.
On 05/14/2012 11:31 AM, Charles E Campbell wrote:
On May 14, 2012, at 12:59 PM, richard emberson
wrote:
This post is with regards to usi
On 2012-05-14, Ben Fritz wrote:
> On Monday, May 14, 2012 1:34:52 PM UTC-5, Gary Johnson wrote:
> >
> > How much slower is it for a file large enough that the write times
> > are more than a second?
> >
> > I don't think we want to noticeably slow down Vim for everyone all
> > the time in order t
Am 14.05.2012 20:21, schrieb Christian Brabandt:
Bram,
On Mo, 14 Mai 2012, Sergey Khorev wrote:
Can someone write a clean statement of the problem (the file
contents and the commands that led to the behaviour that was
unexpected). Just the facts, without opinions on Vim or users.
This is how I
On Monday, May 14, 2012 1:34:52 PM UTC-5, Gary Johnson wrote:
>
> How much slower is it for a file large enough that the write times
> are more than a second?
>
> I don't think we want to noticeably slow down Vim for everyone all
> the time in order to more-conveniently avoid an error that is
> o
On 2012-05-14, Christian Brabandt wrote:
> This patch fixes a data conversion error, that leads to a data loss.
> Problem is, that open() is done, even though it is not clear, conversion
> will work. So this patch runs buf_write_bytes() twice, first time is to
> check that each character can be
On May 14, 2012, at 12:59 PM, richard emberson
wrote:
> This post is with regards to using extended
> box drawing characters in console Vim running
> in a xterm on Linux. Specifically, its about
> getting Vim to display not just the simple
> box drawing characters like "cntl-V u 2500"
> or "cn
Bram,
On Mo, 14 Mai 2012, Sergey Khorev wrote:
> > Can someone write a clean statement of the problem (the file
> > contents and the commands that led to the behaviour that was
> > unexpected). Just the facts, without opinions on Vim or users.
>
> This is how I managed to reproduce. Create a file:
This post is with regards to using extended
box drawing characters in console Vim running
in a xterm on Linux. Specifically, its about
getting Vim to display not just the simple
box drawing characters like "cntl-V u 2500"
or "cntl-V u 250C" (which can be entered
with cntl-K as digraphs) but also t
On Mon, 14 May 2012, Ben Fritz wrote:
On Saturday, May 12, 2012 9:59:44 AM UTC-5, google wrote:
Hello,
This concerns ":help ident-search"
I don't see a :help indent-search in my Vim installation.
:h ident-search
'ident' as in 'identifier', not 'indent'.
-- how would one modify the tip
On Saturday, May 12, 2012 9:59:44 AM UTC-5, google wrote:
> Hello,
>
> This concerns ":help ident-search" -- how would one modify the tip to
> collect the results in a quickfix-file and use commands like :copen etc.?
>
I don't see a :help indent-search in my Vim installation. Assuming it uses a
> Can someone write a clean statement of the problem (the file
> contents and the commands that led to the behaviour that was
> unexpected). Just the facts, without opinions on Vim or users.
This is how I managed to reproduce. Create a file:
--- snip ---
# vim: set fileencoding=cp8
On Saturday, May 12, 2012 1:51:14 AM UTC-5, Erik Christiansen wrote:
> On 11.05.12 13:58, Benjamin Fritz wrote:
> > The attached is sort of what I had in mind (the look, not the markup...I
> > wrote it by hand from scratch). It has the look from Vim but you're able to
> > click on it as you'd expec
On Friday, May 11, 2012 8:41:20 PM UTC-5, Paul wrote:
> Will do...as soon as I find the circumstances that gave rise to the
> problem. It doesn't always seem to exhibit itself.
>
I know on Windows, Vim sometimes changes directories to the file's path when
passed an absolute path to the file. I
On Sunday, May 13, 2012 3:10:33 AM UTC-5, Toddintr wrote:
> For the first time ever since I started using Vim, I lost a file. I had
> a modeline that specified an "encoding" setting for a Python script.
> Vim complained when opening the file. I googled for a solution, decided
> to try fileencodin
On Monday, May 14, 2012 3:04:33 AM UTC-5, Jonathan del Strother wrote:
> Hi,
> I'm using fugitive's :Ggrep (a git-based wrapper around vimgrep) to
> scan for occurrences of a word in my project, viewing them in the
> quickfix window. I end up with quite a few results, and it's not
> obvious which
On Monday, May 14, 2012 7:01:17 AM UTC-5, Jan wrote:
> When I close a tab, I'd like vim to take me back to the last tab that I was
> in, rather than the next in line. For example:
>
> I have several tabs open:
>
> [1] [2] [3]
>
> I'm in tab [1]. I open a new tab, [a], which opens after tab [1]:
On Monday, May 14, 2012 8:24:51 AM UTC-5, miles christopher wrote:
> I want to edit snippet file in a new split window instead of current window.
> Because edit in current window will close current file.
>
> bellowing is a solution to solve this:
> But I do not know how to use variable &filetype b
On Thu, May 10, 2012 at 12:20 PM, Tim Chase wrote:
> I occasionally issue a "$VCS blame" command (where $VCS may be
> subversion, git, or mercurial in most of my use cases). It would be
> nice to be able to see the original source in its "natural" syntax
> highlighting, ignoring the blame leader
On Mon, May 14, 2012 at 4:19 PM, Benjamin R. Haskell wrote:
> A lot of people seem to like remapping CapsLock to Esc. (Which needs to be
> done at the O/S level.) And if you're in gvim (not terminal vim, right
> now), you can use:
>
> " :ino[remap]
> ino
>
Thanks. Actually, I do have CapsLock
I want to edit snippet file in a new split window instead of current window.
Because edit in current window will close current file.
bellowing is a solution to solve this:
But I do not know how to use variable &filetype behind command
:NeoComplCacheEditSnippets.
If you have any idea, please tell
On Mon, 14 May 2012, Dotan Cohen wrote:
On Mon, May 14, 2012 at 3:48 PM, Benjamin R. Haskell wrote:
In any case, by far _most_ of the leading characters are used
outside the mappings, so it is the common case that is being made
annoying for the sake of the uncommon case. If need be, I would
p
On Mon, May 14, 2012 at 3:48 PM, Benjamin R. Haskell wrote:
> See the Eatchar function in the help for map.txt:
> :help map.txt | /Eatchar
>
> I use the following variant of Eatchar (since '\s' is the common case):
>
> fun! Eatchar(...)
> let c = nr2char(getchar(0))
> return c =~ (a:0 ? a:1
Excerpts from Pablo Giménez's message of Mon May 14 12:25:42 +0200 2012:
> Yep I know, just thinking ahead if having a big runtimepath can make things
> slower.
You're right. I'm fine with writing experimental code merging all
runtimepaths into a .vim/ so that you can benchmark the difference and
w
On Mon, 14 May 2012, Dotan Cohen wrote:
On Sun, May 13, 2012 at 9:37 PM, Tim Chase wrote:
On 05/13/12 10:58, Dotan Cohen wrote:
I have a few of these wonderful helpers:
inoremap foreach foreach (){}3kA
I know that there is a snippets plugin, but I like this roll-my-own
solution for a number
>> Error detected while processing function42_NetrwMarkFileMove:
>> line 23:
>> E121: Undefined variable: s:netrwMarkfilelist_35
>> E15: Invalid expression: s:netrwMarkfilelist_{bufnr("%")}
>>
>>
>
> Could you please provide me with a sequence of actions that elicit this
> message?
> (I've tried
On Sun, May 13, 2012 at 9:37 PM, Tim Chase wrote:
> On 05/13/12 10:58, Dotan Cohen wrote:
>> I have a few of these wonderful helpers:
>> inoremap foreach foreach (){> eturn>}3kA
>>
>> I know that there is a snippets plugin, but I like this roll-my-own
>> solution for a number of reasons (one of w
When I close a tab, I'd like vim to take me back to the last tab that I was in,
rather than the next in line. For example:
I have several tabs open:
[1] [2] [3]
I'm in tab [1]. I open a new tab, [a], which opens after tab [1]:
[1] [a] [2] [3]
I'm now in my new tab, [a]. I close it:
[1] [2]
On 14 May 2012 11:43, John Beckett wrote:
> Karthick Gururaj wrote:
>>
>> :noremap
>
> Yes, however it should be a buffer mapping, and you might like
> to use a different key, such as o to open the file:
>
> nnoremap o p
>
> Put the above line in file ~/.vim/after/ftplugin/qf.vim (Unix)
Nifty,
Thanks Chris greatly appreciated. I will.
--jerry
On Mon, May 14, 2012 at 5:50 AM, Christian Brabandt wrote:
> On Mon, May 14, 2012 12:36, Gerald Klein wrote:
> > Tim Hi and thanks for the info, I went in and commented out the lines, it
> > appears that it working, so thanks. One question what l
On Mon, May 14, 2012 12:36, Gerald Klein wrote:
> Tim Hi and thanks for the info, I went in and commented out the lines, it
> appears that it working, so thanks. One question what language are they
> using in these syntax files?
This is VimL which you can read about at :h eval.txt
You should poss
Karthick Gururaj wrote:
>
> :noremap
Yes, however it should be a buffer mapping, and you might like
to use a different key, such as o to open the file:
nnoremap o p
Put the above line in file ~/.vim/after/ftplugin/qf.vim (Unix)
or file $HOME\vimfiles\after\ftplugin\qf.vim (Windows).
Create an
Paul wrote:
> I think you're both right. He should have read the warning
> message, but also I'm surprised that vim modified the file
> before being given any instruction to write it.
The discussion got very ranty earlier (folks, there is no need
to kick the guy, just be glad it wasn't you), and I
Tim Hi and thanks for the info, I went in and commented out the lines, it
appears that it working, so thanks. One question what language are they
using in these syntax files?
thanks again.
--jerry
On Sun, May 13, 2012 at 7:49 PM, Tim Chase wrote:
> On 05/13/12 12:48, Gerald Klein wrote:
> > H
2012/5/11 Marc Weber
> Activating a plugin does not cause much overhead , only a path to
> &runtimepath is added unless the plugin also has plugin/*.vim files.
>
Yep I know, just thinking ahead if having a big runtimepath can make things
slower.
>
> So make me understand what's wrong with always
On Sunday, 13 May, 2012 at 13:31:38 BST, Christian Brabandt wrote:
You get a warning, that writing failed and the file may possibly be
corrupt. Vim even tells you, what you should do to write without
converting the content. What else should Vim do?
I don't understand, what Vim should possibly re
On Mon, May 14, 2012 at 1:34 PM, Jonathan del Strother
wrote:
>
> Hi,
> I'm using fugitive's :Ggrep (a git-based wrapper around vimgrep) to
> scan for occurrences of a word in my project, viewing them in the
> quickfix window. I end up with quite a few results, and it's not
> obvious which file I
Hi,
I'm using fugitive's :Ggrep (a git-based wrapper around vimgrep) to
scan for occurrences of a word in my project, viewing them in the
quickfix window. I end up with quite a few results, and it's not
obvious which file I'm interested in without opening the file. When I
hit enter in the quickfi
On Sunday, May 13, 2012 1:49:42 AM UTC+12, Andrew Spano wrote:
> If I try to give vim multiple
> file arguments when starting vim, it will just open up the first one
> provided.
Are you starting vim from a CLI, like win XP's cmd.exe? There may be a batch
file getting in the way, called vim.bat
40 matches
Mail list logo
