Rebbe Malachi: August 2009

Monday, August 31, 2009

Re: goto line depending on exit code of filter

On 22/08/09 16:56, bill lam wrote:
>
> On Sat, 22 Aug 2009, Tim Chase wrote:
>> Though it's a bit of a horrible abuse, you can do
>>
>> if v:shell_error> 0 | exec v:shell_error | endif
>>
>> which exploits the fact that an ex command of just a number means
>> to go to that line. Granted, the range of exit codes may limit
>> you to a pretty small range (1-127, IIRC), so you can't jump to a
>> line beyond this max. But it's what you asked for :)
>
> Thanks Tim and Ben! "exec number" does the trick.
> I got a pretty print for my source files, when there is syntax error,
> I made it exit with an error code equal to that line number. I tried
> and found vim can jump to lines beyond 4000.
>

Vim can jump to any line that it can count, the problem is having your
external program generate the required number as a return code: IIRC,
return codes are limited to one byte, and those above 127 may have a
special meaning (generated by the OS maybe).

In bash,

foobar
bash: foobar: command not found
echo $?

returns 127, for instance.

Depending on what you exactly want, you could also write it as

if v:shell_error | exe v:shell_error | endif

if v:xhell_error | exe (v:shell_error % 256) | endif

etc.

Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
117. You are more comfortable typing in html.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Re: Use terminal colors in GUI Vim?

Hi Gary!

On Mo, 31 Aug 2009, Gary Johnson wrote:

> g:colors_name is set when :colorscheme is executed, if the
> colorscheme file is properly written. If vim says that
> g:colors_name is undefined, then :colorscheme has not been executed.
>

Or the colorscheme did not set g:colors_name, which would be a bug.
(g:colors_name has to be defined by the colorscheme).

#v+
~$ grep g:colors_name ~/.vim/colors/*.vim
.vim/colors/black_angus.vim:let g:colors_name = "black_angus"
.vim/colors/cb256.vim:let g:colors_name="cb256"
.vim/colors/desert256.vim:let g:colors_name="desert256"
.vim/colors/dw_blue.vim:let g:colors_name="dw_blue"
.vim/colors/maroloccio.vim:let g:colors_name="maroloccio"
.vim/colors/peaksea.vim:let g:colors_name = expand("<sfile>:t:r")
.vim/colors/sean.vim:let g:colors_name = "sean"
.vim/colors/transparent.vim:let g:colors_name="transparent"
.vim/colors/zenburn.vim:let g:colors_name="zenburn"
#v-

regards,
Christian

Re: separate one file into many files

Thanks Tony,

I did name it with the extension .vim, and I did restart vim before typing
:scriptnames

I will end up trying what Christian suggested (loading them manually) the
next time I get to a computer that has vim installed.

Thank you.

Tony Mechelynck-2 wrote:
>
>
> On 20/08/09 21:11, drlatex wrote:
>>
>>
>> Thank you very much. That makes a lot more sense.
>>
>> I'm acutally using vim in windows, and I did add that plugin to the
>> location
>> where all the other plugins are located, but according to :scriptnames,
>> vim
>> doens't automatically load the one that I added (the one you wrote) ...
>> it
>> loads all the other ones in that directory except for the added one.
>>
>> But nevertheless, I was able to get my job done. I used csplit to split
>> the
>> file into its 500 constituent files. Then I used a command in unix with a
>> for loop to rename them appropriately.
>>
>> Thank you very much once again. I really appreciate all of your help and
>> taking the time to respond to me. And it was good that I learned about
>> the
>> plugins, I'm sure that will come in useful another time.
>
> You did restart Vim after dropping the plugin in (whatever)/plugin/
> (where (whatever) is some directory in 'runtimepath' other than
> $VIMRUNTIME), didn't you?
>
> Global plugins are loaded only at startup. If you add one while Vim is
> already running, it won't "see" it. Also, all Vim scripts other than
> vimrc (, .vimrc, _vimrc) and gvimrc (, .gvimrc, _gvimrc) must have the
> .vim extension ta the end of their name.
>
>
> Best regards,
> Tony.
> --
> Q: How many IBM cpu's does it take to do a logical right shift?
> A: 33. 1 to hold the bits and 32 to push the register.
>
> >
>
>

--
View this message in context: http://www.nabble.com/separate-one-file-into-many-files-tp24854914p25234051.html
Sent from the Vim - General mailing list archive at Nabble.com.

Re: Use terminal colors in GUI Vim?

Nathan Neff 写道:
> Hello,
>
> I'm using a custom Xdefaults file for my terminal (urxvt), and I like
> how Vim looks
> in the terminal.
>
> Is there an easy way to make a colorscheme file for Gvim that makes Gvim look
> like my terminal colors?

Guess you had manually defined Color0 to Color15 in Xdefaults?

I don't think there is an easy way to convert that into gvim scheme
unless someone had write script for it.

You may need to design a gui colorscheme file. Design your own gui
colorscheme file isn't very hard, you can start with your moria.vim and
change the colors.

It takes some time to know how to write your own colorscheme file, but
we'll be using vim in the rest of our life and I think it worth the cost.

Re: Use terminal colors in GUI Vim?

I used ":hi + copy/paste" to create a color scheme that reflects my
xterm's default colors.

Pleas find attached the color scheme file I created manually via
copy/paste and a few substitutions + the relevant stanza of my
.Xdefaults file so all you need to do is replace my terminal color
definitions by yours.

:%s/#iiiiii/#jjjjjj/g (e.g.)

Would be nice if someone could suggest an automated solution, though.

:-/

Gen-Paul.

Re: separate one file into many files

On 20/08/09 21:11, drlatex wrote:
>
>
> Thank you very much. That makes a lot more sense.
>
> I'm acutally using vim in windows, and I did add that plugin to the location
> where all the other plugins are located, but according to :scriptnames, vim
> doens't automatically load the one that I added (the one you wrote) ... it
> loads all the other ones in that directory except for the added one.
>
> But nevertheless, I was able to get my job done. I used csplit to split the
> file into its 500 constituent files. Then I used a command in unix with a
> for loop to rename them appropriately.
>
> Thank you very much once again. I really appreciate all of your help and
> taking the time to respond to me. And it was good that I learned about the
> plugins, I'm sure that will come in useful another time.

You did restart Vim after dropping the plugin in (whatever)/plugin/
(where (whatever) is some directory in 'runtimepath' other than
$VIMRUNTIME), didn't you?

Global plugins are loaded only at startup. If you add one while Vim is
already running, it won't "see" it. Also, all Vim scripts other than
vimrc (, .vimrc, _vimrc) and gvimrc (, .gvimrc, _gvimrc) must have the
.vim extension ta the end of their name.

Best regards,
Tony.
--
Q: How many IBM cpu's does it take to do a logical right shift?
A: 33. 1 to hold the bits and 32 to push the register.

improving the :join command

Hi,

as you may know, :join suffers from a serious performance issue, when
joining many lines ( in the order of 10 thousands or more lines).
Therefore I have written the following plugin¹, which tries to improve
the performance when joining lines.

I have been trying to make the plugin behave exactly like the :join
command, therefore I'd like to ask to test, whether it works like
:join.

I hope this helps until the patch at the vim_extend repository get's
into vim mainline.

¹)http://www.vim.org/scripts/script.php?script_id=2766

regards,
Christian

Re: Use terminal colors in GUI Vim?

Nathan Neff wrote:

[..]

>>> What does this tell you?
>>>
>>> :echo g:colors_name
>> I'm using "moria" in Gvim. I'd like to make Gvim have the same colors as
>> vim does in my terminal. I don't know how to convert terminal colors
>> into a Gvim color scheme.

> In addition, when I type :echo g:colors_name in terminal vim, I get
> "Undefined variable: g:colors_name", which makes sense because
> g:colors_name only applies to Gvim.

No.

Type the following in terminal vim:

:colorscheme <space> <Tab>

You will be prompted for different color schemes in succession.

Select one by hitting <Enter>

Then:

:echo g:colors_name

The name of the color scheme that you selected is displayed.

My _guess_ is that you are using the "default" color scheme, which I
believe is hard-coded in vim and the trouble is that in this particular
case the colors_name global variable is not se.

I have not looked at the code, so someone correct me if that is not the
case.

So, I'm not sure where you can go from there. Maybe check if there is a
plugin that lets you dump the "default" color scheme to a colorscheme
file..?

Not sure that's even possible.

Obviously, once you have a copy of the "default" color scheme in a file,
porting it to gvim is trivial.

Otherwise, you could start terminal vim, use the :hi command to display
the current syntax highlighting settings, copy/paste them to a file, and
use these definitions to build a gvim color scheme.

Gen_Paul.

Re: Use terminal colors in GUI Vim?

On 2009-08-31, Nathan Neff wrote:

> In addition, when I type :echo g:colors_name in terminal vim, I get
> "Undefined variable: g:colors_name", which makes sense because
> g:colors_name only applies to Gvim.

Why do you think g:colors_name applies only to gvim?

g:colors_name is set when :colorscheme is executed, if the
colorscheme file is properly written. If vim says that
g:colors_name is undefined, then :colorscheme has not been executed.

Regards,
Gary

Re: Use terminal colors in GUI Vim?

On Mon, Aug 31, 2009 at 3:28 PM, Nathan Neff<nathan.neff@gmail.com> wrote:
> On Mon, Aug 31, 2009 at 1:32 PM, Patrick Gen-Paul<pgenpaul@gmail.com> wrote:
>>
>> Nathan Neff wrote:
>>> I define my color scheme in .Xdefaults, like this, for urxvt:
>>
>> [..]
>>
>>> I don't know if that's what you're asking about. I don't know how
>>> terminal vim interacts with the colors of urxvt, though.
>>
>> I meant a _vim_ color scheme.
>>
>> :h colorscheme
>>
>> In particular: "For info about writing a colorscheme file .." since, to
>> the best of my knowledge, this is what you need to do.
>>
>> What does this tell you?
>>
>> :echo g:colors_name
>
> I'm using "moria" in Gvim. I'd like to make Gvim have the same colors as
> vim does in my terminal. I don't know how to convert terminal colors
> into a Gvim color scheme.

In addition, when I type :echo g:colors_name in terminal vim, I get
"Undefined variable: g:colors_name", which makes sense because
g:colors_name only applies to Gvim.

--Nate

Re: Use terminal colors in GUI Vim?

On Mon, Aug 31, 2009 at 1:32 PM, Patrick Gen-Paul<pgenpaul@gmail.com> wrote:
>
> Nathan Neff wrote:
>> I define my color scheme in .Xdefaults, like this, for urxvt:
>
> [..]
>
>> I don't know if that's what you're asking about. I don't know how
>> terminal vim interacts with the colors of urxvt, though.
>
> I meant a _vim_ color scheme.
>
> :h colorscheme
>
> In particular: "For info about writing a colorscheme file .." since, to
> the best of my knowledge, this is what you need to do.
>
> What does this tell you?
>
> :echo g:colors_name

I'm using "moria" in Gvim. I'd like to make Gvim have the same colors as
vim does in my terminal. I don't know how to convert terminal colors
into a Gvim color scheme.

Thanks,
--Nate

Re: Save through to remote server

Ernest Obusek wrote:
> I'm trying to switch back to vim after years with jEdit, but I need to
> get a set of things working before I can use vim productively. One
> thing I need is to make it so that when I save a file, it scp's it to
> a remote server. I imagine a script could do this, but I have no idea
> how to hook that in to the save command. How can this be done?
:w scp://hostname/filename

You can also :e scp://hostname/filename ... :w

That's assuming that you have
filetype plugin on
in your .vimrc .

Regards,
Chip Campbell

Re: expand variable to command line

On 2009-08-31, Aarto Matti wrote:
> Hello,
>
> How to print an expanded variable into vim command line? For some
> reason I would like to map e.g. F12 to complete edit command with vim
> user files path. I would do something like:
>
> :map <F12> :edit expand($VIM)
>
> What it prints is
>
> :edit expand($VIM)
>
> and I want
>
> :edit /usr/share/vim

Just use this:

:map <F12> :edit $VIM

If you want to actually edit $VIM and not add more to the path
before executing that command, use this:

:map <F12> :edit $VIM<CR>

Regards,
Gary

Re: Save through to remote server

:help netrw-start

On Mon, Aug 31, 2009 at 4:49 PM, Ernest Obusek <ernest@willowfalls.net> wrote:

I'm trying to switch back to vim after years with jEdit, but I need to get a set of things working before I can use vim productively. One thing I need is to make it so that when I save a file, it scp's it to a remote server. I imagine a script could do this, but I have no idea how to hook that in to the save command. How can this be done?

Thanks,

Ernest

--
Christophe-Marie Duquesne

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Re: Use terminal colors in GUI Vim?

Nathan Neff wrote:
> I define my color scheme in .Xdefaults, like this, for urxvt:

[..]

> I don't know if that's what you're asking about. I don't know how
> terminal vim interacts with the colors of urxvt, though.

I meant a _vim_ color scheme.

:h colorscheme

In particular: "For info about writing a colorscheme file .." since, to
the best of my knowledge, this is what you need to do.

What does this tell you?

:echo g:colors_name

Gen-Paul.

Re: expand variable to command line

> How to print an expanded variable into vim command line? For some
> reason I would like to map e.g. F12 to complete edit command with vim
> user files path. I would do something like:
>
> :map <F12> :edit expand($VIM)
>
> What it prints is
>
> :edit expand($VIM)
>
> and I want
>
> :edit /usr/share/vim

Several ways:

:map <f12> :edit <c-r>=expand($VIM)<cr><cr>
:map <f12> :exec "edit ".expand($VIM)<cr>

-tim

Re: globpath with an expression

On Mon, Aug 31, 2009 at 10:19 AM, Brett
Stahlman<brettstahlman@comcast.net> wrote:
...
> The globpath function does not take a regular expression, but rather a
> glob pattern, such as would be accepted by glob(). To see what
> metacharacters are significant...
> :help wildcard

Thanks Brett.

Now I suck everything back with a * and then use a filter() for the
regex on the list afterwards.

Dave

Re: Use terminal colors in GUI Vim?

I define my color scheme in .Xdefaults, like this, for urxvt:

urxvt.scrollTtyOutput: 0
urxvt.scrollTtyKeypress: 1
urxvt.background: #000000
urxvt.foreground: #9a9a9a
urxvt.color0: #000000
urxvt.color1: #af0000
urxvt.color2: #00af00
urxvt.color3: #afaf00
urxvt.color4: #00ff00
urxvt.color5: #af00af
urxvt.color6: #00afaf
urxvt.color7: #9a9a9a
urxvt.color8: #5f5f5f
urxvt.color9: #d70000
urxvt.color10: #00d700
urxvt.color11: #d7d700
urxvt.color12: #00FF00
urxvt.color13: #d700d7
urxvt.color14: #00d7d7
urxvt.color15: #d7d7d7

I don't know if that's what you're asking about. I don't know how
terminal vim interacts with the colors of urxvt, though.

On Mon, Aug 31, 2009 at 12:06 PM, Patrick Gen-Paul<pgenpaul@gmail.com> wrote:
>
> Nathan Neff wrote:
>> Hello,
>>
>> I'm using a custom Xdefaults file for my terminal (urxvt), and I like
>> how Vim looks
>> in the terminal.
>>
>> Is there an easy way to make a colorscheme file for Gvim that makes Gvim look
>> like my terminal colors?
>>
>> I've seen quite a few discussions on how to go from Gvim --> Terminal,
>> but not the other
>> way around.
>
> Difficult to help without a bit more detail about your context.
>
> What color scheme - if any - are you using in the terminal?
>
> I could be wrong, but this sounds like you could duplicate the color
> scheme file, replace all instances of ctermfg and ctermbg by
> respectively guifg and guibg, save the file.. and you're done (?)
>
> Gen-Paul.
>
> >
>

Re: Use terminal colors in GUI Vim?

Nathan Neff wrote:
> Hello,
>
> I'm using a custom Xdefaults file for my terminal (urxvt), and I like
> how Vim looks
> in the terminal.
>
> Is there an easy way to make a colorscheme file for Gvim that makes Gvim look
> like my terminal colors?
>
> I've seen quite a few discussions on how to go from Gvim --> Terminal,
> but not the other
> way around.

Difficult to help without a bit more detail about your context.

What color scheme - if any - are you using in the terminal?

I could be wrong, but this sounds like you could duplicate the color
scheme file, replace all instances of ctermfg and ctermbg by
respectively guifg and guibg, save the file.. and you're done (?)

Gen-Paul.

Re: vim 7.1 - sh.vim syntax file - unwarranted syntax error detected.

John Little wrote:
>> console-screen.kbd.sh
>
> With vim 7.2.245, the highlighting of line 30 is ok but fails on and
> after line 32, even with the very latest syntax file (v108) from the
> maintainer's website (http://mysite.verizon.net/astronaut/vim/
> index.html#vimlinks_syntax). It doesn't like the escaped double quote
> after the square bracket. The following two line shell script
> exhibits the problem:
>
> echo [ \"Lorem
> echo ipsum
>
> Dr Chip will likely see this thread, I hope this helps him, should he
> be inclined to fix it.

I had downloaded the latest version of the syntax file before I posted
and indeed it doesn't make any difference.

I guess I can always send him an email to his contact address in sh.vim
if he does not respond within the next few days.

Where this particular linux init.d script is concerned, and especially
since the line that's affected is very near the beginning, it pretty
much defeats the purpose of syntax highlighting - as time allows, I'm
sure he will want to come up with a fix.

Gen-Paul.

Re: Starting vim :help full screen

Tim Chase wrote:
>> When I type ":help" on an empty vim screen - such as a new tab for
>> instance, vim automatically splits the screen.
>>
>> I proceed to issue a Ctrl-W O to remove the empty half screen, no big deal.
>>
>> Is there any "native" way I could start vim's help full-screen - without
>> coding a macro and mapping it to a key combo - I don't think it's worth
>> bloating my interface further for something this trivial.
>
> A couple options occur to me -- two prefix options, and one
> post-processing idea:
>
> To open the help in its own tab:
>
> :tab help some_topic_to_find
>
> To open the help in the current non-modified empty buffer:
>
> :set bt=help | help some_topic_to_find
>
> Finally, one could create an autocmd for help-type files (my
> autocmd creation is a bit rusty, so you'd have to experiment on
> your own, or somebody else may step in) that forces an ":only" on
> the help window (though it might grouse at you if there are
> modifications in the to-be-closed windows).

Thanks for the tips.

Gen-Paul.

Re: How does the python omnicomplete functionality work with vim?

On Sun, Aug 30, 2009 at 4:15 PM, Mishail<mishail.mishail@gmail.com> wrote:
>
> Have you tried pythoncomplete script (http://www.vim.org/scripts/
> script.php?script_id=1542) ?

I have been using 0.8 version of this plugin and don't find it able to
complete most of the times.
--
HTH,
Hari
> >
>

au_exists bug, was Re: Test Existence of Autocommand?

On Tue, Aug 25, 2009 at 11:38 AM, Ben Fritz<fritzophrenic@gmail.com> wrote:
>> On Fri, Aug 14, 2009 at 6:38 PM, Edward Beach<beach9...@hotmail.com> wrote:
>> > I'm trying to write a script that will toggle an autocommand on/off
>> > and I'm looking for a function to return it's existence. I've found
>> > the built-in exists function and from the help it gives me this:
>> > #group#event autocommand defined for this group and event.
>> > So from my command line I enter in the following
>> > :aug TestGroup | aug END | echo exists("#TestGroup#BufWritePost")
>> > and it comes back 1 -- but shouldn't it be 0 since I haven't created a
>> > BufWritePost event and since
>> > :au TestGroup
>> > returns nothing?
>>
>> It looks like the #group#event code doesn't check for an autocommand
>> for that event being defined *within* the group, just whether both the
>> group and the autocommand exist. The #group#event#pattern does check
>> for an autocommand defined within the specified group, though, so that
>> may be helpful to you.

> Since this is a patch for some VERY unexpected behavior, I'm cc'ing
> vim_dev where such things are normally discussed.
>
> My opinion is that this is a bug, if it can be reliably reproduced. I
> can't imagine any situation where the described behavior would be
> helpful.

Here's a probably better patch, and a test case to show the behavior I
expect from exists() with respect to autocommands:

diff --git a/src/fileio.c b/src/fileio.c
index a9552b5..5da1a96 100644
--- a/src/fileio.c
+++ b/src/fileio.c
@@ -9498,15 +9498,10 @@ au_exists(arg)
ap = first_autopat[(int)event];
if (ap == NULL)
goto theend;
- if (pattern == NULL)
- {
- retval = TRUE;
- goto theend;
- }

/* if pattern is "<buffer>", special handling is needed which
uses curbuf */
/* for pattern "<buffer=N>, fnamecmp() will work fine */
- if (STRICMP(pattern, "<buffer>") == 0)
+ if (pattern != NULL && STRICMP(pattern, "<buffer>") == 0)
buflocal_buf = curbuf;

