Re: Key mapping on "," and "." with "CTRL"
> Another question is how I can check all of the current key mappings in > VIM? I remembered I saw something about it before, but failed to find > it out. try :map hth, ymc
Re: Automatically adding header into file with specific extension
hi, please take a look at vim tip #434 the example there is for *.h and *.cpp files but you might find some idea from it. hth, ymc - Original Message - From: "Gundala Viswanath" <[EMAIL PROTECTED]> To: Sent: Wednesday, October 18, 2006 4:19 PM Subject: Automatically adding header into file with specific extension > Hi, > > I want to be able to have VIM automatically > insert this line: > > #!/usr/bin/python > > Whenever I open a NEW file with *.py or *.egg extension > for example > > under bash > $ vi mycode.py > > or > > $ vi mycode.egg > > or under VI > > : e mycode.py > > Is it possible? > > -- > Gundala Viswanath >
Re: set vb t_vb=
> > I'll send you my vimrc privately as an example; no need to > > spam the list with it. > > spam away ;-) > > -- > Mark > I'm curious too, i know i'll learn a lot from it. regards, harvey
Re: VIM 7: feature documentation
> - Original Message - > From: "ymc014" <[EMAIL PROTECTED]> > To: "Fabio Rotondo" <[EMAIL PROTECTED]> > Cc: > Sent: Tuesday, May 09, 2006 3:50 PM > Subject: Re: VIM 7: feature documentation > > > > > > - Original Message - > > From: "Fabio Rotondo" <[EMAIL PROTECTED]> > > To: > > Sent: Tuesday, May 09, 2006 3:11 PM > > Subject: VIM 7: feature documentation > > > > > > > Hi everybody, > > > > > > I am really new to this list, just installed the latest Vim and I'd like > > > to know where can I look for a detailed documentation of the new > features. > > > > > > Thanks in advance. > > > > > > Ciao, > > > > > > Fabio > > > > > > > > > > > Hello Fabio, > > > > You could try typing this in normal mode > > > > :help > > > > a list of help topics would be displayed. > > > > > > HTH, > > hernan > > OOps, lacking sorry, after typing :help position the cursor on the topic (link) you want to see and press CTRL-]. Press CTRL-T to go back to the previous topic.
Re: VIM 7: feature documentation
- Original Message - From: "Fabio Rotondo" <[EMAIL PROTECTED]> To: Sent: Tuesday, May 09, 2006 3:11 PM Subject: VIM 7: feature documentation > Hi everybody, > > I am really new to this list, just installed the latest Vim and I'd like > to know where can I look for a detailed documentation of the new features. > > Thanks in advance. > > Ciao, > > Fabio > Hello Fabio, You could try typing this in normal mode :help a list of help topics would be displayed. HTH, hernan
Re: Quick peak at files
- Original Message -
From: "Suresh Govindachar" <[EMAIL PROTECTED]>
To:
Sent: Friday, April 28, 2006 12:58 PM
Subject: Quick peak at files
>
> Hello,
>
> I have summarized my posts today titled "Balloons", "File ->
> register" and "Backslash in maps" as a vimtip
> (www.vim.org/tips/tip.php?tip_id=1218) titled "Quick peak at
> files"; the tip is also attached below.
>
> --Suresh
>
> Quick peak at files
>
> In an operating system's command-line terminal, one can get a
> quick peak at a file using commands such as more, cat, head etc.
> In vim, one way to peak at a file would be to open it in a new
> buffer -- but there is a way to peak at a file from vim without
> having to open it in a buffer, browse it and close the buffer --
> one can just view it in vim's command line! This mode of viewing
> is facilitated in vim version 7 by version 7's support for
> scrolling (see :help scroll-back).
>
> So to peak at a file, we just echo its contents (:help echo; info
> on other commands mentioned here can be found likewise via :help).
>
> Simple implementation:
> -
> One way to implement the idea would be:
>
> :new|r |1d|exec 'normal "ayG'|q!|echo @a
>
> One could also do :echo system('cat foo.bat'), but we are trying
> to avoid explicit system calls. In version 7, vim supports
> readfile(). But the results of readfile() is an array of lines --
> and these lines would need to be joined to enable viewing; so we
> have:
>
> :echo join(readfile('foo.bat'), "\n")
>
> Applications:
>
> Here are two applications that build on the idea presented here.
>
> A) Yasuhiro Matsumoto's calendar utility
> (www.vim.org/scripts/script.php?script_id=52) is written to
> display the calendar in a buffer. For a quick peak at the
> calendar, one can modify the plugin to support echoing the
> calendar in vim's command line, and make a simple map (such as
> of a RightMouse click) to trigger the display on the command
> line!
>
> B) I have the following in my vimfiles\after\ftplugin\index.vim
> to speed up previewing emails using my mail user agent utility
> (www.vim.org/scripts/script.php?script_id=1052)
>
> if(v:version < 700)
>
> nnoremap :exec "let @a='r
'.expand('%:p:h').'/'.substitute(
> \getline('.'),
>
\'\\(^.*\|\\s*\\)\\\|\\(\\s\\s*$\\)',
> \'',
> \'g')
> \\\|new\\|@a\\|1d\\|
> \silent exec 'normal\
d}\"ayG'\\|q!\\|echo\ @a"
> else
>
> nnoremap :exec "let
alist=readfile(expand('%:p:h').'/'.
> \substitute(getline('.'),
>
\'\\(^.*\|\\s*\\)\\\|\\(\\s\\s*$\\)',
> \'',
> \'g')
> \)\\|
> \while(remove(alist, 0) != '')
> \\\|endwhile
> \\\|echo\
> \substitute(getline('.'),
>
\'\\(^.*\|\\s*\\)\\\|\\(\\s\\s*$\\)',
> \'',
> \'g').\"\n\n\"
> \\\|echo join(alist,\"\n\")"
>
> endif
>
> Acknowledgment:
> --
> While the idea presented here is mine, people on the vim@vim.org
> mailing list suggested alternate ways of implementing it and
> helped with some implementation details (such as escaping |).
>
> Happy vimming!
>
> --Suresh
>
Just a clarification, peak or peek? People (like me)looking for a tip like
this might missed it. I myself think it's peek but that's just me.
By the way thank you for this tip.
Best regards,
h.
Re: Svn and patches
Thank you for the info - Original Message - From: "Edward L. Fox" <[EMAIL PROTECTED]> To: "Suresh Govindachar" <[EMAIL PROTECTED]>; Sent: Friday, April 28, 2006 1:19 PM Subject: Re: Svn and patches > > Hi, I'm the subversion repository maintainer. I sync the subversion > repository with the CVS repository everyday at about 9:00 (+0800), or > 1:00 (GMT). So if you checkout the code at about 2:00 (GMT), you can > get the latest version. :-) >
