I'm using the Vim Airline plugin which has a nice facility for
displaying whether a file has mixed indents and/or trailing spaces
based on setting a variable:
let g:airline#extensions#whitespace#checks = [ 'indent', 'trailing' ]
However, I'd like to set that to only show mixed indenting problems
when editing Markdown files (that have the extension .md).
How can I configure this in my .vimrc so that it accommodates this...
I often have markdown and, say, Python files open at the same time (in
the latter I want both options, of course)...
c
--
Chris Lott <chris@chrislott.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/groups/opt_out.
Friday, February 28, 2014
Re: Cannot edit remote file via ftp
Lucas Sanner wrote:
> Ok, this is the debugging trace file (without passwords).
>
> The steps I did are:
>
> - Connect to my remote server via ftp
> - Log in
> - Attempt to enter a directory by pressing Enter
> - Attempt to edit a file by pressing Enter
>
> That's all.
> I hope you will be able to detect what's wrong.
>
>
> Thanks
>
Hello!
It seems that you typed:
vim ftp://datamigo@192.168.0.46/myweb/
but there is no directory or file named "myweb" on that system; there is
a directory named joomlight-3.x and a file named test.php, but its under
the home directory, not myweb.
You then selected joomlight-3.x with a <cr>; this resulted in netrw
trying ftp with:
vim ftp://datamigo@192.168.0.46/myweb/joomlight-3.x/
Of course, since there's no directory called "myweb", there's no
directory called "myweb/joomlight-3.x" either.
You then selected test.php with a <cr>; this resulted in netrw trying
ftp with:
vim ftp://datamigo@192.168.0.46/myweb/test.php
Again, there is no myweb directory, and so there's no myweb/test.php file.
However, netrw should issue a message about this problem, so please try
v151f which does so.
(http://www.drchip.org/astronaut/vim/index.html#NETRW)
Regards,
C 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/groups/opt_out.
> Ok, this is the debugging trace file (without passwords).
>
> The steps I did are:
>
> - Connect to my remote server via ftp
> - Log in
> - Attempt to enter a directory by pressing Enter
> - Attempt to edit a file by pressing Enter
>
> That's all.
> I hope you will be able to detect what's wrong.
>
>
> Thanks
>
Hello!
It seems that you typed:
vim ftp://datamigo@192.168.0.46/myweb/
but there is no directory or file named "myweb" on that system; there is
a directory named joomlight-3.x and a file named test.php, but its under
the home directory, not myweb.
You then selected joomlight-3.x with a <cr>; this resulted in netrw
trying ftp with:
vim ftp://datamigo@192.168.0.46/myweb/joomlight-3.x/
Of course, since there's no directory called "myweb", there's no
directory called "myweb/joomlight-3.x" either.
You then selected test.php with a <cr>; this resulted in netrw trying
ftp with:
vim ftp://datamigo@192.168.0.46/myweb/test.php
Again, there is no myweb directory, and so there's no myweb/test.php file.
However, netrw should issue a message about this problem, so please try
v151f which does so.
(http://www.drchip.org/astronaut/vim/index.html#NETRW)
Regards,
C 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/groups/opt_out.
Re: Dumb question: variables in the statusline
On Feb 28, 2014, at 7:58 AM, Nikolay Pavlov <zyx.vim@gmail.com> wrote:
Don't use :execute and incorrect escaping. The following should work:
let &l:statusline='%!FunctionFromWhichIAmTryingToGetAStatusline('.string(a:1).')'
That does seem to have worked. Thanks!
Ben
--
b
Sent from my iPhone
Sent from my iPhone
Re: Dumb question: variables in the statusline
On Feb 27, 2014 9:55 PM, "Benjamin Klein" <ben@silver-chalice.com> wrote:
>
> On Feb 27, 2014, at 11:42 AM, Charles Campbell <Charles.E.Campbell@nasa.gov> wrote:
>
> > * Could you give us the new exe line you're using to set the statusline?
>
> Right now it's
>
> execute "setlocal statusline=" . status
>
> where `status` is the string returned by the function.
>
> > * What does :echo &l:stl show ?
>
> The function which is supposed to get the status line begins the string with the a:1, and then appends %= and the rest of the line to that. &l:stl, after I get the error, is the a:1 (message) passed to the function. Everything from that =% onward is being left out.
>
> > * You're passing a:1 to exe; perhaps it should be escaped, too: ... fnameescape(a:1) ...
>
> A good idea -- thanks. (It hasn't seemed to affect this situation though, sadly.)
Don't use :execute and incorrect escaping. The following should work:
let &l:statusline='%!FunctionFromWhichIAmTryingToGetAStatusline('.string(a:1).')'
Function fnameescape() has other purpose and it must not be used to escape strings for statusline.
I am not sure how this would deal with some special characters though: those below 0x20 and %. They should not cause trouble AFAIK, but I may be wrong.
>
> Ben
>
> --
> b
>
> Sent from my iPhone
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Thursday, February 27, 2014
Re: fixing mistakes in the command line
hi, thanks everyone :) I'll look into your suggestions
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Sum plugin not support comma in digits
hi Dr. chip:
-- I've been using your Sum plugin and it helps from time to time.
today I found that it does not support the comma as displayed in my bank account - give me wrong huge value (I hope the number become true though..)
currently I work around it by removing the comma manually and re-Sum.
do you think it can be supported?
thanks.
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: fixing mistakes in the command line
On 14:28 Wed 26 Feb , Bee wrote:
> On Wednesday, February 26, 2014 2:57:18 AM UTC-8, Matteo Cavalleri wrote:
> > Il giorno mercoledì 26 febbraio 2014 11:49:20 UTC+1, Matteo Cavalleri ha scritto:
> >> I discovered just now abbreviations works also in command line mode, so I suppose my problem is solved :) thanks anyway and sorry for the noise and I discovered just now again they also mess with my search patterns... :(
>
> Define an abbreviation using:
> :ia
> :help :ia
> Then it will only be triggered in insert mode and not command line mode.
Hi,
You can use command aliases for that, check out my plugin:
http://www.vim.org/scripts/script.php?script_id=4250
Best regards,
Marcin
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> On Wednesday, February 26, 2014 2:57:18 AM UTC-8, Matteo Cavalleri wrote:
> > Il giorno mercoledì 26 febbraio 2014 11:49:20 UTC+1, Matteo Cavalleri ha scritto:
> >> I discovered just now abbreviations works also in command line mode, so I suppose my problem is solved :) thanks anyway and sorry for the noise and I discovered just now again they also mess with my search patterns... :(
>
> Define an abbreviation using:
> :ia
> :help :ia
> Then it will only be triggered in insert mode and not command line mode.
Hi,
You can use command aliases for that, check out my plugin:
http://www.vim.org/scripts/script.php?script_id=4250
Best regards,
Marcin
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Vim+mzscheme installer
Vim is not working with the new Racket 6.0. Therefore, I could not ./configure and make VIM+mzscheme. I would like to know whether a member of this group was able to upgrade if_mzsch.c, so it can handle Racket 6.0. The new Racket 6.0 has many nice features that I would like to use.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: README.md to a doc?
2014-02-27 03:45, Tim Johnson skrev:
> * Tim Johnson <tim@akwebsoft.com> [140226 16:44]:
>> * Adnan Zafar <adnanjzafar@gmail.com> [140226 16:32]:
>>> Hi Tim,
>>>
>>> Just leave the file as it is or delete it. Plugin authors provide
>>> files like that to provide information on GitHub pages for example. If
>>> you're installing the plugin using Pathogen or Vundle or one of the
>>> others, everything should be set up to just ignore it. If you're
>>> installing manually, you can just delete the file.
>>
>> I was wondering if there were a built-in way to make a
>> doc-compatible .txt file out of it. It sounds like there isn't.
>>
>> I wouldn't mind spending a little time "marking up" a README.md to
>> make it doc-compatible. I think that there are adequate
>> instructions in :h helptag
> Turns out that in a general case a README.md file can be
> converted to a doc .txt file in just a few minutes.
If you are writing the file yourself it can be marked up as
*both* Markdown and Vim halp without looking *too* strange when
rendered as either. You can see an example here:
<https://github.com/bpj/vim-ToggleKeymap/blob/master/doc/ToggleKeymap.txt>
It's a bit on the extreme side, and I'm afraid it looks just a
little more strange rendered as Vim help than as Markdown!
(Don't look at the code -- it's my first attempt ever at writing
a plugin and I'm sure I've overlooked a ton of things --
including making a SwEnglish translation error when naming it!)
I've been thinking of writing a Pandoc filter -- not knowing
Haskell and not being prepared to tackle the learning curve
writing a filter in Perl is at least feasible to me --
which produces Vim help format when using plain text as target
format. I might still do that -- especially since I'm apparently
not the only one who would find it useful!
It would just do three to five things:
1. Enclose the text of headers which don't contain any whitespace
in asterisks, i.e. `# foo-bar` becomes `# *foo-bar*` with a
vimhelp
tag target, while `# foo bar` remains unchanged because of
the period.
2. Turn links like `[replace virtual characters](URL "vim:gr")`
(i.e. where the title string matches `/^vim:(\S+)$/`) into
`replace virtual characters (|gr|)`.
3. Make sure the URLs of *other* non-local links actually show
up in the output.
4. Maybe recognise links to <http://vimdoc.sourceforge.net>
and do the Right Think with them.
5. Maybe enclosing emphasized text in curlies.
(BIG maybe, but I abhor semantic loss!)
However the file in the link above would become fine Vim help
only with `$ pandoc -w plain ToggleKeymap.txt` if only I
change headers like `:SetKeymap` into `\*:SetKeymap\*`,
but 2. and/or 4. might still be desirable.
/bpj
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> * Tim Johnson <tim@akwebsoft.com> [140226 16:44]:
>> * Adnan Zafar <adnanjzafar@gmail.com> [140226 16:32]:
>>> Hi Tim,
>>>
>>> Just leave the file as it is or delete it. Plugin authors provide
>>> files like that to provide information on GitHub pages for example. If
>>> you're installing the plugin using Pathogen or Vundle or one of the
>>> others, everything should be set up to just ignore it. If you're
>>> installing manually, you can just delete the file.
>>
>> I was wondering if there were a built-in way to make a
>> doc-compatible .txt file out of it. It sounds like there isn't.
>>
>> I wouldn't mind spending a little time "marking up" a README.md to
>> make it doc-compatible. I think that there are adequate
>> instructions in :h helptag
> Turns out that in a general case a README.md file can be
> converted to a doc .txt file in just a few minutes.
If you are writing the file yourself it can be marked up as
*both* Markdown and Vim halp without looking *too* strange when
rendered as either. You can see an example here:
<https://github.com/bpj/vim-ToggleKeymap/blob/master/doc/ToggleKeymap.txt>
It's a bit on the extreme side, and I'm afraid it looks just a
little more strange rendered as Vim help than as Markdown!
(Don't look at the code -- it's my first attempt ever at writing
a plugin and I'm sure I've overlooked a ton of things --
including making a SwEnglish translation error when naming it!)
I've been thinking of writing a Pandoc filter -- not knowing
Haskell and not being prepared to tackle the learning curve
writing a filter in Perl is at least feasible to me --
which produces Vim help format when using plain text as target
format. I might still do that -- especially since I'm apparently
not the only one who would find it useful!
It would just do three to five things:
1. Enclose the text of headers which don't contain any whitespace
in asterisks, i.e. `# foo-bar` becomes `# *foo-bar*` with a
vimhelp
tag target, while `# foo bar` remains unchanged because of
the period.
2. Turn links like `[replace virtual characters](URL "vim:gr")`
(i.e. where the title string matches `/^vim:(\S+)$/`) into
`replace virtual characters (|gr|)`.
3. Make sure the URLs of *other* non-local links actually show
up in the output.
4. Maybe recognise links to <http://vimdoc.sourceforge.net>
and do the Right Think with them.
5. Maybe enclosing emphasized text in curlies.
(BIG maybe, but I abhor semantic loss!)
However the file in the link above would become fine Vim help
only with `$ pandoc -w plain ToggleKeymap.txt` if only I
change headers like `:SetKeymap` into `\*:SetKeymap\*`,
but 2. and/or 4. might still be desirable.
/bpj
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Dumb question: variables in the statusline
On Feb 27, 2014, at 11:42 AM, Charles Campbell <Charles.E.Campbell@nasa.gov> wrote:
> * Could you give us the new exe line you're using to set the statusline?
Right now it's
execute "setlocal statusline=" . status
where `status` is the string returned by the function.
> * What does :echo &l:stl show ?
The function which is supposed to get the status line begins the string with the a:1, and then appends %= and the rest of the line to that. &l:stl, after I get the error, is the a:1 (message) passed to the function. Everything from that =% onward is being left out.
> * You're passing a:1 to exe; perhaps it should be escaped, too: ... fnameescape(a:1) ...
A good idea -- thanks. (It hasn't seemed to affect this situation though, sadly.)
Ben
--
b
Sent from my iPhone
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> * Could you give us the new exe line you're using to set the statusline?
Right now it's
execute "setlocal statusline=" . status
where `status` is the string returned by the function.
> * What does :echo &l:stl show ?
The function which is supposed to get the status line begins the string with the a:1, and then appends %= and the rest of the line to that. &l:stl, after I get the error, is the a:1 (message) passed to the function. Everything from that =% onward is being left out.
> * You're passing a:1 to exe; perhaps it should be escaped, too: ... fnameescape(a:1) ...
A good idea -- thanks. (It hasn't seemed to affect this situation though, sadly.)
Ben
--
b
Sent from my iPhone
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Dumb question: variables in the statusline
Benjamin Klein wrote:
> Huh. Trying that, with a statusline containing "%=", gives me
>
> E518: Unknown option: %=
>
> That's setting the statusline with execute.
>
>
* Could you give us the new exe line you're using to set the statusline?
* What does :echo &l:stl show ?
* You're passing a:1 to exe; perhaps it should be escaped, too: ...
fnameescape(a:1) ...
Regards,
C 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/groups/opt_out.
> Huh. Trying that, with a statusline containing "%=", gives me
>
> E518: Unknown option: %=
>
> That's setting the statusline with execute.
>
>
* Could you give us the new exe line you're using to set the statusline?
* What does :echo &l:stl show ?
* You're passing a:1 to exe; perhaps it should be escaped, too: ...
fnameescape(a:1) ...
Regards,
C 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/groups/opt_out.
Re: problems (and bugs) with netrw
Matteo Cavalleri wrote:
another problem: let's say I do :e app/etc/local.xml and then open
netrw. I move over ../ and press <cr> to go back up one level in the
hierarchy. the cursor move on row 0. is it possibile to let it stay on
the first line of the file listings? i.e. after the netrw header. If i
disable the header with "let g:netrw_banner=0" there's one empty line on
top of the buffer, so a movement is still needed. It also happens when i
open a file with <cr>. if I open netrw again the cursor is no longer on
the file i opened, but on the first line. thanks in advance!
Hello!
With v151e of netrw, I don't see a blank line at the top when
g:netrw_banner=0; I don't think the problem above is present any more.
Regards,
C 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/groups/opt_out.
another problem: let's say I do :e app/etc/local.xml and then open
netrw. I move over ../ and press <cr> to go back up one level in the
hierarchy. the cursor move on row 0. is it possibile to let it stay on
the first line of the file listings? i.e. after the netrw header. If i
disable the header with "let g:netrw_banner=0" there's one empty line on
top of the buffer, so a movement is still needed. It also happens when i
open a file with <cr>. if I open netrw again the cursor is no longer on
the file i opened, but on the first line. thanks in advance!
Hello!
With v151e of netrw, I don't see a blank line at the top when
g:netrw_banner=0; I don't think the problem above is present any more.
Regards,
C 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/groups/opt_out.
Re: problems (and bugs) with netrw
Matteo Cavalleri wrote:
<snip>
> still not what i want to do. If I have one file open, call :Explore,
> and then :q vim quits. I want to go back to the file i was editing.
> The functions I wrote seems to work, except for the weird lag...
<snip>
Hello!
Please try netrw v151e
(http://www.drchip.org/astronaut/vim/index.html#NETRW) and its :Rex
command. I've extended it to not only return to netrw, but when in
netrw, to return to the last file being edited in that window.
Regards,
C 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/groups/opt_out.
<snip>
> still not what i want to do. If I have one file open, call :Explore,
> and then :q vim quits. I want to go back to the file i was editing.
> The functions I wrote seems to work, except for the weird lag...
<snip>
Hello!
Please try netrw v151e
(http://www.drchip.org/astronaut/vim/index.html#NETRW) and its :Rex
command. I've extended it to not only return to netrw, but when in
netrw, to return to the last file being edited in that window.
Regards,
C 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/groups/opt_out.
Re: Dumb question: variables in the statusline
Huh. Trying that, with a statusline containing "%=", gives me
E518: Unknown option: %=
That's setting the statusline with execute.
--
b
Sent from my iPhone
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
E518: Unknown option: %=
That's setting the statusline with execute.
--
b
Sent from my iPhone
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Dumb question: variables in the statusline
On Feb 27, 2014, at 10:05 AM, Paul Isambert <zappathustra@free.fr> wrote:
> "statusline" is a string, so I guess the correct form is:
>
> exe "setlocal statusline=%!FunctionFromWhichIAmTryingToGetAStatusline('" . a:1 . "')"
I was wondering whether I would have to use execute. Thanks!
--
b
Sent from my iPhone
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> "statusline" is a string, so I guess the correct form is:
>
> exe "setlocal statusline=%!FunctionFromWhichIAmTryingToGetAStatusline('" . a:1 . "')"
I was wondering whether I would have to use execute. Thanks!
--
b
Sent from my iPhone
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Dumb question: variables in the statusline
"Ben Klein" <ben@silver-chalice.com>
>
> (Maybe this will be like last time, where I just had to send the
> question to the list before I could realize how idiotically wrong I
> was...)
>
>
> I have a function which takes ... arguments, and when I try to call
> it from another function to set the statusline, I basically get:
>
>
>
> E121: Undefined variable: a:1
> E116: Invalid arguments for function
> FunctionFromWhichIAmTryingToGetAStatusline(a:1)
>
>
> So the function getting the error is more or less:
>
>
> function! SetUpTheStatusline(...)
> setlocal statusline=%!FunctionFromWhichIAmTryingToGetAStatusline(a:1)
> endfunction
>
>
> And that is just getting those two errors.
>
>
> To be clear, I have verified that there is indeed a:1 in the
> SetUpTheStatusline() function. I can do (it seems) anything with it
> -- even use it in the call to
> FunctionFromWhichIAmTryingToGetAStatusline() -- except for using it
> in a function called in the statusline.
>
>
> What am I doing wrong?
"statusline" is a string, so I guess the correct form is:
exe "setlocal statusline=%!FunctionFromWhichIAmTryingToGetAStatusline('" . a:1 . "')"
Of course, a:1 should be of the proper type.
Best,
Paul
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
>
> (Maybe this will be like last time, where I just had to send the
> question to the list before I could realize how idiotically wrong I
> was...)
>
>
> I have a function which takes ... arguments, and when I try to call
> it from another function to set the statusline, I basically get:
>
>
>
> E121: Undefined variable: a:1
> E116: Invalid arguments for function
> FunctionFromWhichIAmTryingToGetAStatusline(a:1)
>
>
> So the function getting the error is more or less:
>
>
> function! SetUpTheStatusline(...)
> setlocal statusline=%!FunctionFromWhichIAmTryingToGetAStatusline(a:1)
> endfunction
>
>
> And that is just getting those two errors.
>
>
> To be clear, I have verified that there is indeed a:1 in the
> SetUpTheStatusline() function. I can do (it seems) anything with it
> -- even use it in the call to
> FunctionFromWhichIAmTryingToGetAStatusline() -- except for using it
> in a function called in the statusline.
>
>
> What am I doing wrong?
"statusline" is a string, so I guess the correct form is:
exe "setlocal statusline=%!FunctionFromWhichIAmTryingToGetAStatusline('" . a:1 . "')"
Of course, a:1 should be of the proper type.
Best,
Paul
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Dumb question: variables in the statusline
(Maybe this will be like last time, where I just had to send the question to the list before I could realize how idiotically wrong I was...)
-- I have a function which takes ... arguments, and when I try to call it from another function to set the statusline, I basically get:
E121: Undefined variable: a:1
E116: Invalid arguments for function FunctionFromWhichIAmTryingToGetAStatusline(a:1)
So the function getting the error is more or less:
function! SetUpTheStatusline(...)
setlocal statusline=%!FunctionFromWhichIAmTryingToGetAStatusline(a:1)
endfunction
And that is just getting those two errors.
To be clear, I have verified that there is indeed a:1 in the SetUpTheStatusline() function. I can do (it seems) anything with it -- even use it in the call to FunctionFromWhichIAmTryingToGetAStatusline() -- except for using it in a function called in the statusline.
What am I doing wrong?
--
b
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Windows 7 & temporary files
Apologies for the slow reply: must have missed the email notification. Realise I'm not painting a good picture of my attention to detail...
On Friday, 21 February 2014 19:11:09 UTC, Ben Fritz wrote:
> For the diff problem, you may have an old diffexpr hanging around with an outdated workaround for stupid cmd.exe quoting rules. Vim's handling of quoting on Windows was improved between 7.3 and 7.4 to work in more situations, but it also breaks some of the old workarounds. Installing a Vim version >= 7.4.103 will have a corrected diffexpr within the _vimrc created by the installer. Or, I pasted it in a superuser answer here: http://superuser.com/questions/697847/cant-run-vimdiff-7-4-on-windows-7
Installing 7.4.103 using the Cream installer sorted my diff issues as you predicted: thanks.
> For the temp files problem, as I mention in a reply to your post on the issue tracker, the 'directory' setting ought to have fixed it. If it doesn't, it's possible you were relying on workarounds for issues fixed by the default values of 'shellxquote', etc. Can you see the problems if you launch Vim with "gvim -N -u NONE -i NONE"?
Having used the 7.4.103 installer & seen diff working, I've tried rolling back to a situation where I could replicate both the diff & the temp issues (changing environment variables back to standard Windows 7 user\appdata\ folder, uninstalling 7.4.103, rebooting, reinstalling from the standard 7.4 executable, leaving the _vimrc as per vanilla install, changing UAC to notify once more), and I could replicate the diff issue but not the sort/temp file issue (whether running with the NONE options you suggest, or as standard). With the 7.4 install, as I'm sure you'd expect, shellquotex& was being set in _vimrc, but I would have said I'd reverted to the problem state with the changes listed in parentheses above.
In short, thanks for pointing to the superuser.com answer: that got me the Cream installer that appears to have resolved my issues. If you do want me to make any further attempts at replication, I'd be quite happy to, but it seems a version change has it sorted anyway.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Friday, 21 February 2014 19:11:09 UTC, Ben Fritz wrote:
> For the diff problem, you may have an old diffexpr hanging around with an outdated workaround for stupid cmd.exe quoting rules. Vim's handling of quoting on Windows was improved between 7.3 and 7.4 to work in more situations, but it also breaks some of the old workarounds. Installing a Vim version >= 7.4.103 will have a corrected diffexpr within the _vimrc created by the installer. Or, I pasted it in a superuser answer here: http://superuser.com/questions/697847/cant-run-vimdiff-7-4-on-windows-7
Installing 7.4.103 using the Cream installer sorted my diff issues as you predicted: thanks.
> For the temp files problem, as I mention in a reply to your post on the issue tracker, the 'directory' setting ought to have fixed it. If it doesn't, it's possible you were relying on workarounds for issues fixed by the default values of 'shellxquote', etc. Can you see the problems if you launch Vim with "gvim -N -u NONE -i NONE"?
Having used the 7.4.103 installer & seen diff working, I've tried rolling back to a situation where I could replicate both the diff & the temp issues (changing environment variables back to standard Windows 7 user\appdata\ folder, uninstalling 7.4.103, rebooting, reinstalling from the standard 7.4 executable, leaving the _vimrc as per vanilla install, changing UAC to notify once more), and I could replicate the diff issue but not the sort/temp file issue (whether running with the NONE options you suggest, or as standard). With the 7.4 install, as I'm sure you'd expect, shellquotex& was being set in _vimrc, but I would have said I'd reverted to the problem state with the changes listed in parentheses above.
In short, thanks for pointing to the superuser.com answer: that got me the Cream installer that appears to have resolved my issues. If you do want me to make any further attempts at replication, I'd be quite happy to, but it seems a version change has it sorted anyway.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Wednesday, February 26, 2014
Re: README.md to a doc?
* Tim Johnson <tim@akwebsoft.com> [140226 16:44]:
> * Adnan Zafar <adnanjzafar@gmail.com> [140226 16:32]:
> > Hi Tim,
> >
> > Just leave the file as it is or delete it. Plugin authors provide
> > files like that to provide information on GitHub pages for example. If
> > you're installing the plugin using Pathogen or Vundle or one of the
> > others, everything should be set up to just ignore it. If you're
> > installing manually, you can just delete the file.
>
> I was wondering if there were a built-in way to make a
> doc-compatible .txt file out of it. It sounds like there isn't.
>
> I wouldn't mind spending a little time "marking up" a README.md to
> make it doc-compatible. I think that there are adequate
> instructions in :h helptag
Turns out that in a general case a README.md file can be
converted to a doc .txt file in just a few minutes.
--
Tim
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com, http://www.tj49.com
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> * Adnan Zafar <adnanjzafar@gmail.com> [140226 16:32]:
> > Hi Tim,
> >
> > Just leave the file as it is or delete it. Plugin authors provide
> > files like that to provide information on GitHub pages for example. If
> > you're installing the plugin using Pathogen or Vundle or one of the
> > others, everything should be set up to just ignore it. If you're
> > installing manually, you can just delete the file.
>
> I was wondering if there were a built-in way to make a
> doc-compatible .txt file out of it. It sounds like there isn't.
>
> I wouldn't mind spending a little time "marking up" a README.md to
> make it doc-compatible. I think that there are adequate
> instructions in :h helptag
Turns out that in a general case a README.md file can be
converted to a doc .txt file in just a few minutes.
--
Tim
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com, http://www.tj49.com
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Need help about CompilerSet errorformat
MarcWeber wrote
>> > CompilerSet errorformat=%EError\ on\ line\ %l\ in %f:\ Column\ %c:,%Z%m
>> However, the errorformat can't recognize the error message output by the
>> Inno Setup compiler. The example error message is (two lines per error):
> You need multilen error format descriptions.
> :h errorformat
>
> => javac sample
>
> :setl efm=%A%f:%l:\ %m,%-Z%p^,%-C%.%#
>
>
> See docs for
> %A start of a multi-line message (unspecified type)
> %C continuation of a multi-line message
>
> Thus try somethingc like this (untested)
>
> %A%f:,%CColumn\ %l:,%Z%m
>
> mind the \ before the space.
Thanks for your suggestion. Finally I solve the problem by changing the
errorformat string to the following:
> CompilerSet errorformat=
> \%EError%*\\son%*\\sline%*\\s%l%*\\sin%*\\s%f:%*\\sColumn%*\\s%c:,%Z%m
I've no idea why errorformat didn't recognize the \<white space>, when I
replace all the \<white space> with %*\\s, it works perfectly.
Could anyone explain this? I use Vim 7.3 on Windows. I could post my _vimrc
here if you want. Thanks
--
View this message in context: http://vim.1045645.n5.nabble.com/Need-help-about-CompilerSet-errorformat-tp5720668p5720693.html
Sent from the Vim - General mailing list archive at Nabble.com.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
>> > CompilerSet errorformat=%EError\ on\ line\ %l\ in %f:\ Column\ %c:,%Z%m
>> However, the errorformat can't recognize the error message output by the
>> Inno Setup compiler. The example error message is (two lines per error):
> You need multilen error format descriptions.
> :h errorformat
>
> => javac sample
>
> :setl efm=%A%f:%l:\ %m,%-Z%p^,%-C%.%#
>
>
> See docs for
> %A start of a multi-line message (unspecified type)
> %C continuation of a multi-line message
>
> Thus try somethingc like this (untested)
>
> %A%f:,%CColumn\ %l:,%Z%m
>
> mind the \ before the space.
Thanks for your suggestion. Finally I solve the problem by changing the
errorformat string to the following:
> CompilerSet errorformat=
> \%EError%*\\son%*\\sline%*\\s%l%*\\sin%*\\s%f:%*\\sColumn%*\\s%c:,%Z%m
I've no idea why errorformat didn't recognize the \<white space>, when I
replace all the \<white space> with %*\\s, it works perfectly.
Could anyone explain this? I use Vim 7.3 on Windows. I could post my _vimrc
here if you want. Thanks
--
View this message in context: http://vim.1045645.n5.nabble.com/Need-help-about-CompilerSet-errorformat-tp5720668p5720693.html
Sent from the Vim - General mailing list archive at Nabble.com.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: README.md to a doc?
* Adnan Zafar <adnanjzafar@gmail.com> [140226 16:32]:
> Hi Tim,
>
> Just leave the file as it is or delete it. Plugin authors provide
> files like that to provide information on GitHub pages for example. If
> you're installing the plugin using Pathogen or Vundle or one of the
> others, everything should be set up to just ignore it. If you're
> installing manually, you can just delete the file.
I was wondering if there were a built-in way to make a
doc-compatible .txt file out of it. It sounds like there isn't.
I wouldn't mind spending a little time "marking up" a README.md to
make it doc-compatible. I think that there are adequate
instructions in :h helptag
--
Tim
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com, http://www.tj49.com
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Hi Tim,
>
> Just leave the file as it is or delete it. Plugin authors provide
> files like that to provide information on GitHub pages for example. If
> you're installing the plugin using Pathogen or Vundle or one of the
> others, everything should be set up to just ignore it. If you're
> installing manually, you can just delete the file.
I was wondering if there were a built-in way to make a
doc-compatible .txt file out of it. It sounds like there isn't.
I wouldn't mind spending a little time "marking up" a README.md to
make it doc-compatible. I think that there are adequate
instructions in :h helptag
--
Tim
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com, http://www.tj49.com
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: README.md to a doc?
Hi Tim,
Just leave the file as it is or delete it. Plugin authors provide
files like that to provide information on GitHub pages for example. If
you're installing the plugin using Pathogen or Vundle or one of the
others, everything should be set up to just ignore it. If you're
installing manually, you can just delete the file.
--Adnan
On Wed, Feb 26, 2014 at 8:05 PM, Tim Johnson <tim@akwebsoft.com> wrote:
> I don't understand how to integrate a README.md file into vim.
>
> Example: I have installed phpcomplete.vim under bundles/
> so ... I have ~/.vim/bundle/phpcomplete.vim/README.md
> And it contains documentation, but if I were to copy it to
> to ~/.cim/doc/phpcomplete.txt and run helptags, I get an error
> message.
> """
> E670: Mix of help file encodings within a language:
> /Users/tim/.vim/doc/phpcomplete.txt
> """
> :( and no :help README.md
>
> using 7.3 on Mac OSX 10.7
>
> thanks
> --
> Tim
> tim at tee jay forty nine dot com or akwebsoft dot com
> http://www.akwebsoft.com, http://www.tj49.com
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Just leave the file as it is or delete it. Plugin authors provide
files like that to provide information on GitHub pages for example. If
you're installing the plugin using Pathogen or Vundle or one of the
others, everything should be set up to just ignore it. If you're
installing manually, you can just delete the file.
--Adnan
On Wed, Feb 26, 2014 at 8:05 PM, Tim Johnson <tim@akwebsoft.com> wrote:
> I don't understand how to integrate a README.md file into vim.
>
> Example: I have installed phpcomplete.vim under bundles/
> so ... I have ~/.vim/bundle/phpcomplete.vim/README.md
> And it contains documentation, but if I were to copy it to
> to ~/.cim/doc/phpcomplete.txt and run helptags, I get an error
> message.
> """
> E670: Mix of help file encodings within a language:
> /Users/tim/.vim/doc/phpcomplete.txt
> """
> :( and no :help README.md
>
> using 7.3 on Mac OSX 10.7
>
> thanks
> --
> Tim
> tim at tee jay forty nine dot com or akwebsoft dot com
> http://www.akwebsoft.com, http://www.tj49.com
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
README.md to a doc?
I don't understand how to integrate a README.md file into vim.
Example: I have installed phpcomplete.vim under bundles/
so ... I have ~/.vim/bundle/phpcomplete.vim/README.md
And it contains documentation, but if I were to copy it to
to ~/.cim/doc/phpcomplete.txt and run helptags, I get an error
message.
"""
E670: Mix of help file encodings within a language:
/Users/tim/.vim/doc/phpcomplete.txt
"""
:( and no :help README.md
using 7.3 on Mac OSX 10.7
thanks
--
Tim
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com, http://www.tj49.com
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Example: I have installed phpcomplete.vim under bundles/
so ... I have ~/.vim/bundle/phpcomplete.vim/README.md
And it contains documentation, but if I were to copy it to
to ~/.cim/doc/phpcomplete.txt and run helptags, I get an error
message.
"""
E670: Mix of help file encodings within a language:
/Users/tim/.vim/doc/phpcomplete.txt
"""
:( and no :help README.md
using 7.3 on Mac OSX 10.7
thanks
--
Tim
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com, http://www.tj49.com
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: php - drupal - symfony - how to manage?
* Benji Fisher <benji@FisherFam.org> [140226 14:13]:
> Tim:
>
> By "the drupal plugin" do you mean https://drupal.org/project/vimrc ?
Yes.
> That already makes some effort to avoid taking over non-Drupal PHP files:
> see https://drupal.org/node/1903214 .
> I am not sure what is available for Symfony. I do plan to modify the
> Drupal "vimrc project" so that it does the right thing (conforming to
> different coding standards) when editing Drupal-ish and Symfony-ish files
> in the same project. I am not sure when I will have time for this ...
Understood, thanks
--
Tim
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com, http://www.tj49.com
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Tim:
>
> By "the drupal plugin" do you mean https://drupal.org/project/vimrc ?
Yes.
> That already makes some effort to avoid taking over non-Drupal PHP files:
> see https://drupal.org/node/1903214 .
> I am not sure what is available for Symfony. I do plan to modify the
> Drupal "vimrc project" so that it does the right thing (conforming to
> different coding standards) when editing Drupal-ish and Symfony-ish files
> in the same project. I am not sure when I will have time for this ...
Understood, thanks
--
Tim
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com, http://www.tj49.com
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: php - drupal - symfony - how to manage?
Tim:
By "the drupal plugin" do you mean https://drupal.org/project/vimrc ? That already makes some effort to avoid taking over non-Drupal PHP files: see https://drupal.org/node/1903214 .
I am not sure what is available for Symfony. I do plan to modify the Drupal "vimrc project" so that it does the right thing (conforming to different coding standards) when editing Drupal-ish and Symfony-ish files in the same project. I am not sure when I will have time for this ...
HTH
--
Benji Fisher
On Tue, Feb 25, 2014 at 8:55 PM, Tim Johnson <tim@akwebsoft.com> wrote:
I'm starting to learn to write drupal 7 modules and at the same
time, symfony. For the time being, they are separate venues,
although drupal 8 will have symfony as the "underlying" framework.
I have been investigating the use of plugins for both drupal and
symfony, but I am only acquainted with using plugins based on
filetype.
FYI: Symfony is based on php, as is drupal.
Is there a way to use the drupal plugin separately from the symfony
plugin? I wouldn't have a problem with manually sourcing a plugin,
if that is what it came too, but would welcome advice from wiser
heads than mine, as I am eternally a "vim noob".
TIA
--
Tim
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com, http://www.tj49.com
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: fixing mistakes in the command line
On Wednesday, February 26, 2014 2:57:18 AM UTC-8, Matteo Cavalleri wrote:
> Il giorno mercoledì 26 febbraio 2014 11:49:20 UTC+1, Matteo Cavalleri ha scritto:
>> I discovered just now abbreviations works also in command line mode, so I suppose my problem is solved :) thanks anyway and sorry for the noise and I discovered just now again they also mess with my search patterns... :(
Define an abbreviation using:
:ia
:help :ia
Then it will only be triggered in insert mode and not command line mode.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Il giorno mercoledì 26 febbraio 2014 11:49:20 UTC+1, Matteo Cavalleri ha scritto:
>> I discovered just now abbreviations works also in command line mode, so I suppose my problem is solved :) thanks anyway and sorry for the noise and I discovered just now again they also mess with my search patterns... :(
Define an abbreviation using:
:ia
:help :ia
Then it will only be triggered in insert mode and not command line mode.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch for tagselect.vim
On 2014-02-26, Marcelo Montú wrote:
> Hello Gary, did you receive any reply from the author?
No, I never did.
> There a is a fork, https://github.com/asford/tagselect, from the
> vim-scripts mirror on github, which may be used as a base for your
> patch.
Thanks. I'll take a look.
Regards,
Gary
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Hello Gary, did you receive any reply from the author?
No, I never did.
> There a is a fork, https://github.com/asford/tagselect, from the
> vim-scripts mirror on github, which may be used as a base for your
> patch.
Thanks. I'll take a look.
Regards,
Gary
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: fixing mistakes in the command line
On Wednesday, February 26, 2014 4:57:18 AM UTC-6, Matteo Cavalleri wrote:
> Il giorno mercoledì 26 febbraio 2014 11:49:20 UTC+1, Matteo Cavalleri ha scritto:
>
>
>
> > I discovered just now abbreviations works also in command line mode, so I suppose my problem is solved :) thanks anyway and sorry for the noise
>
>
>
> and I discovered just now again they also mess with my search patterns... :(
You can fix this with techniques here: http://vim.wikia.com/wiki/Replace_a_builtin_command_using_cabbrev
This tip uses getcmdtype() to make sure only ex commands (not searches) get expanded, and getcmdpos() to make sure it only happens if it's the first character you type on the command-line.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Il giorno mercoledì 26 febbraio 2014 11:49:20 UTC+1, Matteo Cavalleri ha scritto:
>
>
>
> > I discovered just now abbreviations works also in command line mode, so I suppose my problem is solved :) thanks anyway and sorry for the noise
>
>
>
> and I discovered just now again they also mess with my search patterns... :(
You can fix this with techniques here: http://vim.wikia.com/wiki/Replace_a_builtin_command_using_cabbrev
This tip uses getcmdtype() to make sure only ex commands (not searches) get expanded, and getcmdpos() to make sure it only happens if it's the first character you type on the command-line.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
X copy buffer
If I have vim open in a tmux session and X crashes, when I reopen it,
it appears the + buffer doesn't work anymore. Is there a way to fix
this without closing vim?
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
it appears the + buffer doesn't work anymore. Is there a way to fix
this without closing vim?
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch for tagselect.vim
Hello Gary, did you receive any reply from the author?
There a is a fork, https://github.com/asford/tagselect, from the vim-scripts mirror on github, which may be used as a base for your patch.
Regards
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
There a is a fork, https://github.com/asford/tagselect, from the vim-scripts mirror on github, which may be used as a base for your patch.
Regards
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: How to edit a macro?
Dear Marcin, Tim, and Erik,
thank you very much for your help.
All suggesions helped and worked.
Cheers!
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
thank you very much for your help.
All suggesions helped and worked.
Cheers!
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: How to edit a macro?
On 10:52 Tue 25 Feb , Asis Hallab wrote:
> Dear Vim experts,
>
> after recording a macro I realized that I forgot to specify the
> register I yanked into.
>
> The macro in register q was
>
> /^[^#].*<-.*GO:\d\{7\}^My/)^M
>
> and matches lines like the following line 1
> 1 light <- c( 'GO:1234567',
> 2 'GO:7162635', 'GO:4536271',
> 3 'GO:7654321' )
>
> the macro yanks everything up to, and including, line 3.
>
> The problem is, that I want to specify the register the content is yanked to.
> So I tried
>
> :let @q='/^[^#].*<-.*GO:\d\{7\}^M"Gy/)^M'
>
> But the ^M form a problem. The macro is not executed correctly.
>
> Does anyone know how to solve this?
>
> Cheers!
You can dump the macro with:
^r^r"q (in the insert mode see :h i^r^r)
then you can edit it and yank back to register q.
Best regards,
Marcin
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Dear Vim experts,
>
> after recording a macro I realized that I forgot to specify the
> register I yanked into.
>
> The macro in register q was
>
> /^[^#].*<-.*GO:\d\{7\}^My/)^M
>
> and matches lines like the following line 1
> 1 light <- c( 'GO:1234567',
> 2 'GO:7162635', 'GO:4536271',
> 3 'GO:7654321' )
>
> the macro yanks everything up to, and including, line 3.
>
> The problem is, that I want to specify the register the content is yanked to.
> So I tried
>
> :let @q='/^[^#].*<-.*GO:\d\{7\}^M"Gy/)^M'
>
> But the ^M form a problem. The macro is not executed correctly.
>
> Does anyone know how to solve this?
>
> Cheers!
You can dump the macro with:
^r^r"q (in the insert mode see :h i^r^r)
then you can edit it and yank back to register q.
Best regards,
Marcin
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Need help about CompilerSet errorformat
> > CompilerSet errorformat=%EError\ on\ line\ %l\ in %f:\ Column\ %c:,%Z%m
> However, the errorformat can't recognize the error message output by the
> Inno Setup compiler. The example error message is (two lines per error):
You need multilen error format descriptions.
:h errorformat
=> javac sample
:setl efm=%A%f:%l:\ %m,%-Z%p^,%-C%.%#
See docs for
%A start of a multi-line message (unspecified type)
%C continuation of a multi-line message
Thus try somethingc like this (untested)
%A%f:,%CColumn\ %l:,%Z%m
mind the \ before the space.
Marc Weber
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> However, the errorformat can't recognize the error message output by the
> Inno Setup compiler. The example error message is (two lines per error):
You need multilen error format descriptions.
:h errorformat
=> javac sample
:setl efm=%A%f:%l:\ %m,%-Z%p^,%-C%.%#
See docs for
%A start of a multi-line message (unspecified type)
%C continuation of a multi-line message
Thus try somethingc like this (untested)
%A%f:,%CColumn\ %l:,%Z%m
mind the \ before the space.
Marc Weber
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: ??? mozcpp filetype ???
Tony Mechelynck <antoine.mechelynck@gmail.com>:
> I notice a syntax/mozcpp.vim script in my $VIM/vimfiles tree, and
> the appropriate auxiliary files to recognise that filetype
> (statements in $VIM/filetype/filetype.vim for C++ sources in or
> below my Mozilla source repositories) and treat it otherwise as C++
> (ftplugin/mozcpp.vim does nothing other than "runtime!
> ftplugin/cpp.vim").
>
> This looks useful to colorize Mozilla extensions to C++ properly
> (including e.g. many keywords with names starting with PR, NS_ or
> ns), but I can't remember where I got it from, or how to update it.
> Any help please? The syntax script is dated 2011-07-22.
A quick googling turn up this page, which even has a comment from you:
http://kazhack.org/?post/2011/08/11/Vim-Syntax-Highlighting-for-Mozilla-C-Files
-Jan
--
-[ OpenPGP key ID: 00A0FD5F ]-
A book must be the ax for the frozen sea within us.
-- Franz Kafka
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> I notice a syntax/mozcpp.vim script in my $VIM/vimfiles tree, and
> the appropriate auxiliary files to recognise that filetype
> (statements in $VIM/filetype/filetype.vim for C++ sources in or
> below my Mozilla source repositories) and treat it otherwise as C++
> (ftplugin/mozcpp.vim does nothing other than "runtime!
> ftplugin/cpp.vim").
>
> This looks useful to colorize Mozilla extensions to C++ properly
> (including e.g. many keywords with names starting with PR, NS_ or
> ns), but I can't remember where I got it from, or how to update it.
> Any help please? The syntax script is dated 2011-07-22.
A quick googling turn up this page, which even has a comment from you:
http://kazhack.org/?post/2011/08/11/Vim-Syntax-Highlighting-for-Mozilla-C-Files
-Jan
--
-[ OpenPGP key ID: 00A0FD5F ]-
A book must be the ax for the frozen sea within us.
-- Franz Kafka
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Colours in the statusline
Juanjo Gomez Navarro <juanjo.gomeznavarro@gmail.com>:
> hi User1 guifg=#eea040 guibg=#222222
> hi User2 guifg=#dd3333 guibg=#222222
> hi User3 guifg=#ff66ff guibg=#222222
> hi User4 guifg=#a0ee40 guibg=#222222
> hi User5 guifg=#eeee40 guibg=#222222
The 'gui' settings are, as the name would suggest, only for the gui
versions of Vim (like GVim). In addition console Vim does not support
arbitrary RGB values, only the (up to) 256 colours that your terminal
can display. So you would either have to add ctermfg/ctermbg settings
with your preferred terminal colours or use a script like CSApprox that
converts the gui values automatically.
-Jan
--
-[ OpenPGP key ID: 00A0FD5F ]-
Here the ways of men part: if you wish to strive for peace of soul and
pleasure, then believe; if you wish to be a devotee of truth, then inquire.
-- Friedrich Nietzsche
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> hi User1 guifg=#eea040 guibg=#222222
> hi User2 guifg=#dd3333 guibg=#222222
> hi User3 guifg=#ff66ff guibg=#222222
> hi User4 guifg=#a0ee40 guibg=#222222
> hi User5 guifg=#eeee40 guibg=#222222
The 'gui' settings are, as the name would suggest, only for the gui
versions of Vim (like GVim). In addition console Vim does not support
arbitrary RGB values, only the (up to) 256 colours that your terminal
can display. So you would either have to add ctermfg/ctermbg settings
with your preferred terminal colours or use a script like CSApprox that
converts the gui values automatically.
-Jan
--
-[ OpenPGP key ID: 00A0FD5F ]-
Here the ways of men part: if you wish to strive for peace of soul and
pleasure, then believe; if you wish to be a devotee of truth, then inquire.
-- Friedrich Nietzsche
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
??? mozcpp filetype ???
I notice a syntax/mozcpp.vim script in my $VIM/vimfiles tree, and the
appropriate auxiliary files to recognise that filetype (statements in
$VIM/filetype/filetype.vim for C++ sources in or below my Mozilla source
repositories) and treat it otherwise as C++ (ftplugin/mozcpp.vim does
nothing other than "runtime! ftplugin/cpp.vim").
This looks useful to colorize Mozilla extensions to C++ properly
(including e.g. many keywords with names starting with PR, NS_ or ns),
but I can't remember where I got it from, or how to update it. Any help
please? The syntax script is dated 2011-07-22.
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
91. It's Saturday afternoon in the middle of may and you are on computer.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
appropriate auxiliary files to recognise that filetype (statements in
$VIM/filetype/filetype.vim for C++ sources in or below my Mozilla source
repositories) and treat it otherwise as C++ (ftplugin/mozcpp.vim does
nothing other than "runtime! ftplugin/cpp.vim").
This looks useful to colorize Mozilla extensions to C++ properly
(including e.g. many keywords with names starting with PR, NS_ or ns),
but I can't remember where I got it from, or how to update it. Any help
please? The syntax script is dated 2011-07-22.
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
91. It's Saturday afternoon in the middle of may and you are on computer.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Colours in the statusline
Hi, I'm trying to tune a bit my statusline. I have added these lines:
--
-- set noruler
set laststatus=2
hi User1 guifg=#eea040 guibg=#222222
hi User2 guifg=#dd3333 guibg=#222222
hi User3 guifg=#ff66ff guibg=#222222
hi User4 guifg=#a0ee40 guibg=#222222
hi User5 guifg=#eeee40 guibg=#222222
set statusline=
set statusline +=%1*\ %n\ %*
set statusline +=%5*%{&ff}%*
set statusline +=%3*%y%*
set statusline +=%4*\ %<%F%*
set statusline +=%2*%m%*
set statusline +=%1*%=%5l%*
set statusline +=%2*/%L%*
set statusline +=%1*%4v\ %*
set statusline +=%2*0x%04B\ %*
vim displays properly the content of the line, but does not take into account the colours. However gvim does. I attach two screen captures to show what I mean.
What do you think it's going on here?
Juan José Gómez-Navarro
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: fixing mistakes in the command line
Il giorno mercoledì 26 febbraio 2014 11:49:20 UTC+1, Matteo Cavalleri ha scritto:
> I discovered just now abbreviations works also in command line mode, so I suppose my problem is solved :) thanks anyway and sorry for the noise
and I discovered just now again they also mess with my search patterns... :(
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> I discovered just now abbreviations works also in command line mode, so I suppose my problem is solved :) thanks anyway and sorry for the noise
and I discovered just now again they also mess with my search patterns... :(
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: fixing mistakes in the command line
I discovered just now abbreviations works also in command line mode, so I suppose my problem is solved :) thanks anyway and sorry for the noise
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
fixing mistakes in the command line
a lot of time ago, I copied these lines in my vimrc to fix some common mistakes:
nnoremap :W :w
nnoremap :Q :q
nnoremap :E :e
I don't remember where I took this suggestions, but it worked. Now I see I type a lot of times ":ag" instead of ":Ag", however as soon I started to add this new mapping I asked myself if this is really the correct way to deal with this kind of task... I searched on google for some better suggestions, but usually searching about vim's command line finds articles on starting vim from shell with arguments... -________-
In any case even further searches found nothing, so I'm asking here if someone knows what would be the correct way to "auto-fix" mistakes in the command line.
thanks in advance!
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
nnoremap :W :w
nnoremap :Q :q
nnoremap :E :e
I don't remember where I took this suggestions, but it worked. Now I see I type a lot of times ":ag" instead of ":Ag", however as soon I started to add this new mapping I asked myself if this is really the correct way to deal with this kind of task... I searched on google for some better suggestions, but usually searching about vim's command line finds articles on starting vim from shell with arguments... -________-
In any case even further searches found nothing, so I'm asking here if someone knows what would be the correct way to "auto-fix" mistakes in the command line.
thanks in advance!
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Need help about CompilerSet errorformat
I write a compiler plugin for Inno Setup, the following is the content of
iss.vim:
> " Vim compiler file
> " Compiler: iscc (Inno Setup Compiler)
> " Maintainer: Levski Weng
> <
> levskiweng@gmail.com
> >
> " Last Change: 2014 Feb 26
>
> if exists("current_compiler")
> finish
> endif
> let current_compiler = "iss"
>
> if exists(":CompilerSet") != 2 " older Vim always used :setlocal
> command -nargs=* CompilerSet setlocal
> <args>
> endif
>
> CompilerSet makeprg=iscc\ %
>
> CompilerSet errorformat=%EError\ on\ line\ %l\ in %f:\ Column\ %c:,%Z%m
However, the errorformat can't recognize the error message output by the
Inno Setup compiler. The example error message is (two lines per error):
> Error on line 37 in
> C:\Users\wengsq\Desktop\DailyBuildSystem\relative_files\CDMS-agent-auto-installer\setup.iss:
> Column 1:
> Identifier expected.
Is anything wrong with my errorformat?
Any suggestion will be appreciated. Thanks in advanced.
--
View this message in context: http://vim.1045645.n5.nabble.com/Need-help-about-CompilerSet-errorformat-tp5720668.html
Sent from the Vim - General mailing list archive at Nabble.com.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
iss.vim:
> " Vim compiler file
> " Compiler: iscc (Inno Setup Compiler)
> " Maintainer: Levski Weng
> <
> levskiweng@gmail.com
> >
> " Last Change: 2014 Feb 26
>
> if exists("current_compiler")
> finish
> endif
> let current_compiler = "iss"
>
> if exists(":CompilerSet") != 2 " older Vim always used :setlocal
> command -nargs=* CompilerSet setlocal
> <args>
> endif
>
> CompilerSet makeprg=iscc\ %
>
> CompilerSet errorformat=%EError\ on\ line\ %l\ in %f:\ Column\ %c:,%Z%m
However, the errorformat can't recognize the error message output by the
Inno Setup compiler. The example error message is (two lines per error):
> Error on line 37 in
> C:\Users\wengsq\Desktop\DailyBuildSystem\relative_files\CDMS-agent-auto-installer\setup.iss:
> Column 1:
> Identifier expected.
Is anything wrong with my errorformat?
Any suggestion will be appreciated. Thanks in advanced.
--
View this message in context: http://vim.1045645.n5.nabble.com/Need-help-about-CompilerSet-errorformat-tp5720668.html
Sent from the Vim - General mailing list archive at Nabble.com.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Mapping a key as a switch button ?
Ooops I've missed that one, sorry.
Great, it's exactely what I was looking for.
Thanks
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Great, it's exactely what I was looking for.
Thanks
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Tuesday, February 25, 2014
Need help about CompilerSet errorformat
Hello, after reading the Vim manual about CompilerSet and errorformat, I add a custom compiler for Inno Setup for Vim and add the iss.vim to the compiler folder, but Vim doesn't work as expected.
The error message looks like:
Error on line 37 in C:\Users\xxx\setup.iss: Column 1:
Identifier expected.
And the content of my iss.vim under Vim's compiler folder is:
" Vim compiler file
" Compiler: iscc (Inno Setup Compiler)
" Maintainer: Levski Weng <levskiweng@gmail.com>
" Last Change: 2014 Feb 26
if exists("current_compiler")
finish
endif
let current_compiler = "iss"
if exists(":CompilerSet") != 2 " older Vim always used :setlocal
command -nargs=* CompilerSet setlocal <args>
endif
CompilerSet makeprg=iscc\ %
CompilerSet errorformat=%EError\ on\ line\ %l\ in %f:\ Column\ %c:,%Z%m
When I compile a not well-formed .iss file with Vim using command ":make", the vim tells me that the shell return 2, which is the same as my compiling in Windows command line. But Vim doesn't jump to the error line then.
Is my errorformat wrong? And how to fix it?
Any suggestion will be appreciated.
P.S:
I've add the Inno Setup installation folder to the %PATH%, the compiler is iscc.exe
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
The error message looks like:
Error on line 37 in C:\Users\xxx\setup.iss: Column 1:
Identifier expected.
And the content of my iss.vim under Vim's compiler folder is:
" Vim compiler file
" Compiler: iscc (Inno Setup Compiler)
" Maintainer: Levski Weng <levskiweng@gmail.com>
" Last Change: 2014 Feb 26
if exists("current_compiler")
finish
endif
let current_compiler = "iss"
if exists(":CompilerSet") != 2 " older Vim always used :setlocal
command -nargs=* CompilerSet setlocal <args>
endif
CompilerSet makeprg=iscc\ %
CompilerSet errorformat=%EError\ on\ line\ %l\ in %f:\ Column\ %c:,%Z%m
When I compile a not well-formed .iss file with Vim using command ":make", the vim tells me that the shell return 2, which is the same as my compiling in Windows command line. But Vim doesn't jump to the error line then.
Is my errorformat wrong? And how to fix it?
Any suggestion will be appreciated.
P.S:
I've add the Inno Setup installation folder to the %PATH%, the compiler is iscc.exe
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
php - drupal - symfony - how to manage?
I'm starting to learn to write drupal 7 modules and at the same
time, symfony. For the time being, they are separate venues,
although drupal 8 will have symfony as the "underlying" framework.
I have been investigating the use of plugins for both drupal and
symfony, but I am only acquainted with using plugins based on
filetype.
FYI: Symfony is based on php, as is drupal.
Is there a way to use the drupal plugin separately from the symfony
plugin? I wouldn't have a problem with manually sourcing a plugin,
if that is what it came too, but would welcome advice from wiser
heads than mine, as I am eternally a "vim noob".
TIA
--
Tim
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com, http://www.tj49.com
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
time, symfony. For the time being, they are separate venues,
although drupal 8 will have symfony as the "underlying" framework.
I have been investigating the use of plugins for both drupal and
symfony, but I am only acquainted with using plugins based on
filetype.
FYI: Symfony is based on php, as is drupal.
Is there a way to use the drupal plugin separately from the symfony
plugin? I wouldn't have a problem with manually sourcing a plugin,
if that is what it came too, but would welcome advice from wiser
heads than mine, as I am eternally a "vim noob".
TIA
--
Tim
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com, http://www.tj49.com
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Still having different pwd for different windows
Aaron Bohannon wrote:
> I only skimmed this thread, but surprisingly, no one seems to have brought up the issue of netrw. Whenever you browse a directory in a window, netrw executes an :lcd command in that window, so that it's CWD is different from the rest of the windows. Now that is actually a perfectly sensible thing for netrw to do if g:netrw_keepdir == 0. However, netrw *always* does it, even if g:netrw_keepdir == 1 (the default, meaning "don't change the CWD"). It drives me nuts.
>
Please give me an example.
With g:netrw_keepdir= 1, and starting from my home directory:
vim somefile
:echo getcwd() (shows home directory)
:wincmd s
:e .vim
:echo getcwd() (shows home directory)
:wincmd j
:echo getcwd() (shows home directory)
So, netrw did not change the cwd, in either of the two windows used.
Regards,
C 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/groups/opt_out.
> I only skimmed this thread, but surprisingly, no one seems to have brought up the issue of netrw. Whenever you browse a directory in a window, netrw executes an :lcd command in that window, so that it's CWD is different from the rest of the windows. Now that is actually a perfectly sensible thing for netrw to do if g:netrw_keepdir == 0. However, netrw *always* does it, even if g:netrw_keepdir == 1 (the default, meaning "don't change the CWD"). It drives me nuts.
>
Please give me an example.
With g:netrw_keepdir= 1, and starting from my home directory:
vim somefile
:echo getcwd() (shows home directory)
:wincmd s
:e .vim
:echo getcwd() (shows home directory)
:wincmd j
:echo getcwd() (shows home directory)
So, netrw did not change the cwd, in either of the two windows used.
Regards,
C 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/groups/opt_out.
Re: Still having different pwd for different windows
I only skimmed this thread, but surprisingly, no one seems to have brought up the issue of netrw. Whenever you browse a directory in a window, netrw executes an :lcd command in that window, so that it's CWD is different from the rest of the windows. Now that is actually a perfectly sensible thing for netrw to do if g:netrw_keepdir == 0. However, netrw *always* does it, even if g:netrw_keepdir == 1 (the default, meaning "don't change the CWD"). It drives me nuts.
On Sunday, April 28, 2013 4:36:17 PM UTC-7, AndyHancock wrote:
> I posted previously about the fact that pwd returns different
>
> directories for different windows. I was pointed to autochdir, in
>
> particular:
>
>
>
> verbose set autochdir?
>
>
>
> which always returns noautochdir.
>
>
>
> I already have noautochdir in my vimrc, and the above command
>
> indicates that netrw was last to set the autochdir option.
>
>
>
> The problem is sporadic enough that it isn't clear to me that I will
>
> ever be able to figure out how/when autochdir is being set (if it is).
>
>
>
> As an alternative to tracking this down, is there a way to prevent
>
> autochdir from being set at all? I mean even if a plugin or function
>
> somehwere issues a command to set autochdir, I want [g]vim to be
>
> incapable of complying.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Sunday, April 28, 2013 4:36:17 PM UTC-7, AndyHancock wrote:
> I posted previously about the fact that pwd returns different
>
> directories for different windows. I was pointed to autochdir, in
>
> particular:
>
>
>
> verbose set autochdir?
>
>
>
> which always returns noautochdir.
>
>
>
> I already have noautochdir in my vimrc, and the above command
>
> indicates that netrw was last to set the autochdir option.
>
>
>
> The problem is sporadic enough that it isn't clear to me that I will
>
> ever be able to figure out how/when autochdir is being set (if it is).
>
>
>
> As an alternative to tracking this down, is there a way to prevent
>
> autochdir from being set at all? I mean even if a plugin or function
>
> somehwere issues a command to set autochdir, I want [g]vim to be
>
> incapable of complying.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: From 7.4.135 to 7.4.182 now leaves backup files behind
On Tue, Feb 25, 2014 at 08:46:59AM -0800, wearyofallthiscrap@gmail.com wrote:
> On Monday, February 24, 2014 8:28:37 PM UTC-5, Ben Fritz wrote:
> > What might have changed? The vimrc_example.vim file distributed
> > with Vim changed recently to turn the 'undofile' option on. You are
> > probably sourcing that file in your own vimrc.
> Good catch. My .vimrc has been largely unchanged since 2011 or
> so and now I don't remember now why I decided to source that file
> instead of Doing The Right Thing.
there are people [who I believe are misguided] who recommend newbies
source that file -- your experience is quite natural
--
_|_ _ __|_|_ ._ o|
|_(_)(_)|_| ||_)||<
|
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> On Monday, February 24, 2014 8:28:37 PM UTC-5, Ben Fritz wrote:
> > What might have changed? The vimrc_example.vim file distributed
> > with Vim changed recently to turn the 'undofile' option on. You are
> > probably sourcing that file in your own vimrc.
> Good catch. My .vimrc has been largely unchanged since 2011 or
> so and now I don't remember now why I decided to source that file
> instead of Doing The Right Thing.
there are people [who I believe are misguided] who recommend newbies
source that file -- your experience is quite natural
--
_|_ _ __|_|_ ._ o|
|_(_)(_)|_| ||_)||<
|
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: How to edit a macro?
On 2014-02-25 10:52, Asis Hallab wrote:
> /^[^#].*<-.*GO:\d\{7\}^My/)^M
[snip]
> :let @q='/^[^#].*<-.*GO:\d\{7\}^M"Gy/)^M'
You can do things like
:let @q=subsitute(@q, 'y', '"Gy", '')
which would make the same transformation without needing to figure
out the proper escaping and quotation-notation.
-tim
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> /^[^#].*<-.*GO:\d\{7\}^My/)^M
[snip]
> :let @q='/^[^#].*<-.*GO:\d\{7\}^M"Gy/)^M'
You can do things like
:let @q=subsitute(@q, 'y', '"Gy", '')
which would make the same transformation without needing to figure
out the proper escaping and quotation-notation.
-tim
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: From 7.4.135 to 7.4.182 now leaves backup files behind
On Monday, February 24, 2014 8:28:37 PM UTC-5, Ben Fritz wrote:
> What might have changed? The vimrc_example.vim file distributed
> with Vim changed recently to turn the 'undofile' option on. You are
> probably sourcing that file in your own vimrc.
Good catch. My .vimrc has been largely unchanged since 2011 or
so and now I don't remember now why I decided to source that file
instead of Doing The Right Thing.
Thank you Ben!
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> What might have changed? The vimrc_example.vim file distributed
> with Vim changed recently to turn the 'undofile' option on. You are
> probably sourcing that file in your own vimrc.
Good catch. My .vimrc has been largely unchanged since 2011 or
so and now I don't remember now why I decided to source that file
instead of Doing The Right Thing.
Thank you Ben!
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: How to edit a macro?
On 25.02.14 10:52, Asis Hallab wrote:
> :let @q='/^[^#].*<-.*GO:\d\{7\}^M"Gy/)^M'
>
> But the ^M form a problem. The macro is not executed correctly.
Try: ^V^M so that you have a literal control-M, not the two characters ^
and M.
Erik
--
My 4 year old niece offered a helpful suggestion while I was in the middle of
resolving a LAN routing problem: "Turn it off and turn it on, Uncle Jack; that
always works for me." - Jack Ganssle
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> :let @q='/^[^#].*<-.*GO:\d\{7\}^M"Gy/)^M'
>
> But the ^M form a problem. The macro is not executed correctly.
Try: ^V^M so that you have a literal control-M, not the two characters ^
and M.
Erik
--
My 4 year old niece offered a helpful suggestion while I was in the middle of
resolving a LAN routing problem: "Turn it off and turn it on, Uncle Jack; that
always works for me." - Jack Ganssle
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Netrw issue
Thanks. It works great now!
On Mon, Feb 24, 2014 at 3:50 PM, Charles Campbell
<Charles.E.Campbell@nasa.gov> wrote:
> A Loumiotis wrote:
>>
>> On Fri, Feb 21, 2014 at 8:04 PM, Charles Campbell
>> <Charles.E.Campbell@nasa.gov> wrote:
>>>
>>> A Loumiotis wrote:
>>>>
>>>> I have some issues with exploring a folder for which the name contains
>>>> a space and I use command line completion. For example:
>>>>
>>>> :Exp e:\m<tab>
>>>>
>>>> expands to
>>>>
>>>> :Exp e:\My\ Documents
>>>>
>>>> but it does not create a list of the folder contents.
>>>>
>>>> But if I manually delete the backward slash:
>>>>
>>>> :Exp e:\My Documents
>>>>
>>>> then it works.
>>>>
>>>> On the other hand if I use:
>>>>
>>>> :e e:\m<tab>
>>>>
>>>> it expands to
>>>>
>>>> :e e:\My\ Documents
>>>>
>>>> and it works as expected, ie, it lists the contents of the directory
>>>> immediately without having to delete the backward slashes that escape
>>>> spaces as I have to do with the :Exp command.
>>>>
>>>> I use gVim on Windows XP 32 bit.
>>>>
>>> Hello!
>>>
>>> Please try v151d of netrw, available from my website:
>>> http://www.drchip.org/astronaut/vim/index.html#NETRW
>>>
>>> Regards,
>>> C 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/groups/opt_out.
>>
>>
>> Thanks a lot for your help.
>> It works but I now get a list of error messages before I see the
>> contents of any folder:
>>
>> For example if I do:
>>
>> :Exp e:\My\ Documents
>>
>> I get the following errors and then I see correctly the folder contents:
>>
>> Error detected while processing function netrw#Explore:
>> line 1:
>> E117: Unknown function: Dfunc
>> line 18:
>> E117: Unknown function: Decho
>> line 24:
>> E117: Unknown function: Decho
>> line 29:
>> E117: Unknown function: Decho
>> Error detected while processing function netrw#Explore..netrw#Explore:
>> line 1:
>> E117: Unknown function: Dfunc
>> line 18:
>> E117: Unknown function: Decho
>> line 24:
>> E117: Unknown function: Decho
>> line 34:
>> E117: Unknown function: Decho
>> line 92:
>> E117: Unknown function: Decho
>> line 97:
>> E117: Unknown function: Decho
>> line 114:
>> E117: Unknown function: Decho
>> line 116:
>> E117: Unknown function: Decho
>> line 129:
>> E117: Unknown function: Decho
>> line 135:
>> E117: Unknown function: Decho
>> line 178:
>> E117: Unknown function: Decho
>> line 183:
>> E117: Unknown function: Decho
>> line 201:
>> E117: Unknown function: Decho
>> "" [Not edited] --No lines in buffer--
>> "" --No lines in buffer--
>> "" --No lines in buffer--
>> Pattern not found: ^$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.h$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.c$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.cpp$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.o$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.obj$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.info$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.bak$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \~$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Error detected while processing function
>>
>> netrw#Explore..netrw#Explore..netrw#LocalBrowseCheck..<SNR>35_NetrwBrowse..<SNR>35_PerformListing..<SNR>35_NetrwWideListing:
>> line 62:
>> E31: No such mapping
>> Error detected while processing function
>>
>> netrw#Explore..netrw#Explore..netrw#LocalBrowseCheck..<SNR>35_NetrwBrowse..<SNR>35_PerformListing..<SNR>35_NetrwWideListing:
>> line 65:
>> E31: No such mapping
>> line 203:
>> E117: Unknown function: Decho
>>
> <snip>
>
> Sorry about that; I left some debugging calls enabled. I've put v151d back
> on my website, this time with debugging disabled.
>
>
> Regards,
> C 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/groups/opt_out.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Mon, Feb 24, 2014 at 3:50 PM, Charles Campbell
<Charles.E.Campbell@nasa.gov> wrote:
> A Loumiotis wrote:
>>
>> On Fri, Feb 21, 2014 at 8:04 PM, Charles Campbell
>> <Charles.E.Campbell@nasa.gov> wrote:
>>>
>>> A Loumiotis wrote:
>>>>
>>>> I have some issues with exploring a folder for which the name contains
>>>> a space and I use command line completion. For example:
>>>>
>>>> :Exp e:\m<tab>
>>>>
>>>> expands to
>>>>
>>>> :Exp e:\My\ Documents
>>>>
>>>> but it does not create a list of the folder contents.
>>>>
>>>> But if I manually delete the backward slash:
>>>>
>>>> :Exp e:\My Documents
>>>>
>>>> then it works.
>>>>
>>>> On the other hand if I use:
>>>>
>>>> :e e:\m<tab>
>>>>
>>>> it expands to
>>>>
>>>> :e e:\My\ Documents
>>>>
>>>> and it works as expected, ie, it lists the contents of the directory
>>>> immediately without having to delete the backward slashes that escape
>>>> spaces as I have to do with the :Exp command.
>>>>
>>>> I use gVim on Windows XP 32 bit.
>>>>
>>> Hello!
>>>
>>> Please try v151d of netrw, available from my website:
>>> http://www.drchip.org/astronaut/vim/index.html#NETRW
>>>
>>> Regards,
>>> C 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/groups/opt_out.
>>
>>
>> Thanks a lot for your help.
>> It works but I now get a list of error messages before I see the
>> contents of any folder:
>>
>> For example if I do:
>>
>> :Exp e:\My\ Documents
>>
>> I get the following errors and then I see correctly the folder contents:
>>
>> Error detected while processing function netrw#Explore:
>> line 1:
>> E117: Unknown function: Dfunc
>> line 18:
>> E117: Unknown function: Decho
>> line 24:
>> E117: Unknown function: Decho
>> line 29:
>> E117: Unknown function: Decho
>> Error detected while processing function netrw#Explore..netrw#Explore:
>> line 1:
>> E117: Unknown function: Dfunc
>> line 18:
>> E117: Unknown function: Decho
>> line 24:
>> E117: Unknown function: Decho
>> line 34:
>> E117: Unknown function: Decho
>> line 92:
>> E117: Unknown function: Decho
>> line 97:
>> E117: Unknown function: Decho
>> line 114:
>> E117: Unknown function: Decho
>> line 116:
>> E117: Unknown function: Decho
>> line 129:
>> E117: Unknown function: Decho
>> line 135:
>> E117: Unknown function: Decho
>> line 178:
>> E117: Unknown function: Decho
>> line 183:
>> E117: Unknown function: Decho
>> line 201:
>> E117: Unknown function: Decho
>> "" [Not edited] --No lines in buffer--
>> "" --No lines in buffer--
>> "" --No lines in buffer--
>> Pattern not found: ^$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.h$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.c$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.cpp$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.o$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.obj$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.info$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \.bak$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Pattern not found: \~$
>> Pattern not found: ^\d\{3}ÿ\d\{3}\/
>> Error detected while processing function
>>
>> netrw#Explore..netrw#Explore..netrw#LocalBrowseCheck..<SNR>35_NetrwBrowse..<SNR>35_PerformListing..<SNR>35_NetrwWideListing:
>> line 62:
>> E31: No such mapping
>> Error detected while processing function
>>
>> netrw#Explore..netrw#Explore..netrw#LocalBrowseCheck..<SNR>35_NetrwBrowse..<SNR>35_PerformListing..<SNR>35_NetrwWideListing:
>> line 65:
>> E31: No such mapping
>> line 203:
>> E117: Unknown function: Decho
>>
> <snip>
>
> Sorry about that; I left some debugging calls enabled. I've put v151d back
> on my website, this time with debugging disabled.
>
>
> Regards,
> C 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/groups/opt_out.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
How to edit a macro?
Dear Vim experts,
after recording a macro I realized that I forgot to specify the
register I yanked into.
The macro in register q was
/^[^#].*<-.*GO:\d\{7\}^My/)^M
and matches lines like the following line 1
1 light <- c( 'GO:1234567',
2 'GO:7162635', 'GO:4536271',
3 'GO:7654321' )
the macro yanks everything up to, and including, line 3.
The problem is, that I want to specify the register the content is yanked to.
So I tried
:let @q='/^[^#].*<-.*GO:\d\{7\}^M"Gy/)^M'
But the ^M form a problem. The macro is not executed correctly.
Does anyone know how to solve this?
Cheers!
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
after recording a macro I realized that I forgot to specify the
register I yanked into.
The macro in register q was
/^[^#].*<-.*GO:\d\{7\}^My/)^M
and matches lines like the following line 1
1 light <- c( 'GO:1234567',
2 'GO:7162635', 'GO:4536271',
3 'GO:7654321' )
the macro yanks everything up to, and including, line 3.
The problem is, that I want to specify the register the content is yanked to.
So I tried
:let @q='/^[^#].*<-.*GO:\d\{7\}^M"Gy/)^M'
But the ^M form a problem. The macro is not executed correctly.
Does anyone know how to solve this?
Cheers!
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Monday, February 24, 2014
Re: errorformat/cexpr bug?
On 24 February 2014, Aaron Bohannon <aaron678@gmail.com> wrote:
> Sorry, I was a bit hasty with my wording. I do understand that
> the multiignore flag is on the implementation side of things. And
> I appreciate you tracking down the source of the inconsistency
> I noticed. I could recompile vim with your change, but at this
> point, I'm not sure what I would learn because I'm no longer what is
> *supposed* to be happening.
>
> As much as I'd like to believe otherwise, I have an ever-growing
> suspicion that the errorformat mechanism is in fact just a pile of
> ad-hoc hacks without any consistent meaning. And if that's true,
> it's not a good use of my time to try to sort it out. I'm better off
> writing a special-purpose tool from scratch.
No disagreement here. In my opinion too, errorformat is a
convoluted, poorly documented, inflexible, unforgiving, impossible to
debug, inconsistent tool, that has been broken since the beginning
of time. Using it certainly does seem to come with a distinctively
masochistic air attached to it. However, useless this tool isn't. I
happen to be the maintainer of a plugin that parses the output of ~140
different syntax checkers for ~80 languages, and every single one of
those rely on errorformat to do its job. And, believe it or not, they
actually work pretty well.
Is the world ready for a sane errorformat mechanism? Sure; it has
been so for quite a while now. That mechanism is not here yet though.
/lcd
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Sorry, I was a bit hasty with my wording. I do understand that
> the multiignore flag is on the implementation side of things. And
> I appreciate you tracking down the source of the inconsistency
> I noticed. I could recompile vim with your change, but at this
> point, I'm not sure what I would learn because I'm no longer what is
> *supposed* to be happening.
>
> As much as I'd like to believe otherwise, I have an ever-growing
> suspicion that the errorformat mechanism is in fact just a pile of
> ad-hoc hacks without any consistent meaning. And if that's true,
> it's not a good use of my time to try to sort it out. I'm better off
> writing a special-purpose tool from scratch.
No disagreement here. In my opinion too, errorformat is a
convoluted, poorly documented, inflexible, unforgiving, impossible to
debug, inconsistent tool, that has been broken since the beginning
of time. Using it certainly does seem to come with a distinctively
masochistic air attached to it. However, useless this tool isn't. I
happen to be the maintainer of a plugin that parses the output of ~140
different syntax checkers for ~80 languages, and every single one of
those rely on errorformat to do its job. And, believe it or not, they
actually work pretty well.
Is the world ready for a sane errorformat mechanism? Sure; it has
been so for quite a while now. That mechanism is not here yet though.
/lcd
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: errorformat/cexpr bug?
Sorry, I was a bit hasty with my wording. I do understand that the multiignore flag is on the implementation side of things. And I appreciate you tracking down the source of the inconsistency I noticed. I could recompile vim with your change, but at this point, I'm not sure what I would learn because I'm no longer what is *supposed* to be happening.
As much as I'd like to believe otherwise, I have an ever-growing suspicion that the errorformat mechanism is in fact just a pile of ad-hoc hacks without any consistent meaning. And if that's true, it's not a good use of my time to try to sort it out. I'm better off writing a special-purpose tool from scratch.
On Monday, February 24, 2014 2:05:42 PM UTC-8, LCD 47 wrote:
> On 24 February 2014, Aaron Bohannon <aaron678@gmail.com> wrote:
>
> > Thanks for the reply. I find this "multiignore" flag very fishy
>
> > because none of the documentation I have read would imply the
>
> > existence of such a flag. (Why wouldn't "multi" and "ignore" be
>
> > orthogonal notions?)
>
>
>
> The "multiignore" flag I was referring to is a variable in the code,
>
> not something that would make sense for you as an end user.
>
>
>
> > Interestingly, in trying to further reverse-engineer meaning by
>
> > testing behavior, I stumbled on conclusive evidence that something
>
> > here is clearly broken and not simply difficult to understand.
>
> [...]
>
>
>
> Like I said, there's a bug, a successfully matched %-G<mumble> will
>
> prevent subsequent %C<mumble> (and other things) from working. If you
>
> know how to compile Vim yourself, please try the patch I posted in my
>
> previous message. It supposedly fixes the bug, see if things make more
>
> sense after that. Not sure what else I could tell you at this point.
>
>
>
> /lcd
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
As much as I'd like to believe otherwise, I have an ever-growing suspicion that the errorformat mechanism is in fact just a pile of ad-hoc hacks without any consistent meaning. And if that's true, it's not a good use of my time to try to sort it out. I'm better off writing a special-purpose tool from scratch.
On Monday, February 24, 2014 2:05:42 PM UTC-8, LCD 47 wrote:
> On 24 February 2014, Aaron Bohannon <aaron678@gmail.com> wrote:
>
> > Thanks for the reply. I find this "multiignore" flag very fishy
>
> > because none of the documentation I have read would imply the
>
> > existence of such a flag. (Why wouldn't "multi" and "ignore" be
>
> > orthogonal notions?)
>
>
>
> The "multiignore" flag I was referring to is a variable in the code,
>
> not something that would make sense for you as an end user.
>
>
>
> > Interestingly, in trying to further reverse-engineer meaning by
>
> > testing behavior, I stumbled on conclusive evidence that something
>
> > here is clearly broken and not simply difficult to understand.
>
> [...]
>
>
>
> Like I said, there's a bug, a successfully matched %-G<mumble> will
>
> prevent subsequent %C<mumble> (and other things) from working. If you
>
> know how to compile Vim yourself, please try the patch I posted in my
>
> previous message. It supposedly fixes the bug, see if things make more
>
> sense after that. Not sure what else I could tell you at this point.
>
>
>
> /lcd
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: From 7.4.135 to 7.4.182 now leaves backup files behind
On Monday, February 24, 2014 4:48:10 PM UTC-6, Ti Strga wrote:
> I've been happily using 7.4.135 under Cygwin on Windows 7 since its
>
> release. Today I installed (via Cygwin's own "setup.exe"
>
> pseudo-package-manager) 7.4.182, and started running into problems.
>
>
>
> Specifically, after editing files, I'm find Vim swap/backup/something
>
> files left behind. They're binary files that start with "VIM", and
>
> they all follow the same naming scheme: for file FOO, they're left
>
> behind in ".FOO.un~".
>
>
>
> Nothing in my .vimrc has changed. Both "backup" and "writebackup" are
>
> off on the computer in question. I tried editing with -Vtest, but the
>
> "test" file didn't have any particular error messages or other output
>
> (lots and lots of chdirs....).
>
>
>
> Reverting to 7.4.135 makes the spurious swap/backup/?? files go away.
>
>
>
> I looked through ftp://ftp.vim.org/pub/vim/patches/7.4/README and none
>
> of the entries between 135 and 182 jumped out at me as obvious
>
> candidates for what's changed. I'm expecting that this is something I
>
> can work around in my .vimrc, once I know what's causing it:
>
>
>
> - what are the .un~ files?
>
> - what vim settings control them?
>
> - what changed in the latest patches to toggle the behavior?
>
Those are "undo files". They store your undo tree when you exit Vim, so that when you go back into Vim, undo/redo is still available for that file.
This is the "persistent undo" feature of Vim introduced in 7.4.
What might have changed? The vimrc_example.vim file distributed with Vim changed recently to turn the 'undofile' option on. You are probably sourcing that file in your own vimrc.
You can either turn off 'undofile' to make these files go away, or you can use the 'undodir' option to control where they get saved.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> I've been happily using 7.4.135 under Cygwin on Windows 7 since its
>
> release. Today I installed (via Cygwin's own "setup.exe"
>
> pseudo-package-manager) 7.4.182, and started running into problems.
>
>
>
> Specifically, after editing files, I'm find Vim swap/backup/something
>
> files left behind. They're binary files that start with "VIM", and
>
> they all follow the same naming scheme: for file FOO, they're left
>
> behind in ".FOO.un~".
>
>
>
> Nothing in my .vimrc has changed. Both "backup" and "writebackup" are
>
> off on the computer in question. I tried editing with -Vtest, but the
>
> "test" file didn't have any particular error messages or other output
>
> (lots and lots of chdirs....).
>
>
>
> Reverting to 7.4.135 makes the spurious swap/backup/?? files go away.
>
>
>
> I looked through ftp://ftp.vim.org/pub/vim/patches/7.4/README and none
>
> of the entries between 135 and 182 jumped out at me as obvious
>
> candidates for what's changed. I'm expecting that this is something I
>
> can work around in my .vimrc, once I know what's causing it:
>
>
>
> - what are the .un~ files?
>
> - what vim settings control them?
>
> - what changed in the latest patches to toggle the behavior?
>
Those are "undo files". They store your undo tree when you exit Vim, so that when you go back into Vim, undo/redo is still available for that file.
This is the "persistent undo" feature of Vim introduced in 7.4.
What might have changed? The vimrc_example.vim file distributed with Vim changed recently to turn the 'undofile' option on. You are probably sourcing that file in your own vimrc.
You can either turn off 'undofile' to make these files go away, or you can use the 'undodir' option to control where they get saved.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Subscribe to:
Posts (Atom)