Re: Packages

On 2016-03-07, Bram Moolenaar wrote: > Eric Christopherson wrote: > > > On Sun, Mar 06, 2016, Benjamin Fritz wrote: > > [in attachment] > > > +directory under your package, whereas plugins you enable on demand go in > > > an > > > +"opt" directory so that |:packadd| can find them. See |pack-add|

Re: Is there any way to count all latin characters in utf-8 as 1 byte?

2016-03-08 1:32 GMT+03:00 rameo : > >> In Python you are not using *byte* counts, it indexes *unicode >> codepoints*. You may convert unicode Python objects to bytes objects >> by using `string.encode(vim.options['encoding'])`, use >> `.decode(vim.options['encoding'])` to convert

Re: Packages

On 2016-03-07, Eric Christopherson wrote: > On Sun, Mar 06, 2016, Benjamin Fritz wrote: > [in attachment] > > +directory under your package, whereas plugins you enable on demand go in an > > +"opt" directory so that |:packadd| can find them. See |pack-add| below. > > OK, I see that the intended

Re: Is there any way to count all latin characters in utf-8 as 1 byte?

> In Python you are not using *byte* counts, it indexes *unicode > codepoints*. You may convert unicode Python objects to bytes objects > by using `string.encode(vim.options['encoding'])`, use > `.decode(vim.options['encoding'])` to convert back. bytes objects are > indexed by bytes. You may

Re: Packages

Ben Fritz wrote: > > > For Pathogen, you install by unzipping all files for a plugin, into a > > > directory under "bundle": > > > > > > ~/.vim/bundle/someplugin/plugin/foo.vim > > > ~/.vim/bundle/someplugin/autoload/bar.vim > > > ~/.vim/bundle/someplugin/syntax/beez.vim > > > > > >

Re: Packages

Eric Christopherson wrote: > On Sun, Mar 06, 2016, Benjamin Fritz wrote: > [in attachment] > > +directory under your package, whereas plugins you enable on demand go in an > > +"opt" directory so that |:packadd| can find them. See |pack-add| below. > > OK, I see that the intended semantics of

Re: Packages

On Mon, Mar 07, 2016, Nikolay Aleksandrovich Pavlov wrote: > Without isolated namespaces this is absolutely useless behaviour. If A > depends on B, C depends on B and D does not depend on anything and > plugin manager created packages (A,B1), (C,B2) and (D) then out of B1 > and B2 there will be

Re: Packages

On Sun, Mar 06, 2016, Benjamin Fritz wrote: [in attachment] > +directory under your package, whereas plugins you enable on demand go in an > +"opt" directory so that |:packadd| can find them. See |pack-add| below. OK, I see that the intended semantics of the word "ever" is as a synonym of

Jump to last modified buffer

Say I have lots of buffers open, because I've been navigating all over the place in my project. How can I quickly jump back to the buffer (and position) that I last modified? "g;" and ":changes" appear to be buffer local, and ":jumps" doesn't tell me which one was last modified. I could set a

Re: Highlighting matches in quickfix buffer

On Monday, 07 March, 2016 at 15:52:38 GMT, Ben Fritz wrote: Search for the string you used in the grep command, or use :match. There's no automatic way. OK, thanks. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying

Re: How do I add the option +xterm_clipboard to terminal vim

On 2016-03-07, Bee wrote: > On Sunday, March 6, 2016 at 11:26:21 PM UTC-8, Gary Johnson wrote: > > On 2016-03-06, Bee wrote: > > > How do I add the option +xterm_clipboard to terminal vim? > > > > > > I can compile vim with all patches, > > > but do not know how to get the option

Re: Highlighting matches in quickfix buffer

On Monday, March 7, 2016 at 8:40:46 AM UTC-6, Jan wrote: > Is it possible to have the searched for string highlighted in the quickfix > and location list buffers, just as grep's --colour does? It can be confusing > when the results of a search contain long lines, and I just want to skim the >

Re: How do I add the option +xterm_clipboard to terminal vim

On Sunday, March 6, 2016 at 11:26:21 PM UTC-8, Gary Johnson wrote: > On 2016-03-06, Bee wrote: > > How do I add the option +xterm_clipboard to terminal vim? > > > > I can compile vim with all patches, > > but do not know how to get the option +xterm_clipboard. > > I think you will get

Highlighting matches in quickfix buffer

Is it possible to have the searched for string highlighted in the quickfix and location list buffers, just as grep's --colour does? It can be confusing when the results of a search contain long lines, and I just want to skim the results with my eyes, rather than manually visit each result to

Re: Referring to a buffer, and :help help

I was just about to ask if there's a shorter way of doing ":tabedit | b partialname" to open a tab preloaded with a hidden buffer, but discovered it can be done with ":tabe sb partialname", so this post is just for anyone else wondering how it's done :) -- -- You received this message from the

Re: Is there any way to count all latin characters in utf-8 as 1 byte?

2016-03-07 14:54 GMT+03:00 rameo : > I use searchpos() to capture start/endcolumns of a matches. > Then I use the results in Python code to transform the text. > > However I noted that latin characters as 'èéàòìù' are counted as 1 byte in > Python but 2 bytes in Vim and the

Is there any way to count all latin characters in utf-8 as 1 byte?

I use searchpos() to capture start/endcolumns of a matches. Then I use the results in Python code to transform the text. However I noted that latin characters as 'èéàòìù' are counted as 1 byte in Python but 2 bytes in Vim and the output is not as expected. Is there any way to resolve this

Re: Packages

2016-03-07 8:24 GMT+03:00 Benjamin Fritz : > > > On Sat, Mar 5, 2016 at 7:27 AM, Bram Moolenaar wrote: >> >> >> Ben Fritz wrote: >> > >> > For Pathogen, you install by unzipping all files for a plugin, into a >> > directory under "bundle": >> > >> >

Re: How do I add the option +xterm_clipboard to terminal vim

On 06.03.16 20:23, Bee wrote: > How do I add the option +xterm_clipboard to terminal vim? > > I can compile vim with all patches, > but do not know how to get the option +xterm_clipboard. It is a "configure" option. This shows running ./configure with a couple of options: