On Saturday, July 21, 2018 at 9:36:07 PM UTC-5, tom arnall wrote:
> here it is:
>
> :vmap <c-i> "+y
>
> then when i do <c-i> nothing happens
Works for me. When I highlight text in visual mode, then hold CTRL and press the I key, the highlighted text is placed in the '+' register (system clipboard).
If you do ":version", does the output show "+clipboard"? Does "+y work for you outside of a mapping?
--
--
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/d/optout.
Friday, August 31, 2018
Re: Reformat single-line HTML
Following up on you own post, I did find a suggestion to use "tidy -i" as a filter. This seems to be reasonable. I would still love to hear any other better ideas you may have.
--
--
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/d/optout.
--
--
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/d/optout.
Reformat single-line HTML
I'm getting some raw HTML -- usually from the page source of website -- that is formatted as a single line of thousands of characters. Can vim automatically reformat this into readable and indented code? If not, is there a good filter program you can suggest to do the job. 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/d/optout.
--
--
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/d/optout.
No Cyrlillic text in CP866
Hello, all
I am using text-mode Vim on Windows XP, where 'chcp'
tells me that the terminal encoding is cp866. Why
can't I type Russian characters with enc=cp866? It
works with enc=utf-8, though, but I expect Vim also
to support Cyrillic while using and encoding that
matches with that of the terminal...
--
Please, do not forward replies to the list to my e-mail.
--
--
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/d/optout.
I am using text-mode Vim on Windows XP, where 'chcp'
tells me that the terminal encoding is cp866. Why
can't I type Russian characters with enc=cp866? It
works with enc=utf-8, though, but I expect Vim also
to support Cyrillic while using and encoding that
matches with that of the terminal...
--
Please, do not forward replies to the list to my e-mail.
--
--
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/d/optout.
Thursday, August 30, 2018
Re: Accessing mapping from rhs
On 30/08/2018 20:37, Christian Brabandt wrote:
>
> On Do, 30 Aug 2018, John Passaro wrote:
>
>> Could you implement the function and accompanying mapping as follows?
>>
>> imap <expr> <cr> MyFunction("cr")
>> imap <expr> <Leader>n MyFunction("Leader-n")
>
> This is the typical workaround. The idea was to be able to know in the
> function which mapping triggered the call to it, without having special
> arguments (which look like they contain redundant information).
Christian, John,
thanks for your replies. Yes, that's what I am currently doing in my
plugin, and it's a very flexible solution, since the argument of
MyFunction does not have to be equal to the lhs.
I was just curious whether one could replace it with
imap <cr> <plug>(MyPlug)
where <plug>(MyPlug) maps to some function. In this case, you cannot
pass arguments, so I was wondering whether one could access the lhs of
the mapping through the plug (presumably, via some special variable).
I couldn't find any way, but I wanted to make sure I wasn't missing
anything from the documentation.
To be clear, this is not a feature request: the "typical workaround", as
I've said, is just fine.
Thanks again,
Life.
--
--
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/d/optout.
>
> On Do, 30 Aug 2018, John Passaro wrote:
>
>> Could you implement the function and accompanying mapping as follows?
>>
>> imap <expr> <cr> MyFunction("cr")
>> imap <expr> <Leader>n MyFunction("Leader-n")
>
> This is the typical workaround. The idea was to be able to know in the
> function which mapping triggered the call to it, without having special
> arguments (which look like they contain redundant information).
Christian, John,
thanks for your replies. Yes, that's what I am currently doing in my
plugin, and it's a very flexible solution, since the argument of
MyFunction does not have to be equal to the lhs.
I was just curious whether one could replace it with
imap <cr> <plug>(MyPlug)
where <plug>(MyPlug) maps to some function. In this case, you cannot
pass arguments, so I was wondering whether one could access the lhs of
the mapping through the plug (presumably, via some special variable).
I couldn't find any way, but I wanted to make sure I wasn't missing
anything from the documentation.
To be clear, this is not a feature request: the "typical workaround", as
I've said, is just fine.
Thanks again,
Life.
--
--
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/d/optout.
Re: Accessing mapping from rhs
On Do, 30 Aug 2018, John Passaro wrote:
> Could you implement the function and accompanying mapping as follows?
>
> imap <expr> <cr> MyFunction("cr")
> imap <expr> <Leader>n MyFunction("Leader-n")
This is the typical workaround. The idea was to be able to know in the
function which mapping triggered the call to it, without having special
arguments (which look like they contain redundant information).
Best,
Christian
--
Auch wenn es Dich empört: Das Unerlaubte Vergnügen macht Spaß.
-- Ovid (43 v.Chr.-18 n.Chr)
--
--
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/d/optout.
> Could you implement the function and accompanying mapping as follows?
>
> imap <expr> <cr> MyFunction("cr")
> imap <expr> <Leader>n MyFunction("Leader-n")
This is the typical workaround. The idea was to be able to know in the
function which mapping triggered the call to it, without having special
arguments (which look like they contain redundant information).
Best,
Christian
--
Auch wenn es Dich empört: Das Unerlaubte Vergnügen macht Spaß.
-- Ovid (43 v.Chr.-18 n.Chr)
--
--
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/d/optout.
Re: Accessing mapping from rhs
Could you implement the function and accompanying mapping as follows?
imap <expr> <cr> MyFunction("cr")
imap <expr> <Leader>n MyFunction("Leader-n")
Sorry if this is obvious, if it is impractical for some reason I'm curious why.
John Passaro
(917) 678-8293
(917) 678-8293
On Thu, Aug 30, 2018 at 1:18 PM, Christian Brabandt <cblists@256bit.org> wrote:
On Do, 30 Aug 2018, Lifepillar wrote:
> Is it possible to access the lhs of a mapping from its rhs?
> For example, given:
>
> imap <expr> <cr> MyFunction()
>
> is there a way for MyFunction() to know that it was called by <cr>?
Not that I know of and I have whished for that before.
Best,
Christian
--
Wenn ein Kolonialwarenhändler in seinem kleinen Laden so viele
Dummheiten und Fehler machte wie die Staatsmänner und Generäle in
ihren großen Ländern, wäre er in spätestens vier Wochen bankrott.
-- Erich Kästner
--
--
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/d/optout .
--
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/d/optout.
Re: Accessing mapping from rhs
On Do, 30 Aug 2018, Lifepillar wrote:
> Is it possible to access the lhs of a mapping from its rhs?
> For example, given:
>
> imap <expr> <cr> MyFunction()
>
> is there a way for MyFunction() to know that it was called by <cr>?
Not that I know of and I have whished for that before.
Best,
Christian
--
Wenn ein Kolonialwarenhändler in seinem kleinen Laden so viele
Dummheiten und Fehler machte wie die Staatsmänner und Generäle in
ihren großen Ländern, wäre er in spätestens vier Wochen bankrott.
-- Erich Kästner
--
--
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/d/optout.
> Is it possible to access the lhs of a mapping from its rhs?
> For example, given:
>
> imap <expr> <cr> MyFunction()
>
> is there a way for MyFunction() to know that it was called by <cr>?
Not that I know of and I have whished for that before.
Best,
Christian
--
Wenn ein Kolonialwarenhändler in seinem kleinen Laden so viele
Dummheiten und Fehler machte wie die Staatsmänner und Generäle in
ihren großen Ländern, wäre er in spätestens vier Wochen bankrott.
-- Erich Kästner
--
--
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/d/optout.
Re: How can i add the same string to many lines ?
On 2018-08-30 09:01, Antharia Jack wrote:
> I would like to add target="_blank" to all my href in a html file.
> I would like to say to vim : add this string after the second "
> symbol of each line where is the word href.
If all hrefs are quoted and use the same quotation, it's pretty
straightforward:
:%s/href="[^"*"/& target="_blank"/g
However it becomes more complex if you have other complications like
a mix of single- and double-quotes or unquoted values; or href="..."
in something other than an <a> tag that you want to leave alone.
For a fairly robust implementation, assuming all hrefs are quoted, one
can do
:%s/<a\_s\+href=\("[^"]*"\|'[^']*'\|\s\+\)\zs/ target="_blank"/g
Still has issues if they cross lines or you have other attributes
between the <a> and the href= attribute, like
<a style=foo href=blah>
or
<a
href=blah
>
but should simplify the work you need to do.
-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/d/optout.
> I would like to add target="_blank" to all my href in a html file.
> I would like to say to vim : add this string after the second "
> symbol of each line where is the word href.
If all hrefs are quoted and use the same quotation, it's pretty
straightforward:
:%s/href="[^"*"/& target="_blank"/g
However it becomes more complex if you have other complications like
a mix of single- and double-quotes or unquoted values; or href="..."
in something other than an <a> tag that you want to leave alone.
For a fairly robust implementation, assuming all hrefs are quoted, one
can do
:%s/<a\_s\+href=\("[^"]*"\|'[^']*'\|\s\+\)\zs/ target="_blank"/g
Still has issues if they cross lines or you have other attributes
between the <a> and the href= attribute, like
<a style=foo href=blah>
or
<a
href=blah
>
but should simplify the work you need to do.
-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/d/optout.
Accessing mapping from rhs
Is it possible to access the lhs of a mapping from its rhs?
For example, given:
imap <expr> <cr> MyFunction()
is there a way for MyFunction() to know that it was called by <cr>?
Thanks,
Life.
--
--
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/d/optout.
For example, given:
imap <expr> <cr> MyFunction()
is there a way for MyFunction() to know that it was called by <cr>?
Thanks,
Life.
--
--
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/d/optout.
Re: How can i add the same string to many lines ?
On 08/30/2018 10:01 AM, Antharia Jack wrote:
> Hello everyone ?
Hi,
> I would like to add target="_blank" to all my href in a html file.
Okay. That seems odd, but you do your own thing.
> I would like to say to vim : add this string after the second " symbol
> of each line where is the word href.
Can you provide an example?
I'd be inclined to try a regular expression like the following.
:%s/<a href=\(.\{-1,}\)>/<a href=\1 target="_blank">/g
Use a non-greedy wildcard match to find an anchor tag (assuming it
starts with href) and append the target="_blank" to the end.
> For now i just use the dot command to each line.
That's annoying, especially if you have a LOT of anchor tags to change.
> Thanks for reading.
:-)
--
Grant. . . .
unix || die
--
--
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/d/optout.
> Hello everyone ?
Hi,
> I would like to add target="_blank" to all my href in a html file.
Okay. That seems odd, but you do your own thing.
> I would like to say to vim : add this string after the second " symbol
> of each line where is the word href.
Can you provide an example?
I'd be inclined to try a regular expression like the following.
:%s/<a href=\(.\{-1,}\)>/<a href=\1 target="_blank">/g
Use a non-greedy wildcard match to find an anchor tag (assuming it
starts with href) and append the target="_blank" to the end.
> For now i just use the dot command to each line.
That's annoying, especially if you have a LOT of anchor tags to change.
> Thanks for reading.
:-)
--
Grant. . . .
unix || die
--
--
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/d/optout.
How can i add the same string to many lines ?
Hello everyone ?
I would like to add target="_blank" to all my href in a html file.
I would like to say to vim : add this string after the second " symbol of each line where is the word href.
For now i just use the dot command to each line.
Thanks for reading.
--
--
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/d/optout.
I would like to add target="_blank" to all my href in a html file.
I would like to say to vim : add this string after the second " symbol of each line where is the word href.
For now i just use the dot command to each line.
Thanks for reading.
--
--
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/d/optout.
Re: About using vartabstop
Hi,
2018-8-30(Thu) 14:36:09 UTC+9 Christian Brabandt:
> On Mi, 29 Aug 2018, Lifepillar wrote:
>
> > There's a meme (if it may be called so) circulating on Twitter
> > about using Fibonacci sequences for indentation. Just for fun,
> > I wanted to see if it could be implemented using the vartabs
> > feature. I thought that this would do it (for C files):
> >
> > set shiftwidth=0
> > set noexpandtab
> > set vartabstop=1,1,2,3,5,8,13,21,34
> > set autoindent
> > set smartindent
> > set ft=c
> >
> > With the above settings, it appears that the value of tabstop
> > is used. This seems to agree with shiftwidth's documentation:
> > "When [shiftwidth is] zero the 'ts' value will be used", but
> > not with tabstop's help: "the value of 'tabstop' will be
> > ignored while 'vartabstop' is set". Putting together the two,
> > I would expect the above to use vartabstop.
> >
> > Am I missing something?
>
> I am not sure. It might be, that the functionality of using the tabstop
> setting when shiftwidth is zero is indeed missing from vartabstop,
> because this was done some time after the vartab patch has been created
> and that feature has than not made it back into the vartabs patch.
>
> I'll have a look at it in more detail later.
I also tried Fibonacci indent with the vartabstop option yesterday. 😃
https://twitter.com/h_east/status/1034606768226070528 (Japanese)
It worked well for files already indented with tabs, but auto indentation in insert mode did not work well.
I investigated for a moment but I could not fix it.
Probably we will fix it by modifying tabstop_padding().
--
Best regards,
Hirohito Higashi (h_east)
--
--
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/d/optout.
2018-8-30(Thu) 14:36:09 UTC+9 Christian Brabandt:
> On Mi, 29 Aug 2018, Lifepillar wrote:
>
> > There's a meme (if it may be called so) circulating on Twitter
> > about using Fibonacci sequences for indentation. Just for fun,
> > I wanted to see if it could be implemented using the vartabs
> > feature. I thought that this would do it (for C files):
> >
> > set shiftwidth=0
> > set noexpandtab
> > set vartabstop=1,1,2,3,5,8,13,21,34
> > set autoindent
> > set smartindent
> > set ft=c
> >
> > With the above settings, it appears that the value of tabstop
> > is used. This seems to agree with shiftwidth's documentation:
> > "When [shiftwidth is] zero the 'ts' value will be used", but
> > not with tabstop's help: "the value of 'tabstop' will be
> > ignored while 'vartabstop' is set". Putting together the two,
> > I would expect the above to use vartabstop.
> >
> > Am I missing something?
>
> I am not sure. It might be, that the functionality of using the tabstop
> setting when shiftwidth is zero is indeed missing from vartabstop,
> because this was done some time after the vartab patch has been created
> and that feature has than not made it back into the vartabs patch.
>
> I'll have a look at it in more detail later.
I also tried Fibonacci indent with the vartabstop option yesterday. 😃
https://twitter.com/h_east/status/1034606768226070528 (Japanese)
It worked well for files already indented with tabs, but auto indentation in insert mode did not work well.
I investigated for a moment but I could not fix it.
Probably we will fix it by modifying tabstop_padding().
--
Best regards,
Hirohito Higashi (h_east)
--
--
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/d/optout.
Wednesday, August 29, 2018
Re: International Vim conference VimConf 2018
Note that timezone: https://www.timeanddate.com/worldclock/converter.html?iso=20180917T040000&p1=248&p2=1440
--
--
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/d/optout.
--
--
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/d/optout.
Re: About using vartabstop
On Thu, 30 Aug 2018 00:20:18 +0100
David Woodfall <dave@dawoodfall.net> wrote:
> On Wednesday 29 August 2018 18:47,
> Lifepillar <lifepillar@lifepillar.me> put forth the proposition:
> > There's a meme (if it may be called so) circulating on Twitter
> > about using Fibonacci sequences for indentation. Just for fun,
> > I wanted to see if it could be implemented using the vartabs
> > feature. I thought that this would do it (for C files):
> >
> > set shiftwidth=0
> > set noexpandtab
>
> Won't this change *all* tab indents to the same size? Surely you need
> to use expandtab?
>
> > set vartabstop=1,1,2,3,5,8,13,21,34
> > set autoindent
> > set smartindent
> > set ft=c
> >
> > With the above settings, it appears that the value of tabstop
> > is used. This seems to agree with shiftwidth's documentation:
> > "When [shiftwidth is] zero the 'ts' value will be used", but
> > not with tabstop's help: "the value of 'tabstop' will be
> > ignored while 'vartabstop' is set". Putting together the two,
> > I would expect the above to use vartabstop.
> >
> > Am I missing something?
>
> I think it may need more work than that, but I may be wrong.
>
> You may need to indentexpr to a custom function and use that
> to set ind.
>
> See :help indentexpr
It looks like someone else saw that twitter post :)
https://github.com/dodie/vim-fibo-indent
Related:
https://github.com/dodie/vim-disapprove-deep-indentation
ಠ_ಠ
-Dave
--
--
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/d/optout.
David Woodfall <dave@dawoodfall.net> wrote:
> On Wednesday 29 August 2018 18:47,
> Lifepillar <lifepillar@lifepillar.me> put forth the proposition:
> > There's a meme (if it may be called so) circulating on Twitter
> > about using Fibonacci sequences for indentation. Just for fun,
> > I wanted to see if it could be implemented using the vartabs
> > feature. I thought that this would do it (for C files):
> >
> > set shiftwidth=0
> > set noexpandtab
>
> Won't this change *all* tab indents to the same size? Surely you need
> to use expandtab?
>
> > set vartabstop=1,1,2,3,5,8,13,21,34
> > set autoindent
> > set smartindent
> > set ft=c
> >
> > With the above settings, it appears that the value of tabstop
> > is used. This seems to agree with shiftwidth's documentation:
> > "When [shiftwidth is] zero the 'ts' value will be used", but
> > not with tabstop's help: "the value of 'tabstop' will be
> > ignored while 'vartabstop' is set". Putting together the two,
> > I would expect the above to use vartabstop.
> >
> > Am I missing something?
>
> I think it may need more work than that, but I may be wrong.
>
> You may need to indentexpr to a custom function and use that
> to set ind.
>
> See :help indentexpr
It looks like someone else saw that twitter post :)
https://github.com/dodie/vim-fibo-indent
Related:
https://github.com/dodie/vim-disapprove-deep-indentation
ಠ_ಠ
-Dave
--
--
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/d/optout.
Re: International Vim conference VimConf 2018
On Tuesday, July 31, 2018 at 3:47:25 PM UTC+9, Yasuhiro MATSUMOTO wrote:
> Hello Vim users!
>
> Announcing an international Vim conference VimConf 2018 and its CFP being open.
>
> https://vimconf.org/2018/
>
> VimConf is the only and the first international Vim conference that has been running periodically by a Vim community. It had been running for 5 times, and in Tokyo, Japan, so far. We organize VimConf this year again. It'll be in Tokyo, Japan, on Nov 24, 2018.
> I'm going to give a keynote speech there this year. This is a big news you probably don't know, Bram has plan to come to vimconf 2018!!
>
> All the talks will be translated to English/Japanese vice versa. The tickets to participate aren't sold yet but you can already submit a proposal to speech there. Would you like to try talking there to share what you know about Vim inside?
> Please check the VimConf website for details.
>
> See you there,
> mattn
We are having an international Vim conference VimConf 2018 on 2018-11-24 in Tokyo, Japan
As you might already know, Bram Moolenaar, the creator of Vim, gives keynote speech this year!
We are going to start selling tickets on 2018-09-17 1:00 PM JST.
Those interested in participating VimConf 2018, please check the official website below.
https://vimconf.org/2018/
Note that the number of tickets is limited, and it's likely sold out very quickly.
--
--
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/d/optout.
> Hello Vim users!
>
> Announcing an international Vim conference VimConf 2018 and its CFP being open.
>
> https://vimconf.org/2018/
>
> VimConf is the only and the first international Vim conference that has been running periodically by a Vim community. It had been running for 5 times, and in Tokyo, Japan, so far. We organize VimConf this year again. It'll be in Tokyo, Japan, on Nov 24, 2018.
> I'm going to give a keynote speech there this year. This is a big news you probably don't know, Bram has plan to come to vimconf 2018!!
>
> All the talks will be translated to English/Japanese vice versa. The tickets to participate aren't sold yet but you can already submit a proposal to speech there. Would you like to try talking there to share what you know about Vim inside?
> Please check the VimConf website for details.
>
> See you there,
> mattn
We are having an international Vim conference VimConf 2018 on 2018-11-24 in Tokyo, Japan
As you might already know, Bram Moolenaar, the creator of Vim, gives keynote speech this year!
We are going to start selling tickets on 2018-09-17 1:00 PM JST.
Those interested in participating VimConf 2018, please check the official website below.
https://vimconf.org/2018/
Note that the number of tickets is limited, and it's likely sold out very quickly.
--
--
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/d/optout.
Re: About using vartabstop
On Mi, 29 Aug 2018, Lifepillar wrote:
> There's a meme (if it may be called so) circulating on Twitter
> about using Fibonacci sequences for indentation. Just for fun,
> I wanted to see if it could be implemented using the vartabs
> feature. I thought that this would do it (for C files):
>
> set shiftwidth=0
> set noexpandtab
> set vartabstop=1,1,2,3,5,8,13,21,34
> set autoindent
> set smartindent
> set ft=c
>
> With the above settings, it appears that the value of tabstop
> is used. This seems to agree with shiftwidth's documentation:
> "When [shiftwidth is] zero the 'ts' value will be used", but
> not with tabstop's help: "the value of 'tabstop' will be
> ignored while 'vartabstop' is set". Putting together the two,
> I would expect the above to use vartabstop.
>
> Am I missing something?
I am not sure. It might be, that the functionality of using the tabstop
setting when shiftwidth is zero is indeed missing from vartabstop,
because this was done some time after the vartab patch has been created
and that feature has than not made it back into the vartabs patch.
I'll have a look at it in more detail later.
Best,
Christian
--
In der Politik ist nicht alles richtig, was rechtens ist.
-- Rezzo Schlauch
--
--
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/d/optout.
> There's a meme (if it may be called so) circulating on Twitter
> about using Fibonacci sequences for indentation. Just for fun,
> I wanted to see if it could be implemented using the vartabs
> feature. I thought that this would do it (for C files):
>
> set shiftwidth=0
> set noexpandtab
> set vartabstop=1,1,2,3,5,8,13,21,34
> set autoindent
> set smartindent
> set ft=c
>
> With the above settings, it appears that the value of tabstop
> is used. This seems to agree with shiftwidth's documentation:
> "When [shiftwidth is] zero the 'ts' value will be used", but
> not with tabstop's help: "the value of 'tabstop' will be
> ignored while 'vartabstop' is set". Putting together the two,
> I would expect the above to use vartabstop.
>
> Am I missing something?
I am not sure. It might be, that the functionality of using the tabstop
setting when shiftwidth is zero is indeed missing from vartabstop,
because this was done some time after the vartab patch has been created
and that feature has than not made it back into the vartabs patch.
I'll have a look at it in more detail later.
Best,
Christian
--
In der Politik ist nicht alles richtig, was rechtens ist.
-- Rezzo Schlauch
--
--
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/d/optout.
Re: About using vartabstop
On Wednesday 29 August 2018 18:47,
Lifepillar <lifepillar@lifepillar.me> put forth the proposition:
> There's a meme (if it may be called so) circulating on Twitter
> about using Fibonacci sequences for indentation. Just for fun,
> I wanted to see if it could be implemented using the vartabs
> feature. I thought that this would do it (for C files):
>
> set shiftwidth=0
> set noexpandtab
Won't this change *all* tab indents to the same size? Surely you need
to use expandtab?
> set vartabstop=1,1,2,3,5,8,13,21,34
> set autoindent
> set smartindent
> set ft=c
>
> With the above settings, it appears that the value of tabstop
> is used. This seems to agree with shiftwidth's documentation:
> "When [shiftwidth is] zero the 'ts' value will be used", but
> not with tabstop's help: "the value of 'tabstop' will be
> ignored while 'vartabstop' is set". Putting together the two,
> I would expect the above to use vartabstop.
>
> Am I missing something?
I think it may need more work than that, but I may be wrong.
You may need to indentexpr to a custom function and use that
to set ind.
See :help indentexpr
-Dave
--
> I get the following error messages at bootup, could anyone tell me
> what they mean?
> fcntl_setlk() called by process 51 (lpd) with broken flock() emulation
They mean that you have not read the documentation when upgrading the
kernel.
-- seen on c.o.l.misc
.--. oo
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'
--
--
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/d/optout.
Lifepillar <lifepillar@lifepillar.me> put forth the proposition:
> There's a meme (if it may be called so) circulating on Twitter
> about using Fibonacci sequences for indentation. Just for fun,
> I wanted to see if it could be implemented using the vartabs
> feature. I thought that this would do it (for C files):
>
> set shiftwidth=0
> set noexpandtab
Won't this change *all* tab indents to the same size? Surely you need
to use expandtab?
> set vartabstop=1,1,2,3,5,8,13,21,34
> set autoindent
> set smartindent
> set ft=c
>
> With the above settings, it appears that the value of tabstop
> is used. This seems to agree with shiftwidth's documentation:
> "When [shiftwidth is] zero the 'ts' value will be used", but
> not with tabstop's help: "the value of 'tabstop' will be
> ignored while 'vartabstop' is set". Putting together the two,
> I would expect the above to use vartabstop.
>
> Am I missing something?
I think it may need more work than that, but I may be wrong.
You may need to indentexpr to a custom function and use that
to set ind.
See :help indentexpr
-Dave
--
> I get the following error messages at bootup, could anyone tell me
> what they mean?
> fcntl_setlk() called by process 51 (lpd) with broken flock() emulation
They mean that you have not read the documentation when upgrading the
kernel.
-- seen on c.o.l.misc
.--. oo
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'
--
--
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/d/optout.
Re: It is impossible to join unless you have a google account
On Tuesday, August 7, 2018 at 6:55:51 AM UTC-6, Bram Moolenaar wrote:
> I get a bit tired of this Google-bashing by people that don't know what
> is actually happening. First do fact checking before you believe what
> you read.
Right, and "fact-checking" reveals that Google has unethical practices. Here's a recent post from the O'Reilly Web Newsletter:
3. Like it or not, Google's tracking you
Google's corporate conduct guidelines famously include the phrase "Don't be evil." But plenty of people find it evil that Google records and stores your movements even when you use privacy settings the company says prevent it from doing so. Read the Associated Press investigation into Google's location tracking. (https://apnews.com/f60bc112665b458cb6473d7ee9492932)
--
--
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/d/optout.
> I get a bit tired of this Google-bashing by people that don't know what
> is actually happening. First do fact checking before you believe what
> you read.
Right, and "fact-checking" reveals that Google has unethical practices. Here's a recent post from the O'Reilly Web Newsletter:
3. Like it or not, Google's tracking you
Google's corporate conduct guidelines famously include the phrase "Don't be evil." But plenty of people find it evil that Google records and stores your movements even when you use privacy settings the company says prevent it from doing so. Read the Associated Press investigation into Google's location tracking. (https://apnews.com/f60bc112665b458cb6473d7ee9492932)
--
--
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/d/optout.
About using vartabstop
There's a meme (if it may be called so) circulating on Twitter
about using Fibonacci sequences for indentation. Just for fun,
I wanted to see if it could be implemented using the vartabs
feature. I thought that this would do it (for C files):
set shiftwidth=0
set noexpandtab
set vartabstop=1,1,2,3,5,8,13,21,34
set autoindent
set smartindent
set ft=c
With the above settings, it appears that the value of tabstop
is used. This seems to agree with shiftwidth's documentation:
"When [shiftwidth is] zero the 'ts' value will be used", but
not with tabstop's help: "the value of 'tabstop' will be
ignored while 'vartabstop' is set". Putting together the two,
I would expect the above to use vartabstop.
Am I missing something?
Thanks,
Life.
--
--
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/d/optout.
about using Fibonacci sequences for indentation. Just for fun,
I wanted to see if it could be implemented using the vartabs
feature. I thought that this would do it (for C files):
set shiftwidth=0
set noexpandtab
set vartabstop=1,1,2,3,5,8,13,21,34
set autoindent
set smartindent
set ft=c
With the above settings, it appears that the value of tabstop
is used. This seems to agree with shiftwidth's documentation:
"When [shiftwidth is] zero the 'ts' value will be used", but
not with tabstop's help: "the value of 'tabstop' will be
ignored while 'vartabstop' is set". Putting together the two,
I would expect the above to use vartabstop.
Am I missing something?
Thanks,
Life.
--
--
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/d/optout.
Re: Opening remote file with scp and netrw on Windows 7
* Oliver Graute (oliver.graute@gmail.com) wrote:
> :e scp://root@192.168.1.229:2222//home/root/output.log
>
> on Linux this is working fine. But on Windows 7 just a command line
> window is opening with this Error message:
>
> C:\Windows\system32\cmd.exe -c "pscp -q -P 2222 "root@192.168.1.229:/home/root/output.log" "C:\Users\OGR\AppData\Local\Temp\VIA3B61.log""
>
> The command "oot" is either misspelled or could not be found.
> shell returned 1
>
> Hit any key to close this window...
I also experienced this problem before on Windows, but it works pretty fine on my BSD, mac or Linux box. When I tried it on Windows with the isolated Vim, it failed. I then switched and tried it again under Cygwin on Windows, this time it worked fine. I believe that without installing wget, curl or something similar on the system or environment, you will not be able to open any remote files with Vim. So IMHO, the problem you are encountering is not Vim itself, but the environment you are using.
--
Gua Chung Lim
"UNIX is basically a simple operating system,
but you have to be a genius to understand the simplicity."
-- Dennis M. Ritchie
--
--
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/d/optout.
> :e scp://root@192.168.1.229:2222//home/root/output.log
>
> on Linux this is working fine. But on Windows 7 just a command line
> window is opening with this Error message:
>
> C:\Windows\system32\cmd.exe -c "pscp -q -P 2222 "root@192.168.1.229:/home/root/output.log" "C:\Users\OGR\AppData\Local\Temp\VIA3B61.log""
>
> The command "oot" is either misspelled or could not be found.
> shell returned 1
>
> Hit any key to close this window...
I also experienced this problem before on Windows, but it works pretty fine on my BSD, mac or Linux box. When I tried it on Windows with the isolated Vim, it failed. I then switched and tried it again under Cygwin on Windows, this time it worked fine. I believe that without installing wget, curl or something similar on the system or environment, you will not be able to open any remote files with Vim. So IMHO, the problem you are encountering is not Vim itself, but the environment you are using.
--
Gua Chung Lim
"UNIX is basically a simple operating system,
but you have to be a genius to understand the simplicity."
-- Dennis M. Ritchie
--
--
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/d/optout.
RFC: New cfilter plugin
Hi all,
Patch 8.1.0311 adds a new optional cfilter.vim plugin to Vim.
A recent runtime update adds additional functionality to this
plugin.
This plugin provides commands (:Cfilter and :Lfilter) which can
be used to filter entries from a quickfix or a location list.
For example, the command ":Cfilter /mypat/" can be used to
create a new quickfix list from the current quickfix list using
entries with filenames or text matching 'mypat'. The command
":Cfilter! /mypat/" can be used to create a quickfix list with
entries not matching 'mypat'. The ":Lfilter" command operates
on the location list.
To load this plugin, add ":packadd cfilter" to your .vimrc file.
Any comments or suggestions about the new plugin are welcome.
Thanks,
Yegappan
--
--
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/d/optout.
Patch 8.1.0311 adds a new optional cfilter.vim plugin to Vim.
A recent runtime update adds additional functionality to this
plugin.
This plugin provides commands (:Cfilter and :Lfilter) which can
be used to filter entries from a quickfix or a location list.
For example, the command ":Cfilter /mypat/" can be used to
create a new quickfix list from the current quickfix list using
entries with filenames or text matching 'mypat'. The command
":Cfilter! /mypat/" can be used to create a quickfix list with
entries not matching 'mypat'. The ":Lfilter" command operates
on the location list.
To load this plugin, add ":packadd cfilter" to your .vimrc file.
Any comments or suggestions about the new plugin are welcome.
Thanks,
Yegappan
--
--
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/d/optout.
Re: Opening remote file with scp and netrw on Windows 7
On Tue, Aug 28, 2018 at 09:22:04PM +0200, Oliver Graute wrote:
> Hello list,
>
> I tried to open a remote file in Vim with this command:
>
> :e scp://root@192.168.1.229:2222//home/root/output.log
>
> on Linux this is working fine. But on Windows 7 just a command line
> window is opening with this Error message:
>
> C:\Windows\system32\cmd.exe -c "pscp -q -P 2222 "root@192.168.1.229:/home/root/output.log" "C:\Users\OGR\AppData\Local\Temp\VIA3B61.log""
>
> The command "oot" is either misspelled or could not be found.
> shell returned 1
>
> Hit any key to close this window...
>
> I'am using vim 8.0 with netrw v156
> Some hints howto fix this?
I guess this has nothing to do with vim, but is in the way Windows
translates and interprets your scp command.
when using (g)vim in Windows, just use the proper command for that
environment ('pscp' ?), so it doesn't need to be translated.
the "oot" error output indeed is somewhat strange...
//meine
--
--
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/d/optout.
> Hello list,
>
> I tried to open a remote file in Vim with this command:
>
> :e scp://root@192.168.1.229:2222//home/root/output.log
>
> on Linux this is working fine. But on Windows 7 just a command line
> window is opening with this Error message:
>
> C:\Windows\system32\cmd.exe -c "pscp -q -P 2222 "root@192.168.1.229:/home/root/output.log" "C:\Users\OGR\AppData\Local\Temp\VIA3B61.log""
>
> The command "oot" is either misspelled or could not be found.
> shell returned 1
>
> Hit any key to close this window...
>
> I'am using vim 8.0 with netrw v156
> Some hints howto fix this?
I guess this has nothing to do with vim, but is in the way Windows
translates and interprets your scp command.
when using (g)vim in Windows, just use the proper command for that
environment ('pscp' ?), so it doesn't need to be translated.
the "oot" error output indeed is somewhat strange...
//meine
--
--
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/d/optout.
Tuesday, August 28, 2018
Opening remote file with scp and netrw on Windows 7
Hello list,
I tried to open a remote file in Vim with this command:
:e scp://root@192.168.1.229:2222//home/root/output.log
on Linux this is working fine. But on Windows 7 just a command line
window is opening with this Error message:
C:\Windows\system32\cmd.exe -c "pscp -q -P 2222 "root@192.168.1.229:/home/root/output.log" "C:\Users\OGR\AppData\Local\Temp\VIA3B61.log""
The command "oot" is either misspelled or could not be found.
shell returned 1
Hit any key to close this window...
I'am using vim 8.0 with netrw v156
Some hints howto fix this?
Best regards,
Oliver
--
--
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/d/optout.
I tried to open a remote file in Vim with this command:
:e scp://root@192.168.1.229:2222//home/root/output.log
on Linux this is working fine. But on Windows 7 just a command line
window is opening with this Error message:
C:\Windows\system32\cmd.exe -c "pscp -q -P 2222 "root@192.168.1.229:/home/root/output.log" "C:\Users\OGR\AppData\Local\Temp\VIA3B61.log""
The command "oot" is either misspelled or could not be found.
shell returned 1
Hit any key to close this window...
I'am using vim 8.0 with netrw v156
Some hints howto fix this?
Best regards,
Oliver
--
--
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/d/optout.
Re: editing textareas in Firefox with vim
Michael Henry wrote:
> Perhaps one last idea for debugging problems with textern; you
> might close Firefox, rename ``~/.mozilla`` out of the way, then
> restart Firefox to generate a new profile, then see if you can
> make textern work. I recently had to do this myself to solve a
> weird Firefox problem I encountered. I never knew what
> incorrect setting or corrupted file in my profile may have been
> responsible for the problem, but the new profile fixed it.
Thanks for your debugging ideas. I have a somewhat more advanced way to
do that:
alias newfirefox='firefox -ProfileManager -no-remote'
I create new browser profiles regularly for testing things / clearing
settings. I suspect the issue more likely lies in some other aspect of
my system, although I haven't pinpointed what. My personal loathing of
Python is my current stumbling block in trying to add more debugging
output to that script.
(How anyone who grew up using vi's % could like a language with no
matched pairs is beyond me.)
Elijah
--
--
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/d/optout.
> Perhaps one last idea for debugging problems with textern; you
> might close Firefox, rename ``~/.mozilla`` out of the way, then
> restart Firefox to generate a new profile, then see if you can
> make textern work. I recently had to do this myself to solve a
> weird Firefox problem I encountered. I never knew what
> incorrect setting or corrupted file in my profile may have been
> responsible for the problem, but the new profile fixed it.
Thanks for your debugging ideas. I have a somewhat more advanced way to
do that:
alias newfirefox='firefox -ProfileManager -no-remote'
I create new browser profiles regularly for testing things / clearing
settings. I suspect the issue more likely lies in some other aspect of
my system, although I haven't pinpointed what. My personal loathing of
Python is my current stumbling block in trying to add more debugging
output to that script.
(How anyone who grew up using vi's % could like a language with no
matched pairs is beyond me.)
Elijah
--
--
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/d/optout.
Re: editing textareas in Firefox with vim
Perhaps one last idea for debugging problems with textern; you
might close Firefox, rename ``~/.mozilla`` out of the way, then
restart Firefox to generate a new profile, then see if you can
make textern work. I recently had to do this myself to solve a
weird Firefox problem I encountered. I never knew what
incorrect setting or corrupted file in my profile may have been
responsible for the problem, but the new profile fixed it.
Michael Henry
--
--
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/d/optout.
might close Firefox, rename ``~/.mozilla`` out of the way, then
restart Firefox to generate a new profile, then see if you can
make textern work. I recently had to do this myself to solve a
weird Firefox problem I encountered. I never knew what
incorrect setting or corrupted file in my profile may have been
responsible for the problem, but the new profile fixed it.
Michael Henry
--
--
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/d/optout.
Monday, August 27, 2018
Re: editing textareas in Firefox with vim
On 08/27/2018 12:37 AM, Eli the Bearded wrote:
>
> Michael Henry wrote:
>> I've been using "textern" for this, though I don't use it
>> heavily.
>
> This sounds great. Clear instructions, simple install. Nothing happens.
> I even watched stdout / stderr from Firefox, no warnings or errors or
> anything at all.
>
> Textern thinks something is happening, though. If I hit <ctrl-shift-D>
> a second time, it tells me the textarea is already being edited. But ps
> says otherwise. :-(
I'm not familiar with the innards of textern, so all I can
suggest are a few debugging ideas:
- Restart everything (Firefox, your login session) and test
again.
- Verify that you have Python 3.5+ installed on Linux as the
``python3`` executable in PATH.
- Test with gedit or another editor.
- Use a script in place of the editor, and within the script
write to a file to prove the script was launched.
You may well have already tried everything I listed above and
more. For me, it just works as advertised; hopefully you can
make it work in your environment, too.
Michael Henry
--
--
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/d/optout.
>
> Michael Henry wrote:
>> I've been using "textern" for this, though I don't use it
>> heavily.
>
> This sounds great. Clear instructions, simple install. Nothing happens.
> I even watched stdout / stderr from Firefox, no warnings or errors or
> anything at all.
>
> Textern thinks something is happening, though. If I hit <ctrl-shift-D>
> a second time, it tells me the textarea is already being edited. But ps
> says otherwise. :-(
I'm not familiar with the innards of textern, so all I can
suggest are a few debugging ideas:
- Restart everything (Firefox, your login session) and test
again.
- Verify that you have Python 3.5+ installed on Linux as the
``python3`` executable in PATH.
- Test with gedit or another editor.
- Use a script in place of the editor, and within the script
write to a file to prove the script was launched.
You may well have already tried everything I listed above and
more. For me, it just works as advertised; hopefully you can
make it work in your environment, too.
Michael Henry
--
--
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/d/optout.
Sunday, August 26, 2018
Re: editing textareas in Firefox with vim
Michael Henry wrote:
> I've been using "textern" for this, though I don't use it
> heavily. It's working for me on Ubuntu 16.04 with Firefox
> 61.0.1 and GVim 8.1.290. Here are the steps I followed to
> install:
>
> - Install URL:
> https://addons.mozilla.org/en-US/firefox/addon/textern/
This sounds great. Clear instructions, simple install. Nothing happens.
I even watched stdout / stderr from Firefox, no warnings or errors or
anything at all.
Textern thinks something is happening, though. If I hit <ctrl-shift-D>
a second time, it tells me the textarea is already being edited. But ps
says otherwise. :-(
Elijah
--
--
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/d/optout.
> I've been using "textern" for this, though I don't use it
> heavily. It's working for me on Ubuntu 16.04 with Firefox
> 61.0.1 and GVim 8.1.290. Here are the steps I followed to
> install:
>
> - Install URL:
> https://addons.mozilla.org/en-US/firefox/addon/textern/
This sounds great. Clear instructions, simple install. Nothing happens.
I even watched stdout / stderr from Firefox, no warnings or errors or
anything at all.
Textern thinks something is happening, though. If I hit <ctrl-shift-D>
a second time, it tells me the textarea is already being edited. But ps
says otherwise. :-(
Elijah
--
--
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/d/optout.
Re: How to begin using Vim
Once you have motivation, you will find your own path (but go slow!)
On Sat, Aug 25, 2018 at 11:33 AM meine <trialero@gmx.com> wrote:
> I suggest: learn how to switch to normal/insert mode. And that's all. When you're tired of something, or if you miss a feature, learn the solution.
excellent suggestion, and worked well for me learning Vim!
after the basics learnt from vimtutor, just start working with vim and
leave other editors to force yourself learning
you'll encounter situations where you ask yourself if there is a 'vim
solution' --- search for it and use it! (just use a browser and mouse,
be nice to yourself)
try to learn one, maybe two new vim commands a week
train your curiosity and skills eg. by cleaning up a pdf-to-text
converted file. this is a nice way to excersise find, substitute, funny
characters. take a file that you need to use for other purposes to get
some _drive_
//meine
--
--
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/d/optout.
--
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/d/optout.
Re: editing textareas in Firefox with vim
On 08/26/2018 02:02 AM, John Little wrote:
> On Saturday, August 25, 2018 at 11:25:19 PM UTC+12, Michael Henry wrote:
>> I've been using "textern" for this...
>
> Fantastic, I didn't know about this option. I'm typing this
> in gvim using the add-on.
>
>> ...
>> - Press Ctrl-Shift-E to bring up editor.
>
> It defaulted to Ctrl-Shift-D.
Thanks for pointing this out; my instructions were missing one
step, so I've updated my notes accordingly::
- Set Shortcut to ``Ctrl+Shift+E``.
I should probably have left that out of my email, since it's
just a personal preference. I'd gotten used to Ctrl-Shift-E
from a previous plugin, so I change the shortcut for
convenience. It also better matches the ``Ctrl-E`` shortcut
used by the "External Editor" Thunderbird plugin I use for
composing emails using Vim, making it easier for me to remember.
Michael Henry
--
--
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/d/optout.
> On Saturday, August 25, 2018 at 11:25:19 PM UTC+12, Michael Henry wrote:
>> I've been using "textern" for this...
>
> Fantastic, I didn't know about this option. I'm typing this
> in gvim using the add-on.
>
>> ...
>> - Press Ctrl-Shift-E to bring up editor.
>
> It defaulted to Ctrl-Shift-D.
Thanks for pointing this out; my instructions were missing one
step, so I've updated my notes accordingly::
- Set Shortcut to ``Ctrl+Shift+E``.
I should probably have left that out of my email, since it's
just a personal preference. I'd gotten used to Ctrl-Shift-E
from a previous plugin, so I change the shortcut for
convenience. It also better matches the ``Ctrl-E`` shortcut
used by the "External Editor" Thunderbird plugin I use for
composing emails using Vim, making it easier for me to remember.
Michael Henry
--
--
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/d/optout.
Saturday, August 25, 2018
Re: editing textareas in Firefox with vim
On Saturday, August 25, 2018 at 11:25:19 PM UTC+12, Michael Henry wrote:
> I've been using "textern" for this...
Fantastic, I didn't know about this option. I'm typing this in gvim using the add-on.
>...
> - Press Ctrl-Shift-E to bring up editor.
It defaulted to Ctrl-Shift-D.
Regards, John Little
--
--
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/d/optout.
> I've been using "textern" for this...
Fantastic, I didn't know about this option. I'm typing this in gvim using the add-on.
>...
> - Press Ctrl-Shift-E to bring up editor.
It defaulted to Ctrl-Shift-D.
Regards, John Little
--
--
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/d/optout.
Re: editing textareas in Firefox with vim
I've been using "textern" for this, though I don't use it
heavily. It's working for me on Ubuntu 16.04 with Firefox
61.0.1 and GVim 8.1.290. Here are the steps I followed to
install:
- Install URL:
https://addons.mozilla.org/en-US/firefox/addon/textern/
- References:
https://github.com/jlebon/textern
- Bring down native app::
cd ~/build
git clone --recurse-submodules https://github.com/jlebon/textern
cd textern
- Install native app::
make native-install USER=1
- In Firefox preferences for textern:
- Set "External Editor" to ``["gvim", "--nofork"]``.
- Press Ctrl-Shift-E to bring up editor.
Michael Henry
--
--
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/d/optout.
heavily. It's working for me on Ubuntu 16.04 with Firefox
61.0.1 and GVim 8.1.290. Here are the steps I followed to
install:
- Install URL:
https://addons.mozilla.org/en-US/firefox/addon/textern/
- References:
https://github.com/jlebon/textern
- Bring down native app::
cd ~/build
git clone --recurse-submodules https://github.com/jlebon/textern
cd textern
- Install native app::
make native-install USER=1
- In Firefox preferences for textern:
- Set "External Editor" to ``["gvim", "--nofork"]``.
- Press Ctrl-Shift-E to bring up editor.
Michael Henry
--
--
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/d/optout.
Re: How to begin using Vim
> I suggest: learn how to switch to normal/insert mode. And that's all. When you're tired of something, or if you miss a feature, learn the solution.
excellent suggestion, and worked well for me learning Vim!
after the basics learnt from vimtutor, just start working with vim and
leave other editors to force yourself learning
you'll encounter situations where you ask yourself if there is a 'vim
solution' --- search for it and use it! (just use a browser and mouse,
be nice to yourself)
try to learn one, maybe two new vim commands a week
train your curiosity and skills eg. by cleaning up a pdf-to-text
converted file. this is a nice way to excersise find, substitute, funny
characters. take a file that you need to use for other purposes to get
some _drive_
//meine
--
--
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/d/optout.
excellent suggestion, and worked well for me learning Vim!
after the basics learnt from vimtutor, just start working with vim and
leave other editors to force yourself learning
you'll encounter situations where you ask yourself if there is a 'vim
solution' --- search for it and use it! (just use a browser and mouse,
be nice to yourself)
try to learn one, maybe two new vim commands a week
train your curiosity and skills eg. by cleaning up a pdf-to-text
converted file. this is a nice way to excersise find, substitute, funny
characters. take a file that you need to use for other purposes to get
some _drive_
//meine
--
--
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/d/optout.
Friday, August 24, 2018
Re: editing textareas in Firefox with vim
> Have people here on vim-users found another method? Or have tips for
> getting one of these two to work?
>
We're on the same wavelength, Elijah
Sadly I do not have much to offer as my search started after Waterfox https://www.waterfoxproject.org/en-US/waterfox/new/ upgraded and broke It's All Text! https://github.com/docwhat/itsalltext :-(
I did try installing QuteBrowser https://www.qutebrowser.org/ but could not get it working with gvim as I use vim in the terminal though there is a thread https://www.reddit.com/r/qutebrowser/comments/780u6a/how_to_set_vim_as_qutebrowser_editor/ It allows an insert mode with an external editor like vim. YMMV
So right now, I just use "+p and "+y for accessing the system clipboard (+clipboard compiled) http://vim.wikia.com/wiki/Accessing_the_system_clipboard as I am tired of all the workarounds just to edit in vim.
Welcome to 2018!
Best,
tony
--
--
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/d/optout.
> getting one of these two to work?
>
We're on the same wavelength, Elijah
Sadly I do not have much to offer as my search started after Waterfox https://www.waterfoxproject.org/en-US/waterfox/new/ upgraded and broke It's All Text! https://github.com/docwhat/itsalltext :-(
I did try installing QuteBrowser https://www.qutebrowser.org/ but could not get it working with gvim as I use vim in the terminal though there is a thread https://www.reddit.com/r/qutebrowser/comments/780u6a/how_to_set_vim_as_qutebrowser_editor/ It allows an insert mode with an external editor like vim. YMMV
So right now, I just use "+p and "+y for accessing the system clipboard (+clipboard compiled) http://vim.wikia.com/wiki/Accessing_the_system_clipboard as I am tired of all the workarounds just to edit in vim.
Welcome to 2018!
Best,
tony
--
--
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/d/optout.
Re: How to begin using Vim
Le mercredi 8 août 2018 10:48:44 UTC+2, Tony Mechelynck a écrit :
> Bram's advice (on one of the PDFs on his home site) is to read the
> whole "user manual" at one sitting (or that's how I understood it).
> Mine (which is not The Word From On High but just my own point of
> view) is to go even more slowly but more steadily:
>
> 1. Subscribe to the vim_use list (but if you're here, you probably
> already did that). If you are on a Mac, subscribe also to the vim_mac
> list: these two are not about the same subjects. Later, but maybe not
> immediately, you may want to add the vim_dev list which is more
> technical than the other two.
> 2. Do all the Vimtutor lessons one after another — but not without
> breaks: take a break whenever you feel you've got enough for one
> sitting, and if possible before it gives you a headache. Then clear
> your head: play with your children if you have any, walk your dog (if
> you have any) around the block, take a walk in the park, do some
> shopping, whatever. But come back later.
> 3. Hit <F1> to start reading help, and after reading that very
> elementary help (you may skip fast over the table of contents, you'll
> come back to it later), do ":help helphelp" without the quotes but
> with <Enter> at the end (yes, "I tell you three times") which will
> tell you how to find your way around in Vim's help (and how to find
> what you want to know when you want to know it).
> 4. Read the rest of the help (including, but not limited to, the user
> manual), no more than one helpfile at a time (and probably less)
> whenever you find a help subject which is relevant to the kind of
> editing you are doing at that time; and once you've understood the
> part you need, use it immediately. Come back if the new commands you
> use don't do what you want, it just might mean that you skipped over
> one important sentence.
> 5. If you happen to have a free hour or so with nothing better to do,
> it is "not forbidden" to read any random part of the help which looks
> like it might be interesting (this is where you might want to come
> back to the table of contents); but don't forget to stop before you
> get bored, or as soon as some more urgent duty calls you, whichever
> comes first.
>
> Where I agree with Bram is that there are two errors to avoid: (a) not
> reading any of the help, and staying forever with a very few extremely
> elementary commands, maybe using Vim as one would Notepad; and (b)
> wanting to know everything at once, and never getting started on real
> editing. Vim's help is so complete — so encyclopædic — that it might
> take someone forever to know it all, especially since it is constantly
> being added to, whenever Vim gets a new feature. (Well, maybe Bram
> knows it all but he had a head start ;-) ). I won't pretend I know all
> about Vim — I don't — but I'm beginning to know a fair bit of it. I
> started in the way described above at some point between Vim 6.0 and
> 6.1 IIRC (at a time when Unicode support was new and tabpages didn't
> yet exist), and I still discover new things about Vim every day. Like
> Socrates, "the more I know, and the better I realize how little I
> know".
>
> That's all — oh, I almost forgot one more thing, and a very important
> one at that: Have fun!
>
>
> Best regards,
> Tony.
I suggest: learn how to switch to normal/insert mode. And that's all. When you're tired of something, or if you miss a feature, learn the solution.
For example, replace arrows by "hjkl". Then, if you dislike using <Esc>, learn to edit .vimrc to remap to something you like (<Caps Lock> or jj) etc. If you find "hjkl" movement too slow, use "w" and "b"...
If you use another editor (like Visual Studio Code, install vim plugin).
And yes, read and practice vimtutor at your own pace. Learn to use vim help instead of google or stack overflow after learning movement basics.
And keep believing one day you'll be faster than anyone else with a mouse ;)
--
--
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/d/optout.
> Bram's advice (on one of the PDFs on his home site) is to read the
> whole "user manual" at one sitting (or that's how I understood it).
> Mine (which is not The Word From On High but just my own point of
> view) is to go even more slowly but more steadily:
>
> 1. Subscribe to the vim_use list (but if you're here, you probably
> already did that). If you are on a Mac, subscribe also to the vim_mac
> list: these two are not about the same subjects. Later, but maybe not
> immediately, you may want to add the vim_dev list which is more
> technical than the other two.
> 2. Do all the Vimtutor lessons one after another — but not without
> breaks: take a break whenever you feel you've got enough for one
> sitting, and if possible before it gives you a headache. Then clear
> your head: play with your children if you have any, walk your dog (if
> you have any) around the block, take a walk in the park, do some
> shopping, whatever. But come back later.
> 3. Hit <F1> to start reading help, and after reading that very
> elementary help (you may skip fast over the table of contents, you'll
> come back to it later), do ":help helphelp" without the quotes but
> with <Enter> at the end (yes, "I tell you three times") which will
> tell you how to find your way around in Vim's help (and how to find
> what you want to know when you want to know it).
> 4. Read the rest of the help (including, but not limited to, the user
> manual), no more than one helpfile at a time (and probably less)
> whenever you find a help subject which is relevant to the kind of
> editing you are doing at that time; and once you've understood the
> part you need, use it immediately. Come back if the new commands you
> use don't do what you want, it just might mean that you skipped over
> one important sentence.
> 5. If you happen to have a free hour or so with nothing better to do,
> it is "not forbidden" to read any random part of the help which looks
> like it might be interesting (this is where you might want to come
> back to the table of contents); but don't forget to stop before you
> get bored, or as soon as some more urgent duty calls you, whichever
> comes first.
>
> Where I agree with Bram is that there are two errors to avoid: (a) not
> reading any of the help, and staying forever with a very few extremely
> elementary commands, maybe using Vim as one would Notepad; and (b)
> wanting to know everything at once, and never getting started on real
> editing. Vim's help is so complete — so encyclopædic — that it might
> take someone forever to know it all, especially since it is constantly
> being added to, whenever Vim gets a new feature. (Well, maybe Bram
> knows it all but he had a head start ;-) ). I won't pretend I know all
> about Vim — I don't — but I'm beginning to know a fair bit of it. I
> started in the way described above at some point between Vim 6.0 and
> 6.1 IIRC (at a time when Unicode support was new and tabpages didn't
> yet exist), and I still discover new things about Vim every day. Like
> Socrates, "the more I know, and the better I realize how little I
> know".
>
> That's all — oh, I almost forgot one more thing, and a very important
> one at that: Have fun!
>
>
> Best regards,
> Tony.
I suggest: learn how to switch to normal/insert mode. And that's all. When you're tired of something, or if you miss a feature, learn the solution.
For example, replace arrows by "hjkl". Then, if you dislike using <Esc>, learn to edit .vimrc to remap to something you like (<Caps Lock> or jj) etc. If you find "hjkl" movement too slow, use "w" and "b"...
If you use another editor (like Visual Studio Code, install vim plugin).
And yes, read and practice vimtutor at your own pace. Learn to use vim help instead of google or stack overflow after learning movement basics.
And keep believing one day you'll be faster than anyone else with a mouse ;)
--
--
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/d/optout.
editing textareas in Firefox with vim
This is really a Firefox issue, but I figure this list might have a
better set of people to tackle it than mozilla.support.firefox.
At one time, Firefox had a wide open (read: slow and security issue
prone) extensions API. At that time I could use an extension called
"It's All Text". With one very short shell script and one line of
config, I had Firefox configured to open an xterm running vim with the
contents connected to a textarea in the page just by pushing a button
in the webpage. The browser would update on every ":w". It worked
very well and reliably. Then the API was removed.
Now extensions do not have permissions to launch external programs. To
get this kind of functionality, websocket connections to a second
separately run program are used. I know of two implementations:
withExEditor / withExEditorHost
https://addons.mozilla.org/addon/withexeditor/
https://github.com/asamuzaK/withExEditorHost
I got this working shortly after the cutoff for the old API. It's
slightly different in that it also let you edit one line text inputs,
which seems a bit overkill, but okay. I have had a lot of trouble
keeping it working, however. At present withExEditor tells me it is
"connected" to the host, but the host version is incompatible. I'm
pretty sure I have both up to date, though.
GhostText / Ghost Text Vim
https://addons.mozilla.org/en-US/firefox/addon/ghosttext/
https://github.com/falstro/ghost-text-vim
I just learned of this one this week. The vim component is using gvim,
I'm not sure if that's important or just the preference of the author.
Anyway, I installed gvim for the test rather than my preferred
vim-in-xterm setup. It is apparently using some sort of client / server
interface with vim that aims for two way communication between the
textarea in the browser and the editor; updated when not in "insert
mode". As proof of concept, I did get it to work, but not well. On my
test page[*], it opened about twenty gvim windows, only one of which was
connected to the browser.
[*] https://qaz.wtf/ta/
It's about as simple HTML as the URL is short.
Have people here on vim-users found another method? Or have tips for
getting one of these two to work?
Elijah
--
--
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/d/optout.
better set of people to tackle it than mozilla.support.firefox.
At one time, Firefox had a wide open (read: slow and security issue
prone) extensions API. At that time I could use an extension called
"It's All Text". With one very short shell script and one line of
config, I had Firefox configured to open an xterm running vim with the
contents connected to a textarea in the page just by pushing a button
in the webpage. The browser would update on every ":w". It worked
very well and reliably. Then the API was removed.
Now extensions do not have permissions to launch external programs. To
get this kind of functionality, websocket connections to a second
separately run program are used. I know of two implementations:
withExEditor / withExEditorHost
https://addons.mozilla.org/addon/withexeditor/
https://github.com/asamuzaK/withExEditorHost
I got this working shortly after the cutoff for the old API. It's
slightly different in that it also let you edit one line text inputs,
which seems a bit overkill, but okay. I have had a lot of trouble
keeping it working, however. At present withExEditor tells me it is
"connected" to the host, but the host version is incompatible. I'm
pretty sure I have both up to date, though.
GhostText / Ghost Text Vim
https://addons.mozilla.org/en-US/firefox/addon/ghosttext/
https://github.com/falstro/ghost-text-vim
I just learned of this one this week. The vim component is using gvim,
I'm not sure if that's important or just the preference of the author.
Anyway, I installed gvim for the test rather than my preferred
vim-in-xterm setup. It is apparently using some sort of client / server
interface with vim that aims for two way communication between the
textarea in the browser and the editor; updated when not in "insert
mode". As proof of concept, I did get it to work, but not well. On my
test page[*], it opened about twenty gvim windows, only one of which was
connected to the browser.
[*] https://qaz.wtf/ta/
It's about as simple HTML as the URL is short.
Have people here on vim-users found another method? Or have tips for
getting one of these two to work?
Elijah
--
--
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/d/optout.
Thursday, August 23, 2018
Re: lua
rob wrote:
> I'm going to have to grok this.
>
> It will take a bit of time.
Hello:
Often one may use syntax-based folding, but it appears that
syntax/lua.vim doesn't support any folding (ie. :set fdm=syntax). You
might want to bring this up with lua's syntax maintainer (Marcus
Aurelius Farias -- you'll find his email address near the top of
syntax/lua.vim).
Regards,
Chip Campbell
--
--
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/d/optout.
> I'm going to have to grok this.
>
> It will take a bit of time.
Hello:
Often one may use syntax-based folding, but it appears that
syntax/lua.vim doesn't support any folding (ie. :set fdm=syntax). You
might want to bring this up with lua's syntax maintainer (Marcus
Aurelius Farias -- you'll find his email address near the top of
syntax/lua.vim).
Regards,
Chip Campbell
--
--
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/d/optout.
Re: Start terminal in a given directory
Hi,
2018/8/24 Fri 1:19:18 UTC+9 Lifepillar wrote:
> On 23/08/2018 15:28, Jason Franklin wrote:
> > The documentation under term_start() was recently updated
> > to include this option.
>
> So, I have likely searched the help in a version without your patch,
> which, has led me to believe that "cwd" was not supported.
>
> Thanks for letting me know!
> Life.
The "cwd" option was supported by Vim 8.0.0902.
If you use older than that version, you may want to try this:
new | lcd /path/to/dir | terminal ++curwin
Regards,
Ken Takata
--
--
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/d/optout.
2018/8/24 Fri 1:19:18 UTC+9 Lifepillar wrote:
> On 23/08/2018 15:28, Jason Franklin wrote:
> > The documentation under term_start() was recently updated
> > to include this option.
>
> So, I have likely searched the help in a version without your patch,
> which, has led me to believe that "cwd" was not supported.
>
> Thanks for letting me know!
> Life.
The "cwd" option was supported by Vim 8.0.0902.
If you use older than that version, you may want to try this:
new | lcd /path/to/dir | terminal ++curwin
Regards,
Ken Takata
--
--
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/d/optout.
Re: Start terminal in a given directory
On 23/08/2018 15:28, Jason Franklin wrote:
> The documentation under term_start() was recently updated
> to include this option.
So, I have likely searched the help in a version without your patch,
which, has led me to believe that "cwd" was not supported.
Thanks for letting me know!
Life.
--
--
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/d/optout.
> The documentation under term_start() was recently updated
> to include this option.
So, I have likely searched the help in a version without your patch,
which, has led me to believe that "cwd" was not supported.
Thanks for letting me know!
Life.
--
--
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/d/optout.
Re: Start terminal in a given directory
The documentation under term_start() was recently updated
to include this option. See my message below.
https://groups.google.com/forum/#!topic/vim_dev/WAFS5NrSrB4
--
--
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/d/optout.
to include this option. See my message below.
https://groups.google.com/forum/#!topic/vim_dev/WAFS5NrSrB4
--
--
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/d/optout.
Wednesday, August 22, 2018
Re: Start terminal in a given directory
On 22/08/2018 21:06, Bram Moolenaar wrote:
>
>> Currently, terminal jobs are always started in :pwd, AFAICT.
>> Is there a reason why the "cwd" option from job_start() is not inherited
>> by term_start()?
>
> I though this was in the todo list, but I can't find it now.
Ah, it's implemented already and documented under :h term_start()!
This works just fine:
:call term_start("ls", {"cwd": "/usr/local"})
Sorry for the noise: a consequence of an unfortunate combination of
(1) trying to use a wrong syntax, and (2) making a typo when searching
the help.
Life.
--
--
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/d/optout.
>
>> Currently, terminal jobs are always started in :pwd, AFAICT.
>> Is there a reason why the "cwd" option from job_start() is not inherited
>> by term_start()?
>
> I though this was in the todo list, but I can't find it now.
Ah, it's implemented already and documented under :h term_start()!
This works just fine:
:call term_start("ls", {"cwd": "/usr/local"})
Sorry for the noise: a consequence of an unfortunate combination of
(1) trying to use a wrong syntax, and (2) making a typo when searching
the help.
Life.
--
--
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/d/optout.
Re: Start terminal in a given directory
> Currently, terminal jobs are always started in :pwd, AFAICT.
> Is there a reason why the "cwd" option from job_start() is not inherited
> by term_start()?
I though this was in the todo list, but I can't find it now.
> What is the recommended way to start a terminal job in a given
> working directory?
Use a shell script?
--
"Beware of bugs in the above code; I have only proved
it correct, not tried it." -- Donald Knuth
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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/d/optout.
> Is there a reason why the "cwd" option from job_start() is not inherited
> by term_start()?
I though this was in the todo list, but I can't find it now.
> What is the recommended way to start a terminal job in a given
> working directory?
Use a shell script?
--
"Beware of bugs in the above code; I have only proved
it correct, not tried it." -- Donald Knuth
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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/d/optout.
Start terminal in a given directory
Currently, terminal jobs are always started in :pwd, AFAICT.
Is there a reason why the "cwd" option from job_start() is not inherited
by term_start()?
What is the recommended way to start a terminal job in a given
working directory?
Thanks,
Life.
--
--
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/d/optout.
Is there a reason why the "cwd" option from job_start() is not inherited
by term_start()?
What is the recommended way to start a terminal job in a given
working directory?
Thanks,
Life.
--
--
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/d/optout.
Re: FW: Understanding automatic vimrc sourcing
Forwarding to vim_use.
<oleksii.vilchanskyi@gmail.com> wrote:
On 8/22/18 7:59 AM, Christian Brabandt wrote:
>
> On Di, 21 Aug 2018, Oleksii Vilchanskyi wrote:
>
>> However, if I try wrapping it in a function, E127 occurs:
>>> set nocompatible
>>> filetype plugin indent on
>>> syntax on
>>>
>>> augroup vimrc
>>> autocmd!
>>> autocmd BufWritePost testvimrc call s:ReloadRC("testvimrc")
>>> augroup END
>>>
>>> function! s:ReloadRC(rc)
>>> exec 'source ' . a:rc | echom "Reloaded " . a:rc
>>> endfunction
>>
>> Whenever I do :w, I see:
>>> E127: Cannot redefine function <SNR>1_ReloadRC: It is in use
>
> Yes, what happens when you execute the function is, you reload your
> .vimrc which will redefine your function, while the function is
> executed. This is not allowed and causes the error message. Either do
> not use a function, or define your function inside e.g.
> ~/.vim/plugins/reload.vim or similar.
Thank you, the very day I sent the mail people on IRC showed me an
example of how this can look as a plugin (basically, copy all the
information regarding that into a plugin and put it under the guard),
just as you suggested. So, I ended up with this:
> if &compatible || exists('g:loaded_rc_auto_reload')
> finish
> else
> let g:loaded_rc_auto_reload = 1
> endif
>
> function! s:ReloadRC() abort
> execute 'source ' . $MYVIMRC
> redraw! | echomsg 'Reloaded ' . $MYVIMRC
> if has('gui_running')
> execute 'source ' . $MYGVIMRC
> redraw! | echomsg 'Reloaded ' . $MYGVIMRC
> endif
> endfunction
>
> augroup vimrc_auto_reload
> autocmd!
> autocmd BufWritePost $MYVIMRC call s:ReloadRC()
> autocmd BufWritePost $MYGVIMRC call s:ReloadRC()
> augroup EN
Although with the code above, I have noticed that whenever I run gvim,
neither vimrc nor gvimrc get sourced when I edit gvimrc, but both get
sourced if I edit vimrc. With terminal vim it's the same -- if I edit
vimrc, it gets sourced (and only it, since it's terminal vim), if I edit
gvimrc, nothing gets sourced. So, I suspect there is some issue with
> autocmd BufWritePost $MYGVIMRC call s:ReloadRC()
, looks like the condition is not getting triggered, or I don't
understand something.
--
--
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/d/optout.
<oleksii.vilchanskyi@gmail.com> wrote:
On 8/22/18 7:59 AM, Christian Brabandt wrote:
>
> On Di, 21 Aug 2018, Oleksii Vilchanskyi wrote:
>
>> However, if I try wrapping it in a function, E127 occurs:
>>> set nocompatible
>>> filetype plugin indent on
>>> syntax on
>>>
>>> augroup vimrc
>>> autocmd!
>>> autocmd BufWritePost testvimrc call s:ReloadRC("testvimrc")
>>> augroup END
>>>
>>> function! s:ReloadRC(rc)
>>> exec 'source ' . a:rc | echom "Reloaded " . a:rc
>>> endfunction
>>
>> Whenever I do :w, I see:
>>> E127: Cannot redefine function <SNR>1_ReloadRC: It is in use
>
> Yes, what happens when you execute the function is, you reload your
> .vimrc which will redefine your function, while the function is
> executed. This is not allowed and causes the error message. Either do
> not use a function, or define your function inside e.g.
> ~/.vim/plugins/reload.vim or similar.
Thank you, the very day I sent the mail people on IRC showed me an
example of how this can look as a plugin (basically, copy all the
information regarding that into a plugin and put it under the guard),
just as you suggested. So, I ended up with this:
> if &compatible || exists('g:loaded_rc_auto_reload')
> finish
> else
> let g:loaded_rc_auto_reload = 1
> endif
>
> function! s:ReloadRC() abort
> execute 'source ' . $MYVIMRC
> redraw! | echomsg 'Reloaded ' . $MYVIMRC
> if has('gui_running')
> execute 'source ' . $MYGVIMRC
> redraw! | echomsg 'Reloaded ' . $MYGVIMRC
> endif
> endfunction
>
> augroup vimrc_auto_reload
> autocmd!
> autocmd BufWritePost $MYVIMRC call s:ReloadRC()
> autocmd BufWritePost $MYGVIMRC call s:ReloadRC()
> augroup EN
Although with the code above, I have noticed that whenever I run gvim,
neither vimrc nor gvimrc get sourced when I edit gvimrc, but both get
sourced if I edit vimrc. With terminal vim it's the same -- if I edit
vimrc, it gets sourced (and only it, since it's terminal vim), if I edit
gvimrc, nothing gets sourced. So, I suspect there is some issue with
> autocmd BufWritePost $MYGVIMRC call s:ReloadRC()
, looks like the condition is not getting triggered, or I don't
understand something.
--
--
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/d/optout.
Tuesday, August 21, 2018
Re: Understanding automatic vimrc sourcing
On Di, 21 Aug 2018, Oleksii Vilchanskyi wrote:
> However, if I try wrapping it in a function, E127 occurs:
> > set nocompatible
> > filetype plugin indent on
> > syntax on
> >
> > augroup vimrc
> > autocmd!
> > autocmd BufWritePost testvimrc call s:ReloadRC("testvimrc")
> > augroup END
> >
> > function! s:ReloadRC(rc)
> > exec 'source ' . a:rc | echom "Reloaded " . a:rc
> > endfunction
>
> Whenever I do :w, I see:
> > E127: Cannot redefine function <SNR>1_ReloadRC: It is in use
Yes, what happens when you execute the function is, you reload your
.vimrc which will redefine your function, while the function is
executed. This is not allowed and causes the error message. Either do
not use a function, or define your function inside e.g.
~/.vim/plugins/reload.vim or similar.
Best,
Christian
--
Jeder Mensch ist einzigartig.
-- Benedetto Croce
--
--
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/d/optout.
> However, if I try wrapping it in a function, E127 occurs:
> > set nocompatible
> > filetype plugin indent on
> > syntax on
> >
> > augroup vimrc
> > autocmd!
> > autocmd BufWritePost testvimrc call s:ReloadRC("testvimrc")
> > augroup END
> >
> > function! s:ReloadRC(rc)
> > exec 'source ' . a:rc | echom "Reloaded " . a:rc
> > endfunction
>
> Whenever I do :w, I see:
> > E127: Cannot redefine function <SNR>1_ReloadRC: It is in use
Yes, what happens when you execute the function is, you reload your
.vimrc which will redefine your function, while the function is
executed. This is not allowed and causes the error message. Either do
not use a function, or define your function inside e.g.
~/.vim/plugins/reload.vim or similar.
Best,
Christian
--
Jeder Mensch ist einzigartig.
-- Benedetto Croce
--
--
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/d/optout.
Re: Understanding automatic vimrc sourcing
On Tue, Aug 21, 2018 at 12:22 PM, Oleksii Vilchanskyi
<oleksii.vilchanskyi@gmail.com> wrote:
> Hello,
>
> * What I want:
>
> Be able to do :w after editing $MYVIRC and have vim source the new
> version of config. Basically, just execute `source %` automatically.
>
> * What I have tried (all examples are launched with `vim -u testvimrc`):
>
> So, this works without any error, as supposed:
>> set nocompatible
>> filetype plugin indent on
>> syntax on
>>
>> augroup vimrc
>> autocmd!
>> autocmd BufWritePost testvimrc source testvimrc | echom "Reloaded"
>> augroup END
>
> However, if I try wrapping it in a function, E127 occurs:
>> set nocompatible
>> filetype plugin indent on
>> syntax on
>>
>> augroup vimrc
>> autocmd!
>> autocmd BufWritePost testvimrc call s:ReloadRC("testvimrc")
>> augroup END
>>
>> function! s:ReloadRC(rc)
>> exec 'source ' . a:rc | echom "Reloaded " . a:rc
>> endfunction
>
> Whenever I do :w, I see:
>> E127: Cannot redefine function <SNR>1_ReloadRC: It is in use
>
> But at the same time it doesn't abort and I see:
>> Reloaded testvimrc
> , so it looks like the new vimrc gets sourced regardless?..
>
> * My questions:
> 1) Why doesn't this work if wrapped into a function, but does, if
> written out directly?
> 2) Why, if an error occurs, I still see "Reloaded testvimrc"?
> 3) Does it have anything to do with reentrancy?
> 4) Is it possible to make it work through calling a function (since I
> would want to do the same for gvimrc (as well as vimrc), and don't want
> to have repetitive code, instead using a reusable function code)?
>
> Thank you in advance.
> --
> Regards,
> Oleksii Vilchanskyi
> PGP:0x8D3A0E046BDE941F2A53867CE3FD952D48C0B338
See :help E127
To replace a function with an existing name, you need an exclamation
mark after :function. This can be dangerous. IIUC, what happened to
you is that (without an exclamation) Vim gave the error message, did
not replace the function, and later executed the _old_ version of that
function. If you happened not to change that part of your vimrc, it
can be just what you want; but beware of shooting yourself in the
foot.
The approved way to reload your vimrc after changing it is to shutdown
Vim then restart it. Any other method is full of corner cases which
can be hard to debug.
Best regards,
Tony.
--
--
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/d/optout.
<oleksii.vilchanskyi@gmail.com> wrote:
> Hello,
>
> * What I want:
>
> Be able to do :w after editing $MYVIRC and have vim source the new
> version of config. Basically, just execute `source %` automatically.
>
> * What I have tried (all examples are launched with `vim -u testvimrc`):
>
> So, this works without any error, as supposed:
>> set nocompatible
>> filetype plugin indent on
>> syntax on
>>
>> augroup vimrc
>> autocmd!
>> autocmd BufWritePost testvimrc source testvimrc | echom "Reloaded"
>> augroup END
>
> However, if I try wrapping it in a function, E127 occurs:
>> set nocompatible
>> filetype plugin indent on
>> syntax on
>>
>> augroup vimrc
>> autocmd!
>> autocmd BufWritePost testvimrc call s:ReloadRC("testvimrc")
>> augroup END
>>
>> function! s:ReloadRC(rc)
>> exec 'source ' . a:rc | echom "Reloaded " . a:rc
>> endfunction
>
> Whenever I do :w, I see:
>> E127: Cannot redefine function <SNR>1_ReloadRC: It is in use
>
> But at the same time it doesn't abort and I see:
>> Reloaded testvimrc
> , so it looks like the new vimrc gets sourced regardless?..
>
> * My questions:
> 1) Why doesn't this work if wrapped into a function, but does, if
> written out directly?
> 2) Why, if an error occurs, I still see "Reloaded testvimrc"?
> 3) Does it have anything to do with reentrancy?
> 4) Is it possible to make it work through calling a function (since I
> would want to do the same for gvimrc (as well as vimrc), and don't want
> to have repetitive code, instead using a reusable function code)?
>
> Thank you in advance.
> --
> Regards,
> Oleksii Vilchanskyi
> PGP:0x8D3A0E046BDE941F2A53867CE3FD952D48C0B338
See :help E127
To replace a function with an existing name, you need an exclamation
mark after :function. This can be dangerous. IIUC, what happened to
you is that (without an exclamation) Vim gave the error message, did
not replace the function, and later executed the _old_ version of that
function. If you happened not to change that part of your vimrc, it
can be just what you want; but beware of shooting yourself in the
foot.
The approved way to reload your vimrc after changing it is to shutdown
Vim then restart it. Any other method is full of corner cases which
can be hard to debug.
Best regards,
Tony.
--
--
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/d/optout.
Re: lua
On Tuesday 21 August 2018 20:31,
rob <drrob100@fastmail.com> put forth the proposition:
> I'm going to have to grok this.
>
> It will take a bit of time.
>
> Thanks
>
> --rob
> On 08/21/2018 07:48 PM, Tony Mechelynck wrote:
> > On Wed, Aug 22, 2018 at 12:26 AM, rob <drrob106@gmail.com> wrote:
> > > Hi. I'm interested in getting code folding to work. I'm getting a message
> > > on Ubuntu 16.04 amd64 that lua has to be compiled in for a macro to work.
There are a few :help entries on folding, which can be found by e.g. :help
fold<tab> but :help foldmethod (or fdm) is probably the most useful.
I usually set it to 'marker' and add folds manually by putting {{{
}}} around whatever I want folded:
// {{{
<lines of code here>
// }}}
Then you can use a bind such as 'za' to open/close the fold. Change
'//' to whatever comment character(s) your code uses.
You can also add text after the fold lines - e.g.
// {{{ Function description
There are a bunch of different maps that work on folds - see :help
fold-commands.
Another useful one is foldenable (fen). If you set it in your
~/.vimrc it makes all folds closed when you open a file with folds
for the first time.
-Dave
> > > How do I get lua to be compiled into the make process?
> > >
> > > --rob
> > You can get folding without lua in any Normal, Big or Huge Vim; but
> > that doesn't help with your macro.
> >
> > For lua, you need, in addition to everything else needed to compile Vim:
> >
> > 1) lua installed on your system _with_ the corresponding "development"
> > packages (the latter are necessary to compile a program which uses
> > lua). I'm not sure how exactly to get these on Ubuntu (I'm on openSUSE
> > Linux) but you should be able to query your package manager about
> > packages whose names start with lua and make sure that at least the
> > lua library package and the lua development package are installed.
> >
> > 2) then you need to configure and compile Vim with lua. See the
> > following for details:
> > https://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial
> > http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
> > These two may seem a little complex but I tried to make them apply to
> > any use case. (I'm not sure I succeeded but at least I tried.)
> >
> > The relevant configure parameter is --enable-luainterp (e.g. export
> > CONF_OPT_LUA='--enable-luainterp') and I recommend to run "make
> > reconfig" to reconfigure and recompile after any change in your
> > configure settings (which I define by means of environment variables
> > so Make will get them right even if, as it sometimes happens, it
> > decides to run configure again before an ordinary compile).
> >
> > Before running "make install", run src/vim --version to see if the Vim
> > you just compiled has +lua (and everything else that you want it to
> > have). If it doesn't then it is time to ask yourself what went wrong.
> >
> >
> > Best regards,
> > Tony.
--
I forgot to mention an important fact in the 1.3.67 announcement. In order to
get a fully working kernel, you have to follow the steps below:
- Walk around your computer widdershins 3 times, chanting "Linus is
overworked, and he makes lousy patches, but we love him anyway". Get
your spuouse to do this too for extra effect. Children are optional.
- Apply the patch included in this mail
- Call your system "Super-67", and don't forget to unapply the patch
before you later applying the official 1.3.68 patch.
- reboot
-- Linus Torvalds, announcing another kernel patch
.--. oo
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'
--
--
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/d/optout.
rob <drrob100@fastmail.com> put forth the proposition:
> I'm going to have to grok this.
>
> It will take a bit of time.
>
> Thanks
>
> --rob
> On 08/21/2018 07:48 PM, Tony Mechelynck wrote:
> > On Wed, Aug 22, 2018 at 12:26 AM, rob <drrob106@gmail.com> wrote:
> > > Hi. I'm interested in getting code folding to work. I'm getting a message
> > > on Ubuntu 16.04 amd64 that lua has to be compiled in for a macro to work.
There are a few :help entries on folding, which can be found by e.g. :help
fold<tab> but :help foldmethod (or fdm) is probably the most useful.
I usually set it to 'marker' and add folds manually by putting {{{
}}} around whatever I want folded:
// {{{
<lines of code here>
// }}}
Then you can use a bind such as 'za' to open/close the fold. Change
'//' to whatever comment character(s) your code uses.
You can also add text after the fold lines - e.g.
// {{{ Function description
There are a bunch of different maps that work on folds - see :help
fold-commands.
Another useful one is foldenable (fen). If you set it in your
~/.vimrc it makes all folds closed when you open a file with folds
for the first time.
-Dave
> > > How do I get lua to be compiled into the make process?
> > >
> > > --rob
> > You can get folding without lua in any Normal, Big or Huge Vim; but
> > that doesn't help with your macro.
> >
> > For lua, you need, in addition to everything else needed to compile Vim:
> >
> > 1) lua installed on your system _with_ the corresponding "development"
> > packages (the latter are necessary to compile a program which uses
> > lua). I'm not sure how exactly to get these on Ubuntu (I'm on openSUSE
> > Linux) but you should be able to query your package manager about
> > packages whose names start with lua and make sure that at least the
> > lua library package and the lua development package are installed.
> >
> > 2) then you need to configure and compile Vim with lua. See the
> > following for details:
> > https://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial
> > http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
> > These two may seem a little complex but I tried to make them apply to
> > any use case. (I'm not sure I succeeded but at least I tried.)
> >
> > The relevant configure parameter is --enable-luainterp (e.g. export
> > CONF_OPT_LUA='--enable-luainterp') and I recommend to run "make
> > reconfig" to reconfigure and recompile after any change in your
> > configure settings (which I define by means of environment variables
> > so Make will get them right even if, as it sometimes happens, it
> > decides to run configure again before an ordinary compile).
> >
> > Before running "make install", run src/vim --version to see if the Vim
> > you just compiled has +lua (and everything else that you want it to
> > have). If it doesn't then it is time to ask yourself what went wrong.
> >
> >
> > Best regards,
> > Tony.
--
I forgot to mention an important fact in the 1.3.67 announcement. In order to
get a fully working kernel, you have to follow the steps below:
- Walk around your computer widdershins 3 times, chanting "Linus is
overworked, and he makes lousy patches, but we love him anyway". Get
your spuouse to do this too for extra effect. Children are optional.
- Apply the patch included in this mail
- Call your system "Super-67", and don't forget to unapply the patch
before you later applying the official 1.3.68 patch.
- reboot
-- Linus Torvalds, announcing another kernel patch
.--. oo
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'
--
--
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/d/optout.
Re: lua
I'm going to have to grok this.
It will take a bit of time.
Thanks
--rob
On 08/21/2018 07:48 PM, Tony Mechelynck wrote:
> On Wed, Aug 22, 2018 at 12:26 AM, rob <drrob106@gmail.com> wrote:
>> Hi. I'm interested in getting code folding to work. I'm getting a message
>> on Ubuntu 16.04 amd64 that lua has to be compiled in for a macro to work.
>>
>> How do I get lua to be compiled into the make process?
>>
>> --rob
> You can get folding without lua in any Normal, Big or Huge Vim; but
> that doesn't help with your macro.
>
> For lua, you need, in addition to everything else needed to compile Vim:
>
> 1) lua installed on your system _with_ the corresponding "development"
> packages (the latter are necessary to compile a program which uses
> lua). I'm not sure how exactly to get these on Ubuntu (I'm on openSUSE
> Linux) but you should be able to query your package manager about
> packages whose names start with lua and make sure that at least the
> lua library package and the lua development package are installed.
>
> 2) then you need to configure and compile Vim with lua. See the
> following for details:
> https://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial
> http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
> These two may seem a little complex but I tried to make them apply to
> any use case. (I'm not sure I succeeded but at least I tried.)
>
> The relevant configure parameter is --enable-luainterp (e.g. export
> CONF_OPT_LUA='--enable-luainterp') and I recommend to run "make
> reconfig" to reconfigure and recompile after any change in your
> configure settings (which I define by means of environment variables
> so Make will get them right even if, as it sometimes happens, it
> decides to run configure again before an ordinary compile).
>
> Before running "make install", run src/vim --version to see if the Vim
> you just compiled has +lua (and everything else that you want it to
> have). If it doesn't then it is time to ask yourself what went wrong.
>
>
> Best regards,
> Tony.
>
--
--
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/d/optout.
It will take a bit of time.
Thanks
--rob
On 08/21/2018 07:48 PM, Tony Mechelynck wrote:
> On Wed, Aug 22, 2018 at 12:26 AM, rob <drrob106@gmail.com> wrote:
>> Hi. I'm interested in getting code folding to work. I'm getting a message
>> on Ubuntu 16.04 amd64 that lua has to be compiled in for a macro to work.
>>
>> How do I get lua to be compiled into the make process?
>>
>> --rob
> You can get folding without lua in any Normal, Big or Huge Vim; but
> that doesn't help with your macro.
>
> For lua, you need, in addition to everything else needed to compile Vim:
>
> 1) lua installed on your system _with_ the corresponding "development"
> packages (the latter are necessary to compile a program which uses
> lua). I'm not sure how exactly to get these on Ubuntu (I'm on openSUSE
> Linux) but you should be able to query your package manager about
> packages whose names start with lua and make sure that at least the
> lua library package and the lua development package are installed.
>
> 2) then you need to configure and compile Vim with lua. See the
> following for details:
> https://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial
> http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
> These two may seem a little complex but I tried to make them apply to
> any use case. (I'm not sure I succeeded but at least I tried.)
>
> The relevant configure parameter is --enable-luainterp (e.g. export
> CONF_OPT_LUA='--enable-luainterp') and I recommend to run "make
> reconfig" to reconfigure and recompile after any change in your
> configure settings (which I define by means of environment variables
> so Make will get them right even if, as it sometimes happens, it
> decides to run configure again before an ordinary compile).
>
> Before running "make install", run src/vim --version to see if the Vim
> you just compiled has +lua (and everything else that you want it to
> have). If it doesn't then it is time to ask yourself what went wrong.
>
>
> Best regards,
> Tony.
>
--
--
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/d/optout.
Re: lua
On Wed, Aug 22, 2018 at 12:26 AM, rob <drrob106@gmail.com> wrote:
> Hi. I'm interested in getting code folding to work. I'm getting a message
> on Ubuntu 16.04 amd64 that lua has to be compiled in for a macro to work.
>
> How do I get lua to be compiled into the make process?
>
> --rob
You can get folding without lua in any Normal, Big or Huge Vim; but
that doesn't help with your macro.
For lua, you need, in addition to everything else needed to compile Vim:
1) lua installed on your system _with_ the corresponding "development"
packages (the latter are necessary to compile a program which uses
lua). I'm not sure how exactly to get these on Ubuntu (I'm on openSUSE
Linux) but you should be able to query your package manager about
packages whose names start with lua and make sure that at least the
lua library package and the lua development package are installed.
2) then you need to configure and compile Vim with lua. See the
following for details:
https://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
These two may seem a little complex but I tried to make them apply to
any use case. (I'm not sure I succeeded but at least I tried.)
The relevant configure parameter is --enable-luainterp (e.g. export
CONF_OPT_LUA='--enable-luainterp') and I recommend to run "make
reconfig" to reconfigure and recompile after any change in your
configure settings (which I define by means of environment variables
so Make will get them right even if, as it sometimes happens, it
decides to run configure again before an ordinary compile).
Before running "make install", run src/vim --version to see if the Vim
you just compiled has +lua (and everything else that you want it to
have). If it doesn't then it is time to ask yourself what went wrong.
Best regards,
Tony.
--
--
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/d/optout.
> Hi. I'm interested in getting code folding to work. I'm getting a message
> on Ubuntu 16.04 amd64 that lua has to be compiled in for a macro to work.
>
> How do I get lua to be compiled into the make process?
>
> --rob
You can get folding without lua in any Normal, Big or Huge Vim; but
that doesn't help with your macro.
For lua, you need, in addition to everything else needed to compile Vim:
1) lua installed on your system _with_ the corresponding "development"
packages (the latter are necessary to compile a program which uses
lua). I'm not sure how exactly to get these on Ubuntu (I'm on openSUSE
Linux) but you should be able to query your package manager about
packages whose names start with lua and make sure that at least the
lua library package and the lua development package are installed.
2) then you need to configure and compile Vim with lua. See the
following for details:
https://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
These two may seem a little complex but I tried to make them apply to
any use case. (I'm not sure I succeeded but at least I tried.)
The relevant configure parameter is --enable-luainterp (e.g. export
CONF_OPT_LUA='--enable-luainterp') and I recommend to run "make
reconfig" to reconfigure and recompile after any change in your
configure settings (which I define by means of environment variables
so Make will get them right even if, as it sometimes happens, it
decides to run configure again before an ordinary compile).
Before running "make install", run src/vim --version to see if the Vim
you just compiled has +lua (and everything else that you want it to
have). If it doesn't then it is time to ask yourself what went wrong.
Best regards,
Tony.
--
--
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/d/optout.
lua
Hi. I'm interested in getting code folding to work. I'm getting a
message on Ubuntu 16.04 amd64 that lua has to be compiled in for a macro
to work.
How do I get lua to be compiled into the make process?
--rob
--
--
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/d/optout.
message on Ubuntu 16.04 amd64 that lua has to be compiled in for a macro
to work.
How do I get lua to be compiled into the make process?
--rob
--
--
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/d/optout.
Re: I tried a Vim without frills, and it taught me I've been living in luxury
On Tue, Aug 21, 2018 at 4:36 PM, Tim Chase <vim@tim.thechases.com> wrote:
[...]
> Indeed, I often work on FreeBSD & OpenBSD boxes where nvi is the
> default vi instead of vim. I find myself missing a couple things
> like text objects, folding, multiple windows, and expression
> evaluation (whether as a register or as a sub-replace-special) the
> most. Syntax highlighting can be nice, but I can get along without
> it.
IIUC, expression evaluation (and the variables, functions, and
conditional branches and loops that go with it) is the one feature
which makes Vim script language Turing-complete, and that makes a hell
of a huge difference when writing one's vimrc. Other features are
great to have too, of course.
Oh, sure I could get along without syntax highlighting, but given the
choice I would take it. Not only when reading the help as I already
mentioned, but when writing HTML i've oftentimes got my attention
alerted by "weird" highlighting to some typo I'd made.
Best regards,
Tony.
--
--
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/d/optout.
[...]
> Indeed, I often work on FreeBSD & OpenBSD boxes where nvi is the
> default vi instead of vim. I find myself missing a couple things
> like text objects, folding, multiple windows, and expression
> evaluation (whether as a register or as a sub-replace-special) the
> most. Syntax highlighting can be nice, but I can get along without
> it.
IIUC, expression evaluation (and the variables, functions, and
conditional branches and loops that go with it) is the one feature
which makes Vim script language Turing-complete, and that makes a hell
of a huge difference when writing one's vimrc. Other features are
great to have too, of course.
Oh, sure I could get along without syntax highlighting, but given the
choice I would take it. Not only when reading the help as I already
mentioned, but when writing HTML i've oftentimes got my attention
alerted by "weird" highlighting to some typo I'd made.
Best regards,
Tony.
--
--
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/d/optout.
Re: I tried a Vim without frills, and it taught me I've been living in luxury
On 2018-08-21 03:58, Tony Mechelynck wrote:
> Just to see what it meant, I tried a Small Vim (instead of my usual
> Big) with Motif GUI (instead of my usual GTK2), and it taught me
> I've been living in luxury.
Indeed, I often work on FreeBSD & OpenBSD boxes where nvi is the
default vi instead of vim. I find myself missing a couple things
like text objects, folding, multiple windows, and expression
evaluation (whether as a register or as a sub-replace-special) the
most. Syntax highlighting can be nice, but I can get along without
it.
-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/d/optout.
> Just to see what it meant, I tried a Small Vim (instead of my usual
> Big) with Motif GUI (instead of my usual GTK2), and it taught me
> I've been living in luxury.
Indeed, I often work on FreeBSD & OpenBSD boxes where nvi is the
default vi instead of vim. I find myself missing a couple things
like text objects, folding, multiple windows, and expression
evaluation (whether as a register or as a sub-replace-special) the
most. Syntax highlighting can be nice, but I can get along without
it.
-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/d/optout.
Subscribe to:
Posts (Atom)