/* Check if there is an autocommand with the given pattern. */
@@ -9515,9 +9510,10 @@ au_exists(arg)
/* For buffer-local autocommands, fnamecmp() works fine. */
if (ap->pat != NULL && ap->cmds != NULL
&& (group == AUGROUP_ALL || ap->group == group)
- && (buflocal_buf == NULL
- ? fnamecmp(ap->pat, pattern) == 0
- : ap->buflocal_nr == buflocal_buf->b_fnum))
+ && (pattern == NULL
+ || (buflocal_buf == NULL
+ ? fnamecmp(ap->pat, pattern) == 0
+ : ap->buflocal_nr == buflocal_buf->b_fnum)))
{
retval = TRUE;
break;

unpatched testcase results:

$ /usr/bin/vim -u ~/testcase.vim
BufEnter is a valid event (should be true) : 1
BufEnter defined generally (should be false) : 0
BufEnter defined generally (should be true) : 1
BufEnter defined in 'auexists' group (should be false) : 1
BufEnter defined in 'auexists' group (should be true) : 1
BufEnter defined for *.test (should be false) : 0
BufEnter defined for *.test (should be true) : 1
BufEnter defined for local buffer (should be false) : 0
BufEnter defined for local buffer (should be true) : 1

patched testcase results:

$ vim -u ~/testcase.vim
BufEnter is a valid event (should be true) : 1
BufEnter defined generally (should be false) : 0
BufEnter defined generally (should be true) : 1
BufEnter defined in 'auexists' group (should be false) : 0
BufEnter defined in 'auexists' group (should be true) : 1
BufEnter defined for *.test (should be false) : 0
BufEnter defined for *.test (should be true) : 1
BufEnter defined for local buffer (should be false) : 0
BufEnter defined for local buffer (should be true) : 1

testcase.vim:

augroup auexists
augroup END
echomsg "BufEnter is a valid event (should be true) : " exists("##BufEnter")
echomsg "BufEnter defined generally (should be false) : " exists("#BufEnter")
au BufEnter * let g:entered=1
echomsg "BufEnter defined generally (should be true) : " exists("#BufEnter")
echomsg "BufEnter defined in 'auexists' group (should be false) : "
exists("#auexists#BufEnter")
augroup auexists
au BufEnter * let g:entered=1
augroup END
echomsg "BufEnter defined in 'auexists' group (should be true) : "
exists("#auexists#BufEnter")
echomsg "BufEnter defined for *.test (should be false) : "
exists("#BufEnter#*.test")
au BufEnter *.test let g:entered=1
echomsg "BufEnter defined for *.test (should be true) : "
exists("#BufEnter#*.test")
silent edit testfile.test
echomsg "BufEnter defined for local buffer (should be false) : "
exists("#BufEnter#<buffer>")
au BufEnter <buffer> let g:entered=1
echomsg "BufEnter defined for local buffer (should be true) : "
exists("#BufEnter#<buffer>")

Thank you,

bob

Re: Vim Suggestion: adapting tw to displayed with (vs. termwidth) if numbering

On Aug 28, 5:13 pm, Linda W <v...@tlinx.org> wrote:
> Suggesting [programmatically, :-) ]:
>
> When (vimoption(number) == true)) {
> when ("one uses text autoformat" (aka 'gqap')) {
> setlocal tw=disp_width'(dflt==0)) /' - nuw'(vimdflt=4,compat=8) /'
> }
>
> }
>

