That is strange .. Is csv support CKJ (like chinese) well?
I did get stuck in a Chinese csv file and ctl-c doesn't help. I had to kill vim manually. CPU is like 80% or more by vim.
Thanks!
On Nov 30, 2013, at 16:13, Christian Brabandt <cblists@256bit.org> wrote:
> Hi Nikolay!
>
> On So, 01 Dez 2013, Nikolay Pavlov wrote:
>
>> On Dec 1, 2013 12:33 AM, "Christian Brabandt" <cblists@256bit.org> wrote:
>>>
>>> Hi ping!
>>>
>>> On Fr, 29 Nov 2013, ping song wrote:
>>>
>>>> csv plugin is nice, but for some reason when I open a large file it take
>>>> forever to load and then freeze. Ctrl-c doesn't help.
>>>
>>> Actually, Ctrl-C should always abort. I have never seen, when Ctrl-C
>>> does not abort a command. Note, that using :ArrangeColumn (either
>>> explicitly or implicitly using an autocommand (:h csv-arrange-autocmd))
>>> or using dynamic filters can slow down the plugin considerably when used
>>> with large files. My advise is, to simply avoid those commands for large
>>> csv files.
>>
>> It will not abort if code is written not in VimL or if somebody is catching
>> Vim:Interrupt and resumes computations. Assuming "Ctrl-c doesn't help"
>> means "Ctrl-c does not abort" it is most likely the first because sane
>> developers do not do the second.
>
> Neither does the csv plugin.
>
> Best,
> Christian
> --
> "Unter allen Völkerschaften haben die Griechen den Traum des
> Lebens am schönsten geträumt."
> -- Goethe, Maximen und Reflektionen, Nr. 435
>
> --
> --
> You received this message from the "vim_use" 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
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Saturday, November 30, 2013
Re: Location list autocommand
I managed to accomplish what I wanted with the following:
au! BufWinEnter quickfix nnoremap <silent> <buffer> q :cclose<cr>:lclose<cr>
Since there seems to be no way to distinguish a quickfix from a
location-list I just execute both commands and it works as
expected(the other one is just silently ignored)
In any case thanks for your help
On Sat, Nov 30, 2013 at 5:20 PM, Ben Fritz <fritzophrenic@gmail.com> wrote:
> On Saturday, November 30, 2013 6:51:45 AM UTC-6, Thiago de Arruda wrote:
>> Could you give an example? My requirement is very simple: I want to
>>
>> bind the letter 'q' to ':lclose<cr>' for location-list and to
>>
>> ':cclose<cr>' do I can use 'q' to quickly close quickfix or
>>
>> location-list(both have filetype qf). As I said I managed to do it for
>>
>> quickfix, not for location-list
>>
>>
>
> Example:
>
> autocmd BufWinEnter * if &ft=="qf" | echomsg "I'm in quickfix!" | endif
>
> This seems to work for me. Replace echomsg with your desired mapping. Make sure you make the mapping buffer-local.
>
> --
> --
> You received this message from the "vim_use" 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
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
au! BufWinEnter quickfix nnoremap <silent> <buffer> q :cclose<cr>:lclose<cr>
Since there seems to be no way to distinguish a quickfix from a
location-list I just execute both commands and it works as
expected(the other one is just silently ignored)
In any case thanks for your help
On Sat, Nov 30, 2013 at 5:20 PM, Ben Fritz <fritzophrenic@gmail.com> wrote:
> On Saturday, November 30, 2013 6:51:45 AM UTC-6, Thiago de Arruda wrote:
>> Could you give an example? My requirement is very simple: I want to
>>
>> bind the letter 'q' to ':lclose<cr>' for location-list and to
>>
>> ':cclose<cr>' do I can use 'q' to quickly close quickfix or
>>
>> location-list(both have filetype qf). As I said I managed to do it for
>>
>> quickfix, not for location-list
>>
>>
>
> Example:
>
> autocmd BufWinEnter * if &ft=="qf" | echomsg "I'm in quickfix!" | endif
>
> This seems to work for me. Replace echomsg with your desired mapping. Make sure you make the mapping buffer-local.
>
> --
> --
> You received this message from the "vim_use" 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
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Search and stay
Andrew Stewart <boss@airbladesoftware.com> a écrit:
> > Based on this very real annoyance, and having a little bit of time to kill, I
> > wrote the code below: not only does it removes the 'hlsearch' problem, but it
> > also makes search easier by foregrounding matches and letting you jump from
> > one to the next without leaving the search. I find it quite comfortable, but
> > of course others might find that just terrible. Here's how it works:
>
>
> I really like this – thanks!
>
> > If anybody is interested, I can make that into a plugin (rewriting it a little
> > bit less sloppily, because it will fail in some cases, plus it requires a few
> > options to be really interesting), in case, of course, such a plugin does not
> > already exist :)
>
>
> That would be great, if you have the time. I'd prefer to drop in a plugin that enlarge my vimrc.
Not so easy after all if you want things to work properly and with a
few interesting bells and whistles.
I'm working on it, but it'll take more time than expected (it always
does). At least I have the plugin's name: spotlight. That part I'm
quite satisfied with!
Best,
Paul
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> > Based on this very real annoyance, and having a little bit of time to kill, I
> > wrote the code below: not only does it removes the 'hlsearch' problem, but it
> > also makes search easier by foregrounding matches and letting you jump from
> > one to the next without leaving the search. I find it quite comfortable, but
> > of course others might find that just terrible. Here's how it works:
>
>
> I really like this – thanks!
>
> > If anybody is interested, I can make that into a plugin (rewriting it a little
> > bit less sloppily, because it will fail in some cases, plus it requires a few
> > options to be really interesting), in case, of course, such a plugin does not
> > already exist :)
>
>
> That would be great, if you have the time. I'd prefer to drop in a plugin that enlarge my vimrc.
Not so easy after all if you want things to work properly and with a
few interesting bells and whistles.
I'm working on it, but it'll take more time than expected (it always
does). At least I have the plugin's name: spotlight. That part I'm
quite satisfied with!
Best,
Paul
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Type Mac Command symbol in vim
Thanks. Can this be made into the vim default installation?
On Sat, Nov 30, 2013 at 5:47 PM, Tim Chase <vim@tim.thechases.com> wrote:
> On 2013-11-30 17:39, Peng Yu wrote:
>> digraph is a powerful way to typing many symbols. But I don't see a
>> Mac Command symbol available. Is there a way to type Mac Command
>> symbol in vim? Thanks.
>
> A quick experimentation shows this works on mine:
>
> :digraph %% 8984
>
> and then you can use "%%" to enter the cloverleaf in vim's digraph
> mode (after pressing control+K). This is obviously subject to
> 'encoding' and 'fencoding' settings, but with both set to "utf8", it
> works for me in gvim.
>
> -tim
>
>
>
--
Regards,
Peng
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Sat, Nov 30, 2013 at 5:47 PM, Tim Chase <vim@tim.thechases.com> wrote:
> On 2013-11-30 17:39, Peng Yu wrote:
>> digraph is a powerful way to typing many symbols. But I don't see a
>> Mac Command symbol available. Is there a way to type Mac Command
>> symbol in vim? Thanks.
>
> A quick experimentation shows this works on mine:
>
> :digraph %% 8984
>
> and then you can use "%%" to enter the cloverleaf in vim's digraph
> mode (after pressing control+K). This is obviously subject to
> 'encoding' and 'fencoding' settings, but with both set to "utf8", it
> works for me in gvim.
>
> -tim
>
>
>
--
Regards,
Peng
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Type Mac Command symbol in vim
On 2013-11-30 17:39, Peng Yu wrote:
> digraph is a powerful way to typing many symbols. But I don't see a
> Mac Command symbol available. Is there a way to type Mac Command
> symbol in vim? Thanks.
A quick experimentation shows this works on mine:
:digraph %% 8984
and then you can use "%%" to enter the cloverleaf in vim's digraph
mode (after pressing control+K). This is obviously subject to
'encoding' and 'fencoding' settings, but with both set to "utf8", it
works for me in gvim.
-tim
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> digraph is a powerful way to typing many symbols. But I don't see a
> Mac Command symbol available. Is there a way to type Mac Command
> symbol in vim? Thanks.
A quick experimentation shows this works on mine:
:digraph %% 8984
and then you can use "%%" to enter the cloverleaf in vim's digraph
mode (after pressing control+K). This is obviously subject to
'encoding' and 'fencoding' settings, but with both set to "utf8", it
works for me in gvim.
-tim
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Type Mac Command symbol in vim
Hi,
digraph is a powerful way to typing many symbols. But I don't see a
Mac Command symbol available. Is there a way to type Mac Command
symbol in vim? Thanks.
--
Regards,
Peng
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
digraph is a powerful way to typing many symbols. But I don't see a
Mac Command symbol available. Is there a way to type Mac Command
symbol in vim? Thanks.
--
Regards,
Peng
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Runtime problem
On 30/11/2013 22:02, Phil Dobbin wrote:
> Hi, all.
>
> I installed Vim 7.3.429 via 'apt-get install' on a Vagrant Ubuntu 12.04
> 32 bit Virtual Machine hosted on Ubuntu 13.10 & Vim doesn't recognise
> any plugins.
[snip]
Please ignore. Problem solved, file under 'operator error' ;-)
Cheers,
Phil...
--
currently (ab)using
Arch Linux, CentOS 6.4, Debian Squeeze & Wheezy, Fedora 19 & 20, OS X
Snow Leopard & Tiger, Ubuntu Quantal & Saucy
GnuGPG Key : http://phildobbin.org/publickey.asc
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Hi, all.
>
> I installed Vim 7.3.429 via 'apt-get install' on a Vagrant Ubuntu 12.04
> 32 bit Virtual Machine hosted on Ubuntu 13.10 & Vim doesn't recognise
> any plugins.
[snip]
Please ignore. Problem solved, file under 'operator error' ;-)
Cheers,
Phil...
--
currently (ab)using
Arch Linux, CentOS 6.4, Debian Squeeze & Wheezy, Fedora 19 & 20, OS X
Snow Leopard & Tiger, Ubuntu Quantal & Saucy
GnuGPG Key : http://phildobbin.org/publickey.asc
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Trouble with getpos()/setpos().
Christian Brabandt <cblists@256bit.org> a écrit:
> Hi Paul!
>
> On Sa, 30 Nov 2013, Paul Isambert wrote:
>
> > > You are in *linewise* visual mode, so it doesn't really make sense, to
> > > have the column somewhere different then either 0 or MAXCOLUMN.
> >
> > Thanks Christian, I'm not in linewise visual mode, but just after I've
> > left it; I would understand if I were still in that mode, but that's
> > not the case.
>
> Actually, you are, since that mode is remembered for I think gv.
Indeed. But then it really looks like a bug to me, or at least an
unwanted side-effect; you can't rely on a function that depends on the
last – unknown – mode and doesn't work half of the time. Or does that
serve any purpose?
Best,
Paul
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Hi Paul!
>
> On Sa, 30 Nov 2013, Paul Isambert wrote:
>
> > > You are in *linewise* visual mode, so it doesn't really make sense, to
> > > have the column somewhere different then either 0 or MAXCOLUMN.
> >
> > Thanks Christian, I'm not in linewise visual mode, but just after I've
> > left it; I would understand if I were still in that mode, but that's
> > not the case.
>
> Actually, you are, since that mode is remembered for I think gv.
Indeed. But then it really looks like a bug to me, or at least an
unwanted side-effect; you can't rely on a function that depends on the
last – unknown – mode and doesn't work half of the time. Or does that
serve any purpose?
Best,
Paul
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Trouble with getpos()/setpos().
Hi Paul!
On Sa, 30 Nov 2013, Paul Isambert wrote:
> > You are in *linewise* visual mode, so it doesn't really make sense, to
> > have the column somewhere different then either 0 or MAXCOLUMN.
>
> Thanks Christian, I'm not in linewise visual mode, but just after I've
> left it; I would understand if I were still in that mode, but that's
> not the case.
Actually, you are, since that mode is remembered for I think gv.
Best,
Christian
--
Es ist höchste Zeit, sich wieder zum Atheismus zu bekennen.
-- Friedrich Dürrenmatt
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Sa, 30 Nov 2013, Paul Isambert wrote:
> > You are in *linewise* visual mode, so it doesn't really make sense, to
> > have the column somewhere different then either 0 or MAXCOLUMN.
>
> Thanks Christian, I'm not in linewise visual mode, but just after I've
> left it; I would understand if I were still in that mode, but that's
> not the case.
Actually, you are, since that mode is remembered for I think gv.
Best,
Christian
--
Es ist höchste Zeit, sich wieder zum Atheismus zu bekennen.
-- Friedrich Dürrenmatt
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Runtime problem
Hi, all.
I installed Vim 7.3.429 via 'apt-get install' on a Vagrant Ubuntu 12.04
32 bit Virtual Machine hosted on Ubuntu 13.10 & Vim doesn't recognise
any plugins.
I always use Vundle & have installed, from GitHub, that & my Vim runtime
many, many times but this time no go.
Vim recognises some commands in my vimrc but not all of them & I get a
'E492' when I try to access any plugin via a mapping (the error message
does mention the plugin I'm trying to use).
I'm totally at a loss to explain it or fix it.
Any help appreciated.
Cheers,
Phil...
--
currently (ab)using
Arch Linux, CentOS 6.4, Debian Squeeze & Wheezy, Fedora 19 & 20, OS X
Snow Leopard & Tiger, Ubuntu Quantal & Saucy
GnuGPG Key : http://phildobbin.org/publickey.asc
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I installed Vim 7.3.429 via 'apt-get install' on a Vagrant Ubuntu 12.04
32 bit Virtual Machine hosted on Ubuntu 13.10 & Vim doesn't recognise
any plugins.
I always use Vundle & have installed, from GitHub, that & my Vim runtime
many, many times but this time no go.
Vim recognises some commands in my vimrc but not all of them & I get a
'E492' when I try to access any plugin via a mapping (the error message
does mention the plugin I'm trying to use).
I'm totally at a loss to explain it or fix it.
Any help appreciated.
Cheers,
Phil...
--
currently (ab)using
Arch Linux, CentOS 6.4, Debian Squeeze & Wheezy, Fedora 19 & 20, OS X
Snow Leopard & Tiger, Ubuntu Quantal & Saucy
GnuGPG Key : http://phildobbin.org/publickey.asc
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Trouble with getpos()/setpos().
Christian Brabandt <cblists@256bit.org> a écrit:
> Hi Paul!
>
> On Sa, 30 Nov 2013, Paul Isambert wrote:
>
> > Hello all,
> >
> > I've encountered a behavior which really smells like a bug, but I'd
> > like to check here beforehand to be sure:
> >
> > Go into linewise visual mode and leave it. Show the position of the '> mark with:
> >
> > echo getpos("'>")
> >
> > It returns something like (if you were on line 23):
> >
> > [0, 23, 2147483647, 0]
> >
> > where the very big value for the column means you were in linewise
> > visual mode. Now try to set the '> mark with e.g.:
> >
> > echo setpos("'>", [0, 25, 12, 0])
> >
> > "0" is echoed, meaning nothing went wrong. Use "getpos("'>")" again to see
> > the position of the mark, this time you'll see:
> >
> > [0, 25, 2147483647, 0]
> >
> > The line was changed, but not the column. And it seems to happen
> > whenever the column number has that big value, i.e. whenever you went
> > into linewise visual mode.
> >
> > Am I missing something?
>
> You are seeing implementation details, leaking into the Vim API.
>
> You are in *linewise* visual mode, so it doesn't really make sense, to
> have the column somewhere different then either 0 or MAXCOLUMN.
Thanks Christian, I'm not in linewise visual mode, but just after I've
left it; I would understand if I were still in that mode, but that's
not the case.
> Also note, that '< will always be the upper position of these two marks
> within the buffer, while '> will always be the lower position of those
> two marks. (e.g. you can't set '> to a lower line then '< and you can't
> set '< to a larger line number then '>)
I'd noticed that. Actually, if you try to set '> before '<, the former
is set to the current value of the latter, which is set to the new
value.
> Das muß ein Esel sein, der mit fünfzig Jahren noch dieselben
> Anschauungen hat wie vor zwanzig Jahren.
> -- Otto von Bismarck
Good ol' Otto :)
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Hi Paul!
>
> On Sa, 30 Nov 2013, Paul Isambert wrote:
>
> > Hello all,
> >
> > I've encountered a behavior which really smells like a bug, but I'd
> > like to check here beforehand to be sure:
> >
> > Go into linewise visual mode and leave it. Show the position of the '> mark with:
> >
> > echo getpos("'>")
> >
> > It returns something like (if you were on line 23):
> >
> > [0, 23, 2147483647, 0]
> >
> > where the very big value for the column means you were in linewise
> > visual mode. Now try to set the '> mark with e.g.:
> >
> > echo setpos("'>", [0, 25, 12, 0])
> >
> > "0" is echoed, meaning nothing went wrong. Use "getpos("'>")" again to see
> > the position of the mark, this time you'll see:
> >
> > [0, 25, 2147483647, 0]
> >
> > The line was changed, but not the column. And it seems to happen
> > whenever the column number has that big value, i.e. whenever you went
> > into linewise visual mode.
> >
> > Am I missing something?
>
> You are seeing implementation details, leaking into the Vim API.
>
> You are in *linewise* visual mode, so it doesn't really make sense, to
> have the column somewhere different then either 0 or MAXCOLUMN.
Thanks Christian, I'm not in linewise visual mode, but just after I've
left it; I would understand if I were still in that mode, but that's
not the case.
> Also note, that '< will always be the upper position of these two marks
> within the buffer, while '> will always be the lower position of those
> two marks. (e.g. you can't set '> to a lower line then '< and you can't
> set '< to a larger line number then '>)
I'd noticed that. Actually, if you try to set '> before '<, the former
is set to the current value of the latter, which is set to the new
value.
> Das muß ein Esel sein, der mit fünfzig Jahren noch dieselben
> Anschauungen hat wie vor zwanzig Jahren.
> -- Otto von Bismarck
Good ol' Otto :)
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Trouble with getpos()/setpos().
Hi Paul!
On Sa, 30 Nov 2013, Paul Isambert wrote:
> Hello all,
>
> I've encountered a behavior which really smells like a bug, but I'd
> like to check here beforehand to be sure:
>
> Go into linewise visual mode and leave it. Show the position of the '> mark with:
>
> echo getpos("'>")
>
> It returns something like (if you were on line 23):
>
> [0, 23, 2147483647, 0]
>
> where the very big value for the column means you were in linewise
> visual mode. Now try to set the '> mark with e.g.:
>
> echo setpos("'>", [0, 25, 12, 0])
>
> "0" is echoed, meaning nothing went wrong. Use "getpos("'>")" again to see
> the position of the mark, this time you'll see:
>
> [0, 25, 2147483647, 0]
>
> The line was changed, but not the column. And it seems to happen
> whenever the column number has that big value, i.e. whenever you went
> into linewise visual mode.
>
> Am I missing something?
You are seeing implementation details, leaking into the Vim API.
You are in *linewise* visual mode, so it doesn't really make sense, to
have the column somewhere different then either 0 or MAXCOLUMN.
Also note, that '< will always be the upper position of these two marks
within the buffer, while '> will always be the lower position of those
two marks. (e.g. you can't set '> to a lower line then '< and you can't
set '< to a larger line number then '>)
Best,
Christian
--
Das muß ein Esel sein, der mit fünfzig Jahren noch dieselben
Anschauungen hat wie vor zwanzig Jahren.
-- Otto von Bismarck
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Sa, 30 Nov 2013, Paul Isambert wrote:
> Hello all,
>
> I've encountered a behavior which really smells like a bug, but I'd
> like to check here beforehand to be sure:
>
> Go into linewise visual mode and leave it. Show the position of the '> mark with:
>
> echo getpos("'>")
>
> It returns something like (if you were on line 23):
>
> [0, 23, 2147483647, 0]
>
> where the very big value for the column means you were in linewise
> visual mode. Now try to set the '> mark with e.g.:
>
> echo setpos("'>", [0, 25, 12, 0])
>
> "0" is echoed, meaning nothing went wrong. Use "getpos("'>")" again to see
> the position of the mark, this time you'll see:
>
> [0, 25, 2147483647, 0]
>
> The line was changed, but not the column. And it seems to happen
> whenever the column number has that big value, i.e. whenever you went
> into linewise visual mode.
>
> Am I missing something?
You are seeing implementation details, leaking into the Vim API.
You are in *linewise* visual mode, so it doesn't really make sense, to
have the column somewhere different then either 0 or MAXCOLUMN.
Also note, that '< will always be the upper position of these two marks
within the buffer, while '> will always be the lower position of those
two marks. (e.g. you can't set '> to a lower line then '< and you can't
set '< to a larger line number then '>)
Best,
Christian
--
Das muß ein Esel sein, der mit fünfzig Jahren noch dieselben
Anschauungen hat wie vor zwanzig Jahren.
-- Otto von Bismarck
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: how to disable (or toggle) csv plugin?
Hi Nikolay!
On So, 01 Dez 2013, Nikolay Pavlov wrote:
> On Dec 1, 2013 12:33 AM, "Christian Brabandt" <cblists@256bit.org> wrote:
> >
> > Hi ping!
> >
> > On Fr, 29 Nov 2013, ping song wrote:
> >
> > > csv plugin is nice, but for some reason when I open a large file it take
> > > forever to load and then freeze. Ctrl-c doesn't help.
> >
> > Actually, Ctrl-C should always abort. I have never seen, when Ctrl-C
> > does not abort a command. Note, that using :ArrangeColumn (either
> > explicitly or implicitly using an autocommand (:h csv-arrange-autocmd))
> > or using dynamic filters can slow down the plugin considerably when used
> > with large files. My advise is, to simply avoid those commands for large
> > csv files.
>
> It will not abort if code is written not in VimL or if somebody is catching
> Vim:Interrupt and resumes computations. Assuming "Ctrl-c doesn't help"
> means "Ctrl-c does not abort" it is most likely the first because sane
> developers do not do the second.
Neither does the csv plugin.
Best,
Christian
--
"Unter allen Völkerschaften haben die Griechen den Traum des
Lebens am schönsten geträumt."
-- Goethe, Maximen und Reflektionen, Nr. 435
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On So, 01 Dez 2013, Nikolay Pavlov wrote:
> On Dec 1, 2013 12:33 AM, "Christian Brabandt" <cblists@256bit.org> wrote:
> >
> > Hi ping!
> >
> > On Fr, 29 Nov 2013, ping song wrote:
> >
> > > csv plugin is nice, but for some reason when I open a large file it take
> > > forever to load and then freeze. Ctrl-c doesn't help.
> >
> > Actually, Ctrl-C should always abort. I have never seen, when Ctrl-C
> > does not abort a command. Note, that using :ArrangeColumn (either
> > explicitly or implicitly using an autocommand (:h csv-arrange-autocmd))
> > or using dynamic filters can slow down the plugin considerably when used
> > with large files. My advise is, to simply avoid those commands for large
> > csv files.
>
> It will not abort if code is written not in VimL or if somebody is catching
> Vim:Interrupt and resumes computations. Assuming "Ctrl-c doesn't help"
> means "Ctrl-c does not abort" it is most likely the first because sane
> developers do not do the second.
Neither does the csv plugin.
Best,
Christian
--
"Unter allen Völkerschaften haben die Griechen den Traum des
Lebens am schönsten geträumt."
-- Goethe, Maximen und Reflektionen, Nr. 435
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: how to disable (or toggle) csv plugin?
On Dec 1, 2013 12:33 AM, "Christian Brabandt" <cblists@256bit.org> wrote:
>
> Hi ping!
>
> On Fr, 29 Nov 2013, ping song wrote:
>
> > csv plugin is nice, but for some reason when I open a large file it take
> > forever to load and then freeze. Ctrl-c doesn't help.
>
> Actually, Ctrl-C should always abort. I have never seen, when Ctrl-C
> does not abort a command. Note, that using :ArrangeColumn (either
> explicitly or implicitly using an autocommand (:h csv-arrange-autocmd))
> or using dynamic filters can slow down the plugin considerably when used
> with large files. My advise is, to simply avoid those commands for large
> csv files.
It will not abort if code is written not in VimL or if somebody is catching Vim:Interrupt and resumes computations. Assuming "Ctrl-c doesn't help" means "Ctrl-c does not abort" it is most likely the first because sane developers do not do the second.
>
> > is there a way to disable it (without uninstall) temporarily?
>
> :set ft=foobar
>
> Best,
> Christian
> --
> Wer niemals außer sich geriete, wird niemals in sich gehen.
> -- Paul von Heyse
>
> --
> --
> You received this message from the "vim_use" 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
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: how to disable (or toggle) csv plugin?
Hi ping!
On Fr, 29 Nov 2013, ping song wrote:
> csv plugin is nice, but for some reason when I open a large file it take
> forever to load and then freeze. Ctrl-c doesn't help.
Actually, Ctrl-C should always abort. I have never seen, when Ctrl-C
does not abort a command. Note, that using :ArrangeColumn (either
explicitly or implicitly using an autocommand (:h csv-arrange-autocmd))
or using dynamic filters can slow down the plugin considerably when used
with large files. My advise is, to simply avoid those commands for large
csv files.
> is there a way to disable it (without uninstall) temporarily?
:set ft=foobar
Best,
Christian
--
Wer niemals außer sich geriete, wird niemals in sich gehen.
-- Paul von Heyse
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Fr, 29 Nov 2013, ping song wrote:
> csv plugin is nice, but for some reason when I open a large file it take
> forever to load and then freeze. Ctrl-c doesn't help.
Actually, Ctrl-C should always abort. I have never seen, when Ctrl-C
does not abort a command. Note, that using :ArrangeColumn (either
explicitly or implicitly using an autocommand (:h csv-arrange-autocmd))
or using dynamic filters can slow down the plugin considerably when used
with large files. My advise is, to simply avoid those commands for large
csv files.
> is there a way to disable it (without uninstall) temporarily?
:set ft=foobar
Best,
Christian
--
Wer niemals außer sich geriete, wird niemals in sich gehen.
-- Paul von Heyse
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: how to make vim read local configuration files
Hi Mauro!
On Sa, 30 Nov 2013, Mauro Sacchetto wrote:
> i put some local configuration files for latex-suite
> in ~/.vim/ftplugin/latex-suite. but it continues
> to read the system configuration files placed in
> /usr/share/vim/addons/ftplugin/latex-suite/ and in
> /var/lib/vim/addons/ftplugin/latex-suite.
> how can i suggest vim to read my local files?
There is no filetype latex-suite.
I suggest putting your file into ~/.vim/ftplugin/tex/ directory.
(assuming, you want the file loaded for TeX files and you have filetype
plugin on set in your .vimrc)
Best,
Christian
--
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Sa, 30 Nov 2013, Mauro Sacchetto wrote:
> i put some local configuration files for latex-suite
> in ~/.vim/ftplugin/latex-suite. but it continues
> to read the system configuration files placed in
> /usr/share/vim/addons/ftplugin/latex-suite/ and in
> /var/lib/vim/addons/ftplugin/latex-suite.
> how can i suggest vim to read my local files?
There is no filetype latex-suite.
I suggest putting your file into ~/.vim/ftplugin/tex/ directory.
(assuming, you want the file loaded for TeX files and you have filetype
plugin on set in your .vimrc)
Best,
Christian
--
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Location list autocommand
On Saturday, November 30, 2013 6:51:45 AM UTC-6, Thiago de Arruda wrote:
> Could you give an example? My requirement is very simple: I want to
>
> bind the letter 'q' to ':lclose<cr>' for location-list and to
>
> ':cclose<cr>' do I can use 'q' to quickly close quickfix or
>
> location-list(both have filetype qf). As I said I managed to do it for
>
> quickfix, not for location-list
>
>
Example:
autocmd BufWinEnter * if &ft=="qf" | echomsg "I'm in quickfix!" | endif
This seems to work for me. Replace echomsg with your desired mapping. Make sure you make the mapping buffer-local.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Could you give an example? My requirement is very simple: I want to
>
> bind the letter 'q' to ':lclose<cr>' for location-list and to
>
> ':cclose<cr>' do I can use 'q' to quickly close quickfix or
>
> location-list(both have filetype qf). As I said I managed to do it for
>
> quickfix, not for location-list
>
>
Example:
autocmd BufWinEnter * if &ft=="qf" | echomsg "I'm in quickfix!" | endif
This seems to work for me. Replace echomsg with your desired mapping. Make sure you make the mapping buffer-local.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: how to make vim read local configuration files
On Nov 30, 2013 10:06 PM, "Mauro Sacchetto" <mauro.sacchetto@gmail.com> wrote:
>
> i put some local configuration files for latex-suite
> in ~/.vim/ftplugin/latex-suite. but it continues
> to read the system configuration files placed in
> /usr/share/vim/addons/ftplugin/latex-suite/ and in
> /var/lib/vim/addons/ftplugin/latex-suite.
> how can i suggest vim to read my local files?
These are not *configuration* files. These are source code files.
You should use ftplugin/tex directory or ftplugin/tex.vim file to make your settings loaded when you open tex file and vimrc or plugin/ directory to make them applied always.
>
> thanx
> ms
>
>
> --
> Linux user no.: 353546
> public key at http://keyserver.linux.it
>
> --
> --
> You received this message from the "vim_use" 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
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: how to make vim read local configuration files
On Nov 30, 2013 10:15 PM, "Marc Weber" <marco-oweber@gmx.de> wrote:
>
> Excerpts from Mauro Sacchetto's message of Sat Nov 30 19:06:28 +0100 2013:
> > to read the system configuration files placed in
> > /usr/share/vim/addons/ftplugin/latex-suite/ and in
> > /var/lib/vim/addons/ftplugin/latex-suite.
> > how can i suggest vim to read my local files?
> Well - its bad habit to install plugins "system wide" for that reason
> eventually.
Unless you are going to modify files it makes no difference. It *may* be bad (really not bad, but annoying) habit to install plugins in multiple ways, but I see nothing bad in using only one variant.
>
> Many ftplugin files have a b:did_ftplugin setting, you should set it in
> your custom file to prevent the system wide to take any action.
There is no latex-suite filetype: besides the location these files are *not* filetype plugins.
>
> Typical guards look like this:
>
> if exists('b:did_ftplugin')
> finish
> endif
> let b:did_ftplugin = 1
>
> Another way is to "override" settings by using ~/.vim/after/ftplugin/*
> which should be loaded last.
This is not going to work: latex-suite authors do not use FileType event to load plugins thus ftplugin/latex-suite may be just as well named macros/latex-suite since it is loaded by :source or :runtime (the fact that OP files were not loaded suggests they are either named not like files in ftplugin/latex-suite or :source is used).
>
> Marc Weber
>
> --
> --
> You received this message from the "vim_use" 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
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: how to make vim read local configuration files
Excerpts from Mauro Sacchetto's message of Sat Nov 30 19:06:28 +0100 2013:
> to read the system configuration files placed in
> /usr/share/vim/addons/ftplugin/latex-suite/ and in
> /var/lib/vim/addons/ftplugin/latex-suite.
> how can i suggest vim to read my local files?
Well - its bad habit to install plugins "system wide" for that reason
eventually.
Many ftplugin files have a b:did_ftplugin setting, you should set it in
your custom file to prevent the system wide to take any action.
Typical guards look like this:
if exists('b:did_ftplugin')
finish
endif
let b:did_ftplugin = 1
Another way is to "override" settings by using ~/.vim/after/ftplugin/*
which should be loaded last.
Marc Weber
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> to read the system configuration files placed in
> /usr/share/vim/addons/ftplugin/latex-suite/ and in
> /var/lib/vim/addons/ftplugin/latex-suite.
> how can i suggest vim to read my local files?
Well - its bad habit to install plugins "system wide" for that reason
eventually.
Many ftplugin files have a b:did_ftplugin setting, you should set it in
your custom file to prevent the system wide to take any action.
Typical guards look like this:
if exists('b:did_ftplugin')
finish
endif
let b:did_ftplugin = 1
Another way is to "override" settings by using ~/.vim/after/ftplugin/*
which should be loaded last.
Marc Weber
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
how to make vim read local configuration files
i put some local configuration files for latex-suite
in ~/.vim/ftplugin/latex-suite. but it continues
to read the system configuration files placed in
/usr/share/vim/addons/ftplugin/latex-suite/ and in
/var/lib/vim/addons/ftplugin/latex-suite.
how can i suggest vim to read my local files?
thanx
ms
--
Linux user no.: 353546
public key at http://keyserver.linux.it
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
in ~/.vim/ftplugin/latex-suite. but it continues
to read the system configuration files placed in
/usr/share/vim/addons/ftplugin/latex-suite/ and in
/var/lib/vim/addons/ftplugin/latex-suite.
how can i suggest vim to read my local files?
thanx
ms
--
Linux user no.: 353546
public key at http://keyserver.linux.it
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Location list autocommand
Could you give an example? My requirement is very simple: I want to
bind the letter 'q' to ':lclose<cr>' for location-list and to
':cclose<cr>' do I can use 'q' to quickly close quickfix or
location-list(both have filetype qf). As I said I managed to do it for
quickfix, not for location-list
On Fri, Nov 29, 2013 at 5:55 PM, Ben Fritz <fritzophrenic@gmail.com> wrote:
> On Friday, November 29, 2013 9:59:42 AM UTC-6, Thiago de Arruda wrote:
>> Hi
>>
>>
>>
>> I have some mappings done for quickfix window like this:
>>
>>
>>
>> au! BufWinEnter quickfix nnoremap....
>>
>>
>>
>> How can I do the same for the location list window?
>
> I normally just use a WinEnter and check that the filetype is qf and then set some window-local variable so I can avoid doing it again.
>
> --
> --
> You received this message from the "vim_use" 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
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
bind the letter 'q' to ':lclose<cr>' for location-list and to
':cclose<cr>' do I can use 'q' to quickly close quickfix or
location-list(both have filetype qf). As I said I managed to do it for
quickfix, not for location-list
On Fri, Nov 29, 2013 at 5:55 PM, Ben Fritz <fritzophrenic@gmail.com> wrote:
> On Friday, November 29, 2013 9:59:42 AM UTC-6, Thiago de Arruda wrote:
>> Hi
>>
>>
>>
>> I have some mappings done for quickfix window like this:
>>
>>
>>
>> au! BufWinEnter quickfix nnoremap....
>>
>>
>>
>> How can I do the same for the location list window?
>
> I normally just use a WinEnter and check that the filetype is qf and then set some window-local variable so I can avoid doing it again.
>
> --
> --
> You received this message from the "vim_use" 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
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Trouble with getpos()/setpos().
On Saturday, November 30, 2013 11:40:12 AM UTC+1, Paul Isambert wrote:
> glts <676c7473@gmail.com> a écrit:
> > Paul,
> >
> > On Saturday, November 30, 2013 10:03:07 AM UTC+1, Paul Isambert wrote:
> > > I've encountered a behavior which really smells like a bug, but I'd
> > > like to check here beforehand to be sure:
> > >
> > > Go into linewise visual mode and leave it. Show the position of the '> mark with:
> > >
> > > echo getpos("'>")
> > >
> > > It returns something like (if you were on line 23):
> > >
> > > [0, 23, 2147483647, 0]
> > >
> > > where the very big value for the column means you were in linewise
> > > visual mode. Now try to set the '> mark with e.g.:
> > >
> > > echo setpos("'>", [0, 25, 12, 0])
> > >
> > > "0" is echoed, meaning nothing went wrong. Use "getpos("'>")" again to see
> > > the position of the mark, this time you'll see:
> > >
> > > [0, 25, 2147483647, 0]
> > >
> > > The line was changed, but not the column. And it seems to happen
> > > whenever the column number has that big value, i.e. whenever you went
> > > into linewise visual mode.
> > >
> > > Am I missing something?
> >
> > I tripped over this myself in the past and posted it here as a bug.
> >
> > But it's documented behaviour. :h setpos(), the last paragraph:
> >
> > > This does not restore the preferred column for moving vertically. See
> > > |winrestview()| for that.
>
> Thank you David. I'd seen that part without really reading it nor
> understanding what it means. In particular, how does it explain that
> "setpos()" doesn't set the column if and only if the current column is
> "infinite", whereas it works ok otherwise?
>
> To put it another way, if "setpos()" is half useless, why does it
> exit to begin with?
I answered too quickly, sorry. Now that I reread your description it
does seem strange, I can't explain it.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> glts <676c7473@gmail.com> a écrit:
> > Paul,
> >
> > On Saturday, November 30, 2013 10:03:07 AM UTC+1, Paul Isambert wrote:
> > > I've encountered a behavior which really smells like a bug, but I'd
> > > like to check here beforehand to be sure:
> > >
> > > Go into linewise visual mode and leave it. Show the position of the '> mark with:
> > >
> > > echo getpos("'>")
> > >
> > > It returns something like (if you were on line 23):
> > >
> > > [0, 23, 2147483647, 0]
> > >
> > > where the very big value for the column means you were in linewise
> > > visual mode. Now try to set the '> mark with e.g.:
> > >
> > > echo setpos("'>", [0, 25, 12, 0])
> > >
> > > "0" is echoed, meaning nothing went wrong. Use "getpos("'>")" again to see
> > > the position of the mark, this time you'll see:
> > >
> > > [0, 25, 2147483647, 0]
> > >
> > > The line was changed, but not the column. And it seems to happen
> > > whenever the column number has that big value, i.e. whenever you went
> > > into linewise visual mode.
> > >
> > > Am I missing something?
> >
> > I tripped over this myself in the past and posted it here as a bug.
> >
> > But it's documented behaviour. :h setpos(), the last paragraph:
> >
> > > This does not restore the preferred column for moving vertically. See
> > > |winrestview()| for that.
>
> Thank you David. I'd seen that part without really reading it nor
> understanding what it means. In particular, how does it explain that
> "setpos()" doesn't set the column if and only if the current column is
> "infinite", whereas it works ok otherwise?
>
> To put it another way, if "setpos()" is half useless, why does it
> exit to begin with?
I answered too quickly, sorry. Now that I reread your description it
does seem strange, I can't explain it.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Trouble with getpos()/setpos().
glts <676c7473@gmail.com> a écrit:
> Paul,
>
> On Saturday, November 30, 2013 10:03:07 AM UTC+1, Paul Isambert wrote:
> > I've encountered a behavior which really smells like a bug, but I'd
> > like to check here beforehand to be sure:
> >
> > Go into linewise visual mode and leave it. Show the position of the '> mark with:
> >
> > echo getpos("'>")
> >
> > It returns something like (if you were on line 23):
> >
> > [0, 23, 2147483647, 0]
> >
> > where the very big value for the column means you were in linewise
> > visual mode. Now try to set the '> mark with e.g.:
> >
> > echo setpos("'>", [0, 25, 12, 0])
> >
> > "0" is echoed, meaning nothing went wrong. Use "getpos("'>")" again to see
> > the position of the mark, this time you'll see:
> >
> > [0, 25, 2147483647, 0]
> >
> > The line was changed, but not the column. And it seems to happen
> > whenever the column number has that big value, i.e. whenever you went
> > into linewise visual mode.
> >
> > Am I missing something?
>
> I tripped over this myself in the past and posted it here as a bug.
>
> But it's documented behaviour. :h setpos(), the last paragraph:
>
> > This does not restore the preferred column for moving vertically. See
> > |winrestview()| for that.
Thank you David. I'd seen that part without really reading it nor
understanding what it means. In particular, how does it explain that
"setpos()" doesn't set the column if and only if the current column is
"infinite", whereas it works ok otherwise?
To put it another way, if "setpos()" is half useless, why does it
exit to begin with?
Best,
Paul
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Paul,
>
> On Saturday, November 30, 2013 10:03:07 AM UTC+1, Paul Isambert wrote:
> > I've encountered a behavior which really smells like a bug, but I'd
> > like to check here beforehand to be sure:
> >
> > Go into linewise visual mode and leave it. Show the position of the '> mark with:
> >
> > echo getpos("'>")
> >
> > It returns something like (if you were on line 23):
> >
> > [0, 23, 2147483647, 0]
> >
> > where the very big value for the column means you were in linewise
> > visual mode. Now try to set the '> mark with e.g.:
> >
> > echo setpos("'>", [0, 25, 12, 0])
> >
> > "0" is echoed, meaning nothing went wrong. Use "getpos("'>")" again to see
> > the position of the mark, this time you'll see:
> >
> > [0, 25, 2147483647, 0]
> >
> > The line was changed, but not the column. And it seems to happen
> > whenever the column number has that big value, i.e. whenever you went
> > into linewise visual mode.
> >
> > Am I missing something?
>
> I tripped over this myself in the past and posted it here as a bug.
>
> But it's documented behaviour. :h setpos(), the last paragraph:
>
> > This does not restore the preferred column for moving vertically. See
> > |winrestview()| for that.
Thank you David. I'd seen that part without really reading it nor
understanding what it means. In particular, how does it explain that
"setpos()" doesn't set the column if and only if the current column is
"infinite", whereas it works ok otherwise?
To put it another way, if "setpos()" is half useless, why does it
exit to begin with?
Best,
Paul
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Trouble with getpos()/setpos().
Paul,
On Saturday, November 30, 2013 10:03:07 AM UTC+1, Paul Isambert wrote:
> I've encountered a behavior which really smells like a bug, but I'd
> like to check here beforehand to be sure:
>
> Go into linewise visual mode and leave it. Show the position of the '> mark with:
>
> echo getpos("'>")
>
> It returns something like (if you were on line 23):
>
> [0, 23, 2147483647, 0]
>
> where the very big value for the column means you were in linewise
> visual mode. Now try to set the '> mark with e.g.:
>
> echo setpos("'>", [0, 25, 12, 0])
>
> "0" is echoed, meaning nothing went wrong. Use "getpos("'>")" again to see
> the position of the mark, this time you'll see:
>
> [0, 25, 2147483647, 0]
>
> The line was changed, but not the column. And it seems to happen
> whenever the column number has that big value, i.e. whenever you went
> into linewise visual mode.
>
> Am I missing something?
I tripped over this myself in the past and posted it here as a bug.
But it's documented behaviour. :h setpos(), the last paragraph:
> This does not restore the preferred column for moving vertically. See
> |winrestview()| for that.
Best,
--
David
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Saturday, November 30, 2013 10:03:07 AM UTC+1, Paul Isambert wrote:
> I've encountered a behavior which really smells like a bug, but I'd
> like to check here beforehand to be sure:
>
> Go into linewise visual mode and leave it. Show the position of the '> mark with:
>
> echo getpos("'>")
>
> It returns something like (if you were on line 23):
>
> [0, 23, 2147483647, 0]
>
> where the very big value for the column means you were in linewise
> visual mode. Now try to set the '> mark with e.g.:
>
> echo setpos("'>", [0, 25, 12, 0])
>
> "0" is echoed, meaning nothing went wrong. Use "getpos("'>")" again to see
> the position of the mark, this time you'll see:
>
> [0, 25, 2147483647, 0]
>
> The line was changed, but not the column. And it seems to happen
> whenever the column number has that big value, i.e. whenever you went
> into linewise visual mode.
>
> Am I missing something?
I tripped over this myself in the past and posted it here as a bug.
But it's documented behaviour. :h setpos(), the last paragraph:
> This does not restore the preferred column for moving vertically. See
> |winrestview()| for that.
Best,
--
David
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Trouble with getpos()/setpos().
Hello all,
I've encountered a behavior which really smells like a bug, but I'd
like to check here beforehand to be sure:
Go into linewise visual mode and leave it. Show the position of the '> mark with:
echo getpos("'>")
It returns something like (if you were on line 23):
[0, 23, 2147483647, 0]
where the very big value for the column means you were in linewise
visual mode. Now try to set the '> mark with e.g.:
echo setpos("'>", [0, 25, 12, 0])
"0" is echoed, meaning nothing went wrong. Use "getpos("'>")" again to see
the position of the mark, this time you'll see:
[0, 25, 2147483647, 0]
The line was changed, but not the column. And it seems to happen
whenever the column number has that big value, i.e. whenever you went
into linewise visual mode.
Am I missing something?
Best,
Paul
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I've encountered a behavior which really smells like a bug, but I'd
like to check here beforehand to be sure:
Go into linewise visual mode and leave it. Show the position of the '> mark with:
echo getpos("'>")
It returns something like (if you were on line 23):
[0, 23, 2147483647, 0]
where the very big value for the column means you were in linewise
visual mode. Now try to set the '> mark with e.g.:
echo setpos("'>", [0, 25, 12, 0])
"0" is echoed, meaning nothing went wrong. Use "getpos("'>")" again to see
the position of the mark, this time you'll see:
[0, 25, 2147483647, 0]
The line was changed, but not the column. And it seems to happen
whenever the column number has that big value, i.e. whenever you went
into linewise visual mode.
Am I missing something?
Best,
Paul
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Friday, November 29, 2013
Re: vim slow, Lisp, etc.
Excerpts from Ed Kostas's message of Fri Nov 29 12:29:33 +0100 2013:
> Let us examine the specific questions, as suggested by mfid. To make a
> long story short, I may recommend my friends to stick to emacs/evil,
[..] that's what we were silently suggesting because you depend on so
many Emacs specific features.
> flymake
Traditional:
:set makeprg=gcc
:make
:cope
:cnext :cfirst :cprevious :colder
Alternatives:
There are tons of plugins at vim.org, I wrote vim-addon-actions which
lets you bind actions (1st set error format 2snd run compiler) to keys
or bufwrite events.
Some presets can be found in :e $VIMRUNTIME/compilers/* or such.
You use them by :compiler gcc
Howver its not modular enough which is why eg I started
github.com/MarcWeber/vim-addon-errorformats so that I can mix multiple
error format descriptions (eg ruby build system building ocaml, so I
need to recognize ruby and ocaml error messages).
Marc Weber
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Let us examine the specific questions, as suggested by mfid. To make a
> long story short, I may recommend my friends to stick to emacs/evil,
[..] that's what we were silently suggesting because you depend on so
many Emacs specific features.
> flymake
Traditional:
:set makeprg=gcc
:make
:cope
:cnext :cfirst :cprevious :colder
Alternatives:
There are tons of plugins at vim.org, I wrote vim-addon-actions which
lets you bind actions (1st set error format 2snd run compiler) to keys
or bufwrite events.
Some presets can be found in :e $VIMRUNTIME/compilers/* or such.
You use them by :compiler gcc
Howver its not modular enough which is why eg I started
github.com/MarcWeber/vim-addon-errorformats so that I can mix multiple
error format descriptions (eg ruby build system building ocaml, so I
need to recognize ruby and ocaml error messages).
Marc Weber
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
how to disable (or toggle) csv plugin?
csv plugin is nice, but for some reason when I open a large file it take forever to load and then freeze. Ctrl-c doesn't help.
-- is there a way to disable it (without uninstall) temporarily?
thanks!
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Location list autocommand
On Friday, November 29, 2013 9:59:42 AM UTC-6, Thiago de Arruda wrote:
> Hi
>
>
>
> I have some mappings done for quickfix window like this:
>
>
>
> au! BufWinEnter quickfix nnoremap....
>
>
>
> How can I do the same for the location list window?
I normally just use a WinEnter and check that the filetype is qf and then set some window-local variable so I can avoid doing it again.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Hi
>
>
>
> I have some mappings done for quickfix window like this:
>
>
>
> au! BufWinEnter quickfix nnoremap....
>
>
>
> How can I do the same for the location list window?
I normally just use a WinEnter and check that the filetype is qf and then set some window-local variable so I can avoid doing it again.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: yet another vim documentation, in French
Hi Shlomi,
Many thanks for this quick answer and good suggestions.
> Thanks for preparing it and making it available! I will probably link to it
>
> from http://vim.begin-site.org/ and would like to enquire - what is its licence?
>
> Would you like to put it under one of the Creative Commons licences or a similar
>
> licence? See https://creativecommons.org/choose/ . You may also wish to
>
> announce your work on http://www.reddit.com/r/vim .
I just added a creative commons licence in the web page ! (Document freely usable but no commercial use.) As for reddit publicity I will consider it later.
> Finally, I should note that in English "documentation" is an uncountable noun
>
> (see http://en.wiktionary.org/wiki/documentation ). You can use "document" if
>
> you refer to a single document.
Thanks for this remark. I didn't write the document in English in the first place because of such errors I know I am making all time... Even if I think documents probably keep on to be readable.
Regards,
Alain
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Many thanks for this quick answer and good suggestions.
> Thanks for preparing it and making it available! I will probably link to it
>
> from http://vim.begin-site.org/ and would like to enquire - what is its licence?
>
> Would you like to put it under one of the Creative Commons licences or a similar
>
> licence? See https://creativecommons.org/choose/ . You may also wish to
>
> announce your work on http://www.reddit.com/r/vim .
I just added a creative commons licence in the web page ! (Document freely usable but no commercial use.) As for reddit publicity I will consider it later.
> Finally, I should note that in English "documentation" is an uncountable noun
>
> (see http://en.wiktionary.org/wiki/documentation ). You can use "document" if
>
> you refer to a single document.
Thanks for this remark. I didn't write the document in English in the first place because of such errors I know I am making all time... Even if I think documents probably keep on to be readable.
Regards,
Alain
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: vim slow, Lisp, etc.
Well, I tested the suggestion of adding --enable-pythoninterp to the command line, and compiling racket from sources. Now, everything is working beautifully. Thanks to everybody for helping me. I appreciated specially Marc Weber page, that contains many insightful observations about Vim. I am not sure whether I can help with coding, but I certainly will help with testing.
I believe that C. Campbell analyzed the problem of speeding up latex syntax highlighting, since his suggestions were quite useful. Besides this, I searched this group, and found another of his interesting posts (Slow Syntax Highlighting with Latex), where he offers a few additional suggestions.
Mzscheme (Racket) is really fast. I used the search engine that my friends use to build outlines of their pleadings, and noticed that Mzscheme is at least ten times faster than elisp.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I believe that C. Campbell analyzed the problem of speeding up latex syntax highlighting, since his suggestions were quite useful. Besides this, I searched this group, and found another of his interesting posts (Slow Syntax Highlighting with Latex), where he offers a few additional suggestions.
Mzscheme (Racket) is really fast. I used the search engine that my friends use to build outlines of their pleadings, and noticed that Mzscheme is at least ten times faster than elisp.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: yet another vim documentation, in French
Hi Alain,
On Fri, 29 Nov 2013 09:39:09 -0800 (PST)
alain braun <notesvimab@gmail.com> wrote:
> Hi everybody,
> Bonjour à tous,
>
> *English text*
>
> Yet another documentation on vim, in French, made by a standard vim user, but
> still vim lover. This is kind of an informal rather big document trying to
> give a vim large overview to vim users, except true beginners.
>
> This documentation is first aimed at my former colleagues at Météo-France
> (French Weather Service), but may also be used more broadly.
>
> A presentation and the documentation itself may be found on my personal site
> http://a.braun31.free.fr (in French).
>
Thanks for preparing it and making it available! I will probably link to it
from http://vim.begin-site.org/ and would like to enquire - what is its licence?
Would you like to put it under one of the Creative Commons licences or a similar
licence? See https://creativecommons.org/choose/ . You may also wish to
announce your work on http://www.reddit.com/r/vim .
Finally, I should note that in English "documentation" is an uncountable noun
(see http://en.wiktionary.org/wiki/documentation ). You can use "document" if
you refer to a single document.
Regards,
Shlomi Fish
--
-----------------------------------------------------------------
Shlomi Fish http://www.shlomifish.org/
Optimising Code for Speed - http://shlom.in/optimise
If his programming is anything like his philosophising, he would find ten
imaginary bugs in the "Hello World" program.
Please reply to list if it's a mailing list post - http://shlom.in/reply .
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Fri, 29 Nov 2013 09:39:09 -0800 (PST)
alain braun <notesvimab@gmail.com> wrote:
> Hi everybody,
> Bonjour à tous,
>
> *English text*
>
> Yet another documentation on vim, in French, made by a standard vim user, but
> still vim lover. This is kind of an informal rather big document trying to
> give a vim large overview to vim users, except true beginners.
>
> This documentation is first aimed at my former colleagues at Météo-France
> (French Weather Service), but may also be used more broadly.
>
> A presentation and the documentation itself may be found on my personal site
> http://a.braun31.free.fr (in French).
>
Thanks for preparing it and making it available! I will probably link to it
from http://vim.begin-site.org/ and would like to enquire - what is its licence?
Would you like to put it under one of the Creative Commons licences or a similar
licence? See https://creativecommons.org/choose/ . You may also wish to
announce your work on http://www.reddit.com/r/vim .
Finally, I should note that in English "documentation" is an uncountable noun
(see http://en.wiktionary.org/wiki/documentation ). You can use "document" if
you refer to a single document.
Regards,
Shlomi Fish
--
-----------------------------------------------------------------
Shlomi Fish http://www.shlomifish.org/
Optimising Code for Speed - http://shlom.in/optimise
If his programming is anything like his philosophising, he would find ten
imaginary bugs in the "Hello World" program.
Please reply to list if it's a mailing list post - http://shlom.in/reply .
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
yet another vim documentation, in French
Hi everybody,
Bonjour à tous,
*English text*
Yet another documentation on vim, in French, made by a standard vim user, but still vim lover. This is kind of an informal rather big document trying to give a vim large overview to vim users, except true beginners.
This documentation is first aimed at my former colleagues at Météo-France (French Weather Service), but may also be used more broadly.
A presentation and the documentation itself may be found on my personal site http://a.braun31.free.fr (in French).
*French text*
Une nouvelle documentation vim vous est proposée ici, en français, écrite par mes soins, simple utilisateur, fan de vim. Il s'agit d'un document pdf de 136 pages, donnant une vue d'ensemble d'un grand nombre de caractéristiques vim, de manière plutôt informelle. Les lecteurs visés sont ceux ayant déjà une pratique de base de vim et voulant améliorer leurs connaissances.
Le titre du document est
"Une vue d'ensemble de l'éditeur de texte Vim"
"Notes Vim AB".
La documentation est au départ destinée à mes anciens collègues de Météo-France, mais tous les utilisateurs vim francophones pourraient y voir un intérêt.
Une présentation et la documentation elle-même sont disponibles sur mon site personnel http://a.braun31.free.fr.
Votre avis m'intéresse. Une analyse critique du document par un ou des experts vim serait très appréciée !
Bonne vimification,
Alain Braun
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Bonjour à tous,
*English text*
Yet another documentation on vim, in French, made by a standard vim user, but still vim lover. This is kind of an informal rather big document trying to give a vim large overview to vim users, except true beginners.
This documentation is first aimed at my former colleagues at Météo-France (French Weather Service), but may also be used more broadly.
A presentation and the documentation itself may be found on my personal site http://a.braun31.free.fr (in French).
*French text*
Une nouvelle documentation vim vous est proposée ici, en français, écrite par mes soins, simple utilisateur, fan de vim. Il s'agit d'un document pdf de 136 pages, donnant une vue d'ensemble d'un grand nombre de caractéristiques vim, de manière plutôt informelle. Les lecteurs visés sont ceux ayant déjà une pratique de base de vim et voulant améliorer leurs connaissances.
Le titre du document est
"Une vue d'ensemble de l'éditeur de texte Vim"
"Notes Vim AB".
La documentation est au départ destinée à mes anciens collègues de Météo-France, mais tous les utilisateurs vim francophones pourraient y voir un intérêt.
Une présentation et la documentation elle-même sont disponibles sur mon site personnel http://a.braun31.free.fr.
Votre avis m'intéresse. Une analyse critique du document par un ou des experts vim serait très appréciée !
Bonne vimification,
Alain Braun
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Location list autocommand
Hi
I have some mappings done for quickfix window like this:
au! BufWinEnter quickfix nnoremap....
How can I do the same for the location list window?
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I have some mappings done for quickfix window like this:
au! BufWinEnter quickfix nnoremap....
How can I do the same for the location list window?
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: vim slow, Lisp, etc.
On Nov 29, 2013 6:54 PM, "Ed Kostas" <edu500ac@gmail.com> wrote:
>
> One of the lawyers and an engineer interested in Vim told me that they succeeded in compiling Vim, with mzscheme and with somewhat faster syntax coloring. I did not test their instruction myself, but both said that they did the following:
>
> 1 - Add python. They even don't know what python is, but they read somewhere that python requires threads. They don't know what threads are either, but they know that Emacs has threads; therefore, threads are the thing that is missing.
>
> 2 - Install Racket from sources. Then copy the libraries libracket.a and libmzgc.a to /usr/local/lib
>
> The command line becomes:
>
> ./configure --enable-mzschemeinterp --enable-pythoninterp
>
> They claim that this did the trick. I will try it later on. They also followed the suggestion of DrChip for improving the speed. It seems that it works.
>
> I know that people here are users, not the core developers of Vim. However, I believe that Vim (and Racket) should simplify the installation process. This would prevent people like me from nagging the members of this list with details of installation. Here is a few suggestions (again, I know that this list is not the place for it):
>
> 1 -- Racket should put the libraries in the binary distribution. Most people don't compile from sources.
It is the job that maintainers of the package in given distribution should do. You cannot possibly target all linux distributions, there are way too many.
> 2 -- Vim should point out that the libraries are necessary, and that they are not distributed normally from the site of Racket.
> 3 -- Vim should explain that threads are necessary, and explain how to add threads. For example, by installing python. Even better, if_mzscheme should intall threads automatically.
There cannot possibly be such requirement as "threads". Thread is a part of the running process, it does not exist until vim is run and python does not create any threads without request. Using python interpreter does not require using more then one thread (there is no way you can use less then one thread in a running process and having exactly one implies referring to the application as not threaded).
There may be some library required (like -lpthread) that is brought by depending on python, but "installing thread(s)" makes just as no sense as "installing session". You should post build logs (at least in failing case) here to verify that it is library that is missing (it may just as well be missing #ifdef) and that it is libpthread.
Neither python nor mzscheme (racket) distribute libpthread. It is a matter of missing argument to a linker: you may have this library be installed to every directory in your filesystem and yet it will be "missing" if linker was not supplied with -lpthread argument.
Linking library in libracket.a is enough unless if_mzscheme contains explicit calls to functions from libpthread. Racket library should have already been linked properly though or it will not run at all.
>
>
>
> --
> --
> You received this message from the "vim_use" 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
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: vim slow, Lisp, etc.
One of the lawyers and an engineer interested in Vim told me that they succeeded in compiling Vim, with mzscheme and with somewhat faster syntax coloring. I did not test their instruction myself, but both said that they did the following:
1 - Add python. They even don't know what python is, but they read somewhere that python requires threads. They don't know what threads are either, but they know that Emacs has threads; therefore, threads are the thing that is missing.
2 - Install Racket from sources. Then copy the libraries libracket.a and libmzgc.a to /usr/local/lib
The command line becomes:
./configure --enable-mzschemeinterp --enable-pythoninterp
They claim that this did the trick. I will try it later on. They also followed the suggestion of DrChip for improving the speed. It seems that it works.
I know that people here are users, not the core developers of Vim. However, I believe that Vim (and Racket) should simplify the installation process. This would prevent people like me from nagging the members of this list with details of installation. Here is a few suggestions (again, I know that this list is not the place for it):
1 -- Racket should put the libraries in the binary distribution. Most people don't compile from sources.
2 -- Vim should point out that the libraries are necessary, and that they are not distributed normally from the site of Racket.
3 -- Vim should explain that threads are necessary, and explain how to add threads. For example, by installing python. Even better, if_mzscheme should intall threads automatically.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
1 - Add python. They even don't know what python is, but they read somewhere that python requires threads. They don't know what threads are either, but they know that Emacs has threads; therefore, threads are the thing that is missing.
2 - Install Racket from sources. Then copy the libraries libracket.a and libmzgc.a to /usr/local/lib
The command line becomes:
./configure --enable-mzschemeinterp --enable-pythoninterp
They claim that this did the trick. I will try it later on. They also followed the suggestion of DrChip for improving the speed. It seems that it works.
I know that people here are users, not the core developers of Vim. However, I believe that Vim (and Racket) should simplify the installation process. This would prevent people like me from nagging the members of this list with details of installation. Here is a few suggestions (again, I know that this list is not the place for it):
1 -- Racket should put the libraries in the binary distribution. Most people don't compile from sources.
2 -- Vim should point out that the libraries are necessary, and that they are not distributed normally from the site of Racket.
3 -- Vim should explain that threads are necessary, and explain how to add threads. For example, by installing python. Even better, if_mzscheme should intall threads automatically.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: vim slow, Lisp, etc.
Let us examine the specific questions, as suggested by mfid. To make a long story short, I may recommend my friends to stick to emacs/evil, but they must first try vim. However, I need to compile Vim with mzscheme (or any other lisp) so they can keep using specific programs. Since I do not know C, I need your help. Emacs has a program, called flymake.el that shows where are the errors in a C program. I guess that Vim has flymake too, but since I was not able to compile Vim, I used flymake from Emacs. All this was suggested by Juan Francisco Cantero Hurtado. I hope you can help me to fix the problems. Here are the errors from Vim make:
if_mzsch.c: In function 'window_new':
if_mzsch.c:1782:5: error: lvalue required as left operand of assignment
if_mzsch.c: In function 'buffer_new':
if_mzsch.c:2136:5: error: lvalue required as left operand of assignment
make[1]: ** [objects/if_mzsch.o] Erro 1
make[1]: Saindo do diretório `/home/rosa/edt/vim/src'
make: ** [first] Erro 2
When I opene if_mzsch.c, flymake shows the following lines in red:
MZ_GC_CHECK();
BUFFER_REF(buf) = self; <-- This line is red
MZ_GC_CHECK();
self->buf = buf;
self->so.type = mz_buffer_type;
static Scheme_Object *
window_new(win_T *win)
{... etc.
MZ_GC_CHECK();
WINDOW_REF(win) = self; <-- This line is red
MZ_GC_CHECK();
self->win = win;
self->so.type = mz_window_type;
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
if_mzsch.c: In function 'window_new':
if_mzsch.c:1782:5: error: lvalue required as left operand of assignment
if_mzsch.c: In function 'buffer_new':
if_mzsch.c:2136:5: error: lvalue required as left operand of assignment
make[1]: ** [objects/if_mzsch.o] Erro 1
make[1]: Saindo do diretório `/home/rosa/edt/vim/src'
make: ** [first] Erro 2
When I opene if_mzsch.c, flymake shows the following lines in red:
MZ_GC_CHECK();
BUFFER_REF(buf) = self; <-- This line is red
MZ_GC_CHECK();
self->buf = buf;
self->so.type = mz_buffer_type;
static Scheme_Object *
window_new(win_T *win)
{... etc.
MZ_GC_CHECK();
WINDOW_REF(win) = self; <-- This line is red
MZ_GC_CHECK();
self->win = win;
self->so.type = mz_window_type;
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Search and stay
> Based on this very real annoyance, and having a little bit of time to kill, I
> wrote the code below: not only does it removes the 'hlsearch' problem, but it
> also makes search easier by foregrounding matches and letting you jump from
> one to the next without leaving the search. I find it quite comfortable, but
> of course others might find that just terrible. Here's how it works:
I really like this – thanks!
> If anybody is interested, I can make that into a plugin (rewriting it a little
> bit less sloppily, because it will fail in some cases, plus it requires a few
> options to be really interesting), in case, of course, such a plugin does not
> already exist :)
That would be great, if you have the time. I'd prefer to drop in a plugin that enlarge my vimrc.
Yours,
Andy Stewart
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> wrote the code below: not only does it removes the 'hlsearch' problem, but it
> also makes search easier by foregrounding matches and letting you jump from
> one to the next without leaving the search. I find it quite comfortable, but
> of course others might find that just terrible. Here's how it works:
I really like this – thanks!
> If anybody is interested, I can make that into a plugin (rewriting it a little
> bit less sloppily, because it will fail in some cases, plus it requires a few
> options to be really interesting), in case, of course, such a plugin does not
> already exist :)
That would be great, if you have the time. I'd prefer to drop in a plugin that enlarge my vimrc.
Yours,
Andy Stewart
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Thursday, November 28, 2013
Re: Encoding Issues on Windows
First of all, could you type `chcp` in terminal and tell me what is your default codepage? Thanks.
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Encoding Issues on Windows
hi Alexander,
>Now, the problem is that I don't understand why when I type anything non-ANSI in terminal Vim, I see `?` symbols? Furthermore, Airline does not display fancy symbols from patched Consolas as well.How to configure true Unicode for terminal Vim on Win32?
I download ConEmu and find the same question as you.
after a little goole,I press:
:set termencoding
and find *utf-8*
then, I put those in my _vimrc:
set encoding=utf-8 "解决各种乱码问题
if has("win32") || has("win64")
set termencoding=gbk
endif
if has("linux") || has("unix")
set termencoding=utf-8
endif
and question disappear! :)
dyh_2011
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: vim slow, Lisp, etc.
Excerpts from Nikolay Pavlov's message of Thu Nov 28 20:56:15 +0100 2013:
> It is completely distribution-specific. I would write ebuild in this case
> (Gentoo-specific) or leave vim not installed and running from mercurial
> repository where it was build (assuming I am the only user on the machine;
> otherwise *only* ebuild).
nixos.org is little bit smarter than gentoo, but also newer (eventually
less packages).
vim with racket support can be installed easily by adding 2 lines to a
configuration file.
The most important difference is that you can always rollback after
upgrades if something breaks. Might be of interest if you depend on your
computer ..
(You should have a backup anyway ..)
Marc Weber
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> It is completely distribution-specific. I would write ebuild in this case
> (Gentoo-specific) or leave vim not installed and running from mercurial
> repository where it was build (assuming I am the only user on the machine;
> otherwise *only* ebuild).
nixos.org is little bit smarter than gentoo, but also newer (eventually
less packages).
vim with racket support can be installed easily by adding 2 lines to a
configuration file.
The most important difference is that you can always rollback after
upgrades if something breaks. Might be of interest if you depend on your
computer ..
(You should have a backup anyway ..)
Marc Weber
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: vim slow, Lisp, etc.
Ed Kostas wrote:
> On Thursday, November 28, 2013 2:25:40 PM UTC-2, mfid...@meetinghouse.net wrote:
>> Ed Kostas wrote:
>>
>>> 3- It seems that there is a Vi clone that does everything these lawyers want. It is fast in dealing with large Latex sources, it has an org-mode that works like emacs, etc. etc. It is called Evil. Third question: What am I loosing if I work with Evil?
>> A little googling yields this: https://gitorious.org/evil/pages/Home
>>
>> Which describes Evil as "an *e*xtensible *vi* *l*ayer for Emacs
>>
>> <http://www.gnu.org/software/emacs/>. It emulates the main features of
>>
>> Vim <http://www.vim.org/>, and provides facilities for writing custom
>>
>> extensions."
>>
>>
>>
>> In other words, it makes emacs look like vim. So all the features
>>
>> they're using now - including the analysis routines written in lisp;
>>
>> through a simpler interface.
>>
>>
>>
>> But a larger question here: Why are they even considering moving to
>>
>> Vim? They seem to be using a lot of critical emacs features
>>
>> (particularly those based on lisp) - how would they be able to do their
>>
>> work without those features? If they're looking for a simpler
>>
>> interface, then maybe Evil would help, but then there are a few nice
>>
>> GUIs for emacs that might make more sense.
>>
>>
> Well, Miles. For lawyers, mandatory electronic pleading is a novelty. Even in the United States it is quite recent. In Brazil, it became mandatory two years ago. In Philippines, two months ago. Here are news from Philippines:
First off, kill the snide responses - not very useful when asking for help.
Second, what does the Philippines have to do with anything?
> The fact is that lawyers don't know what they need. Everything is very
> recent. They ask experts and the answer is: Emacs or Vim. I mean,
> there are experts that recommend Vim. Other experts recommend Emacs.
> The solution is checking both. That is what most lawyers are doing.
Ok, you asked a very specific question: "What am I loosing if I work
with Evil?" With the implication of "in comparison with either emacs or
vim." To be very clear, the answer appears to be "nothing" - you're
gaining in comparison to both:
1. you get org-mode
2. you get properly functioning elisp scripts
3. you get a vim-like interface
It simply doesn't sound like basic vim gets you what you're asking for.
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> On Thursday, November 28, 2013 2:25:40 PM UTC-2, mfid...@meetinghouse.net wrote:
>> Ed Kostas wrote:
>>
>>> 3- It seems that there is a Vi clone that does everything these lawyers want. It is fast in dealing with large Latex sources, it has an org-mode that works like emacs, etc. etc. It is called Evil. Third question: What am I loosing if I work with Evil?
>> A little googling yields this: https://gitorious.org/evil/pages/Home
>>
>> Which describes Evil as "an *e*xtensible *vi* *l*ayer for Emacs
>>
>> <http://www.gnu.org/software/emacs/>. It emulates the main features of
>>
>> Vim <http://www.vim.org/>, and provides facilities for writing custom
>>
>> extensions."
>>
>>
>>
>> In other words, it makes emacs look like vim. So all the features
>>
>> they're using now - including the analysis routines written in lisp;
>>
>> through a simpler interface.
>>
>>
>>
>> But a larger question here: Why are they even considering moving to
>>
>> Vim? They seem to be using a lot of critical emacs features
>>
>> (particularly those based on lisp) - how would they be able to do their
>>
>> work without those features? If they're looking for a simpler
>>
>> interface, then maybe Evil would help, but then there are a few nice
>>
>> GUIs for emacs that might make more sense.
>>
>>
> Well, Miles. For lawyers, mandatory electronic pleading is a novelty. Even in the United States it is quite recent. In Brazil, it became mandatory two years ago. In Philippines, two months ago. Here are news from Philippines:
First off, kill the snide responses - not very useful when asking for help.
Second, what does the Philippines have to do with anything?
> The fact is that lawyers don't know what they need. Everything is very
> recent. They ask experts and the answer is: Emacs or Vim. I mean,
> there are experts that recommend Vim. Other experts recommend Emacs.
> The solution is checking both. That is what most lawyers are doing.
Ok, you asked a very specific question: "What am I loosing if I work
with Evil?" With the implication of "in comparison with either emacs or
vim." To be very clear, the answer appears to be "nothing" - you're
gaining in comparison to both:
1. you get org-mode
2. you get properly functioning elisp scripts
3. you get a vim-like interface
It simply doesn't sound like basic vim gets you what you're asking for.
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Text Editing on an Infinite Plane (A Project)
2013/11/27 Liang Li <q335r49@gmail.com>
I'm not quite sure what you mean by a "graph of windows"... for me, it was just a way to keep track of memories spatially rather than via a more traditional hierarchical structure. For example, in the future, I Imagine having a "link" that would literally zoom you across the map to another location.On Wed, Nov 27, 2013 at 4:49 AM, Gautier DI FOLCO <gautier.difolco@gmail.com> wrote:
2013/11/26 Liang Li <q335r49@gmail.com>
Hey guys!
Here is a project I've been working on that's nearing completing. Check out the demo at:
http://www.youtube.com/watch?v=_c_het11TBo
It tries to provide a new paradigm for writing massive amounts of prose by simulating an infinite plane via "panning" splits. Tell me what you think!Thanks,
Liang
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hello,I think it is an interesting project, it opens many ways, for example: be able to have a graph of windows which represents the structure of a concurrent program based on its modules' interactions.
Regards.
Yes, this is the same idea, applied to another context :)
I am impatient to see how it will evolve.
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: vim slow, Lisp, etc.
On Thursday, November 28, 2013 4:50:17 PM UTC-2, Gary Johnson wrote:
> On 2013-11-28, Nikolay Pavlov wrote:
>
>
>
> > Also using "make install" is considered a bad practice for any
>
> > distribution. It does not do something like rendering vim unusable,
>
> > but maintaining jobs (like updating software on machine) will
>
> > become such a pain in ass if you have packages installed like this.
>
>
>
> "make install" is pretty standard practice and this is the first I've
>
> heard that it is considered bad. It has always worked fine for me.
>
> The only problem I can think of is that it is not always easy to
>
> uninstall programs, but I never do that.
>
>
>
> What do you recommend instead?
>
>
>
> Regards,
>
> Gary
Besides this, Gary, there is the problem that the people I am talking about are computer illiterates, and proud of it. The most complex thing the can do is configure, make, make install. And believe me, they need two or three hours of training, before they can use the console to configure, make and make install. Don't ask them to learn where to install this and that.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> On 2013-11-28, Nikolay Pavlov wrote:
>
>
>
> > Also using "make install" is considered a bad practice for any
>
> > distribution. It does not do something like rendering vim unusable,
>
> > but maintaining jobs (like updating software on machine) will
>
> > become such a pain in ass if you have packages installed like this.
>
>
>
> "make install" is pretty standard practice and this is the first I've
>
> heard that it is considered bad. It has always worked fine for me.
>
> The only problem I can think of is that it is not always easy to
>
> uninstall programs, but I never do that.
>
>
>
> What do you recommend instead?
>
>
>
> Regards,
>
> Gary
Besides this, Gary, there is the problem that the people I am talking about are computer illiterates, and proud of it. The most complex thing the can do is configure, make, make install. And believe me, they need two or three hours of training, before they can use the console to configure, make and make install. Don't ask them to learn where to install this and that.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: vim slow, Lisp, etc.
On Thursday, November 28, 2013 11:45:52 AM UTC-2, MarcWeber wrote:
> Excerpts from Ed Kostas's message of Thu Nov 28 14:27:30 +0100 2013:
>
> > However, the syntax colors disappeared. I am sure that you expected that.
>
> Sure.
>
>
>
> Try this in your .vimrc to get the old engine:
>
> set regexpengine=1
>
>
>
> If this makes Vim fast again this bug should be reported on vim-dev
>
> with sample file.
>
>
>
> > 2)
>
> > I would appreciate if somebody know how to do it, and could
>
> > provide a command line to build vim with Racket.
>
> Which operating system ? ...
>
>
>
> --enable-mzscheme or such should be enough (after having installed
>
> racket). See ./configure --help
>
>
>
> Marc Weber
Everybody here (something like 40 people) tried this --enable-mzscheme. People tried it in many Linux distributions (Mint, Zorin, Ubuntu, Slackware, etc.) Here is the result:
checking MzScheme install prefix... /usr/local
checking if scheme.h can be found in /usr/local/include... no
checking if scheme.h can be found in /usr/local/include/plt... no
checking if scheme.h can be found in /usr/local/include/racket... yes
checking for racket collects directory... /usr/local/lib/racket/
checking for mzscheme_base.c... needed
checking for ffi_type_void in -lffi... no
checking if compile and link flags for MzScheme are sane... no: MZSCHEME DISABLED
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Excerpts from Ed Kostas's message of Thu Nov 28 14:27:30 +0100 2013:
>
> > However, the syntax colors disappeared. I am sure that you expected that.
>
> Sure.
>
>
>
> Try this in your .vimrc to get the old engine:
>
> set regexpengine=1
>
>
>
> If this makes Vim fast again this bug should be reported on vim-dev
>
> with sample file.
>
>
>
> > 2)
>
> > I would appreciate if somebody know how to do it, and could
>
> > provide a command line to build vim with Racket.
>
> Which operating system ? ...
>
>
>
> --enable-mzscheme or such should be enough (after having installed
>
> racket). See ./configure --help
>
>
>
> Marc Weber
Everybody here (something like 40 people) tried this --enable-mzscheme. People tried it in many Linux distributions (Mint, Zorin, Ubuntu, Slackware, etc.) Here is the result:
checking MzScheme install prefix... /usr/local
checking if scheme.h can be found in /usr/local/include... no
checking if scheme.h can be found in /usr/local/include/plt... no
checking if scheme.h can be found in /usr/local/include/racket... yes
checking for racket collects directory... /usr/local/lib/racket/
checking for mzscheme_base.c... needed
checking for ffi_type_void in -lffi... no
checking if compile and link flags for MzScheme are sane... no: MZSCHEME DISABLED
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: vim slow, Lisp, etc.
On Thursday, November 28, 2013 2:25:40 PM UTC-2, mfid...@meetinghouse.net wrote:
> Ed Kostas wrote:
>
> > 3- It seems that there is a Vi clone that does everything these lawyers want. It is fast in dealing with large Latex sources, it has an org-mode that works like emacs, etc. etc. It is called Evil. Third question: What am I loosing if I work with Evil?
>
> >
>
> >
>
> A little googling yields this: https://gitorious.org/evil/pages/Home
>
> Which describes Evil as "an *e*xtensible *vi* *l*ayer for Emacs
>
> <http://www.gnu.org/software/emacs/>. It emulates the main features of
>
> Vim <http://www.vim.org/>, and provides facilities for writing custom
>
> extensions."
>
>
>
> In other words, it makes emacs look like vim. So all the features
>
> they're using now - including the analysis routines written in lisp;
>
> through a simpler interface.
>
>
>
> But a larger question here: Why are they even considering moving to
>
> Vim? They seem to be using a lot of critical emacs features
>
> (particularly those based on lisp) - how would they be able to do their
>
> work without those features? If they're looking for a simpler
>
> interface, then maybe Evil would help, but then there are a few nice
>
> GUIs for emacs that might make more sense.
>
>
>
> Miles Fidelman
>
>
>
> --
>
> In theory, there is no difference between theory and practice.
>
> In practice, there is. .... Yogi Berra
Well, Miles. For lawyers, mandatory electronic pleading is a novelty. Even in the United States it is quite recent. In Brazil, it became mandatory two years ago. In Philippines, two months ago. Here are news from Philippines:
Beginning October, the Supreme Court will require petitioners to submit electronic copies or "soft copies" of all pleadings filed with the high court, in an effort to go "paperless."
Therefore, lawyers still don't know what tools are good for them. In most countries, however, the rules are:
1 -- The document must be filled in text format. This makes sense, because other formats would require a special tools for reading. For example, docx requires MS Word. However, some countries, like Brazil, accept documents in pdf.
2 -- The text format must provide directives for outline. This is necessary, because the judge and lawyers need to survey the documents, overview pleadings, etc. Even a single lawsuit or criminal prosecution may have 5000 pages of legalese.
3 -- In countries that allow pdf documents, like Brazil and Paraguay, it is necessary to have a tool to generate pdf from the outline directives. Lawyers also like to post an summaries and surveys on special pages for their clients. These pages are also generated from text with outline directives. You know, a lawyer must be sure that her clients are satisfied, because an unhappy client may be dangerous.
4 -- Electronic translations may be necessary in a globalized world.
5 -- A protocol to send emails, electronic signatures, cryptography, etc.
The fact is that lawyers don't know what they need. Everything is very recent. They ask experts and the answer is: Emacs or Vim. I mean, there are experts that recommend Vim. Other experts recommend Emacs. The solution is checking both. That is what most lawyers are doing.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Ed Kostas wrote:
>
> > 3- It seems that there is a Vi clone that does everything these lawyers want. It is fast in dealing with large Latex sources, it has an org-mode that works like emacs, etc. etc. It is called Evil. Third question: What am I loosing if I work with Evil?
>
> >
>
> >
>
> A little googling yields this: https://gitorious.org/evil/pages/Home
>
> Which describes Evil as "an *e*xtensible *vi* *l*ayer for Emacs
>
> <http://www.gnu.org/software/emacs/>. It emulates the main features of
>
> Vim <http://www.vim.org/>, and provides facilities for writing custom
>
> extensions."
>
>
>
> In other words, it makes emacs look like vim. So all the features
>
> they're using now - including the analysis routines written in lisp;
>
> through a simpler interface.
>
>
>
> But a larger question here: Why are they even considering moving to
>
> Vim? They seem to be using a lot of critical emacs features
>
> (particularly those based on lisp) - how would they be able to do their
>
> work without those features? If they're looking for a simpler
>
> interface, then maybe Evil would help, but then there are a few nice
>
> GUIs for emacs that might make more sense.
>
>
>
> Miles Fidelman
>
>
>
> --
>
> In theory, there is no difference between theory and practice.
>
> In practice, there is. .... Yogi Berra
Well, Miles. For lawyers, mandatory electronic pleading is a novelty. Even in the United States it is quite recent. In Brazil, it became mandatory two years ago. In Philippines, two months ago. Here are news from Philippines:
Beginning October, the Supreme Court will require petitioners to submit electronic copies or "soft copies" of all pleadings filed with the high court, in an effort to go "paperless."
Therefore, lawyers still don't know what tools are good for them. In most countries, however, the rules are:
1 -- The document must be filled in text format. This makes sense, because other formats would require a special tools for reading. For example, docx requires MS Word. However, some countries, like Brazil, accept documents in pdf.
2 -- The text format must provide directives for outline. This is necessary, because the judge and lawyers need to survey the documents, overview pleadings, etc. Even a single lawsuit or criminal prosecution may have 5000 pages of legalese.
3 -- In countries that allow pdf documents, like Brazil and Paraguay, it is necessary to have a tool to generate pdf from the outline directives. Lawyers also like to post an summaries and surveys on special pages for their clients. These pages are also generated from text with outline directives. You know, a lawyer must be sure that her clients are satisfied, because an unhappy client may be dangerous.
4 -- Electronic translations may be necessary in a globalized world.
5 -- A protocol to send emails, electronic signatures, cryptography, etc.
The fact is that lawyers don't know what they need. Everything is very recent. They ask experts and the answer is: Emacs or Vim. I mean, there are experts that recommend Vim. Other experts recommend Emacs. The solution is checking both. That is what most lawyers are doing.
--
--
You received this message from the "vim_use" 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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.