On Monday 12 April 2010 17:23:02 Duane Johnson wrote:
> I'm a total newbie to Vim. I'd like to map a new command-line
> command (":vimrc") to open up my vimrc file (":e ~/.vimrc").
you are correct in thinking you don't really need a plugin for
this, unless of course you are interested in it mai
On Mon, Apr 12, 2010 at 6:23 PM, Duane Johnson wrote:
> I'm a total newbie to Vim. I'd like to map a new command-line command
> (":vimrc") to open up my vimrc file (":e ~/.vimrc").
As an addition to the other answers you've gotten - is this really
worth spending time optimizing? Especially when
On 2010-04-12, Duane Johnson wrote:
> I'm a total newbie to Vim. I'd like to map a new command-line command
> (":vimrc") to open up my vimrc file (":e ~/.vimrc").
>
> I tried something with cmap in my vimrc but caused infinite recursion by
> mistake (I have no idea if cmap is the right command to
Duane Johnson wrote:
> cmap vimrc e ~/.vimrc
I just use ':e $MYVIMRC' with command completion:
http://vim.wikia.com/wiki/Open_vimrc_file
You need 'cnoremap' rather than 'cmap' (and $MYVIMRC). However,
the mapping applies wherever you might type 'vimrc' in the
command line and I generally find tha
I'm a total newbie to Vim. I'd like to map a new command-line command
(":vimrc") to open up my vimrc file (":e ~/.vimrc").
I tried something with cmap in my vimrc but caused infinite recursion
by mistake (I have no idea if cmap is the right command to try):
cmap vimrc e ~/.vimrc
I also
On Mon, Apr 12, 2010 at 11:28 AM, Benoit Thomas wrote:
> Thanks, works great.
Please bottom post in the future - It's the mailing list policy, and
reading long threads can be painful when different posters are
inconsistent.
> However, is there a more "elegant" way of doing this ? Otherwise I'll e
Thanks a lot for the reply, this should get me started :)
Ben.
On 2010-04-12 12:05, Jürgen Krämer wrote:
Hi,
[Quoting reordered]
Benoit Thomas wrote:
On 2010-04-12 11:07, Jürgen Krämer wrote:
Benoit Thomas wrote:
I've done my own color scheme file, which work great. Howe
Hi,
[Quoting reordered]
Benoit Thomas wrote:
>
> On 2010-04-12 11:07, Jürgen Krämer wrote:
>>
>> Benoit Thomas wrote:
>>
>>> I've done my own color scheme file, which work great. However, when I
>>> tried to use variable instead of color name or color number (#00) it
>>> doesn't work an
Thanks, works great.
However, is there a more "elegant" way of doing this ? Otherwise I'll
end up doing :
exe 'hi Normal gui=' . s:text_style . ' guifg=' . s:text_fg . ' guibg='
. s:text_bg
which may become hard to read.
Ben.
On 2010-04-12 11:07, Jürgen Krämer wrote:
Hi,
Benoit Thomas w
Hi,
Benoit Thomas wrote:
>
> I've done my own color scheme file, which work great. However, when I
> tried to use variable instead of color name or color number (#00) it
> doesn't work and I don't know what I'm doing wrong.
>
> For example, I want to do something like this:
>
> " Text co
Hello everyone,
I've done my own color scheme file, which work great. However, when I
tried to use variable instead of color name or color number (#00) it
doesn't work and I don't know what I'm doing wrong.
For example, I want to do something like this:
" Text color is black.
let s:text
On 2010-04-12, esquifit wrote:
> On 12 Abr, 08:00, Gary Johnson wrote:
> > On 2010-04-11, esquifit wrote:
> > > I'm using gVim under Windows XP and set cygwin's bash to be the shell
> > > enviroment for gVim.
> >
> > [...]
> >
> > > In other words, seems that system correctly expects cygwin synta
> I have a patch for if_python.c that adds direct access to Vims
> internal screen.
Is there a chance this functionality will be available from vimscript
as well (and therewith be available to ruby etc. too). As long as one
of the top items (use python) isn't implemented.
--
You received this m
> #13 (Access W32 clipboard from Cygwin "Unix" Vim) is interesting but still
> in beta. IIUC ifdeffed by whatever FEAT_* corresponds to has('win32unix').
> Bring 'em in or let it bake some more?
I would really like this one. Even though it's possible to recreate
most of the functionality (via Fak
On Mon, Apr 12, 2010 at 8:08 AM, Tony Mechelynck
wrote:
> On 11/04/10 22:16, Bram Moolenaar wrote:
>>
>> Christian Brabandt wrote:
>>
>>> Are you considering any patches from
>>> http://groups.google.com/group/vim_dev/web/vim-patches
>>> for inclusion?
>>
>> Yes, but many of these patches are not
Hi Tony!
(replying to vim_use and vim_dev. Should we keep the discussion on
vim_dev or rather on vim_use?)
Disclaimer:
I know, this is not a wishlist thread, but I could not resist ;)
On Mo, 12 Apr 2010, Tony Mechelynck wrote:
> It is true that they are in different stages of development. Here a
On Sun, Apr 11, 2010 at 04:33:31PM +0200, Bram Moolenaar wrote:
>
> Hello Vim users!
>
> [...]
>
> Mercurial is going to be the primary method for distribution. I'll
> drop CVS, it slows me down too much. Someone else might be able to
> mirror the Mercurial repository in CVS, like it's done fo
esquifit 写道:
Regarding the suggestion of using cygwin vim in a terminal, I'd love
being able to do it, but unfortunately the (binary) cygwin
distribution of vim lacks a number of features (present on gVim) which
I absolutely need, and I don't have currently the knowledge nor the
time to attempt t
On 12/04/10 00:29, Albert wrote:
Hi,
I'm using gVimPortable and when I load up a file and type :mkview, it
responds with this error message:
http://sites.google.com/site/xtheunknown0/vim-code-folding
How do I fix this?
TIA,
Albert
:verbose set viewdir?
Make sure it is set to somep
On 11 apr., 16:33, Bram Moolenaar wrote:
> Hello Vim users!
>
> I will try to include a few patches that have been pending for a while.
> I don't have much time available, thus I will only include things that
> take a few hours of my time. That basically means patches that are
> ready to be inclu
Thank you for your swift reply. The point you explain below, namely
that filereadable() is part of the interface with the underlying OS
and that system() talks to the configured shell, was already apparent
to me. What I wanted to know was whether this was "intentional" or
not. I understand that th
> do you want both windows to display the same buffer or do you want the
> second one to be empty? In the fist case you can start vim with
>
> vim -c split myfile
>
> In the second case use
>
> vim -c new myfile
>
> With the -c option you tell Vim which commands shall be executed after
> loading
On 11/04/10 22:16, Bram Moolenaar wrote:
Christian Brabandt wrote:
Are you considering any patches from
http://groups.google.com/group/vim_dev/web/vim-patches
for inclusion?
Yes, but many of these patches are not mature. E.g., first one,
"Improved regular expression engine", is still lackin
23 matches
Mail list logo