I'm sorry, I don't understand. Is this different than the 'wrapmargin'
option?
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

expand variable to command line

Hello,

How to print an expanded variable into vim command line? For some
reason I would like to map e.g. F12 to complete edit command with vim
user files path. I would do something like:

:map <F12> :edit expand($VIM)

What it prints is

:edit expand($VIM)

and I want

:edit /usr/share/vim

--
Aarto

Save through to remote server

I’m trying to switch back to vim after years with jEdit, but I need to get a set of things working before I can use vim productively. One thing I need is to make it so that when I save a file, it scp’s it to a remote server. I imagine a script could do this, but I have no idea how to hook that in to the save command. How can this be done?

Thanks,

Ernest

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Re: Use VIM to perform text manipulation on file (like sed/awk)

Thank you very much Christian. That was a very detailed and helpful answer!

Re: globpath with an expression

On Aug 31, 6:33 am, David Fishburn <dfishburn....@gmail.com> wrote:
> Vim 7.2.1-255
>
> Not quite getting something.
>
> I can do this:
> echo globpath('C:\temp', 'test')
> -- Nothing
>
> echo globpath('C:\temp', 'test.*')
> c:\temp\test.db
> c:\temp\test.js
> c:\temp\test.log
> c:\temp\test.vim
>
> echo globpath('C:\temp', 'test$.*$')
> c:\temp\test.db
> c:\temp\test.js
> c:\temp\test.log
> c:\temp\test.vim
>
> echo globpath('C:\temp', 'test$.vim$')
> -- Nothing
>
> So, I am trying to use a regular expression to start limiting the files.
> Any ideas on what I am missing?

David,
The globpath function does not take a regular expression, but rather a
glob pattern, such as would be accepted by glob(). To see what
metacharacters are significant...
:help wildcard

I'm not sure why the  construct is accepted. Note, however, that
the `.' in your examples is matching a literal `.', not "any
character" as it would in a regex. This being the case, I would expect
'test$.vim$' and 'test$.*$' to pass or fail together, but I'm
thinking that  may be taking advantage of some undocumented
behavior. Perhaps I've just overlooked something in the documentation.

Brett S.

>
> TIA,
> Dave
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Re: Use VIM to perform text manipulation on file (like sed/awk)

Hi yosi!

On Mo, 31 Aug 2009, yosi izaq wrote:

> Let me see if I got your script right. You tell sed to work on the
> range from "-c" to first blank line right?
> Then you instruct it to comment the lines that are not already in
> comment in that range (which in this case is also a paragraph).
> It should work well so long as $1 is the first line in the paragraph.

No. Using -c will comment the selected paragraph (that is, from the
line that matches the pattern until the next blank line), without -c
it will uncomment the paragraph:

#v+
chrisbra t41:~/sed [1025]% cat resolv.conf
#Company IT nameservers
nameserver 1.2.3.4
nameserver 1.2.3.5
nameserver 1.2.3.6

Lab1 nameservers
nameserver 10.1.2.3
nameserver 10.1.2.4

#Lab2 nameservers
#nameserver 20.1.2.2

chrisbra t41:~/sed [1026]% ./resolv.sh -c Lab1 resolv.conf; cat resolv.conf
#Company IT nameservers
nameserver 1.2.3.4
nameserver 1.2.3.5
nameserver 1.2.3.6