Excerpts from Pablo Giménez's message of Thu Apr 26 20:00:23 +0200 2012:
I dont know exactly how it works but this is what it is doing ans is great.
AFAIK in vam you have to activate the plugins manually using
ActivateAddons, then the plugin rather than being waiting to be called it
is loaded.
Hi,
which Mark.vim you are using:
http://www.vim.org/scripts/script.php?script_id=1238
or
http://www.vim.org/scripts/script.php?script_id=2666
I haven't used any of those but there is a chance that
http://www.vim.org/scripts/script.php?script_id=2666
will support restoring from session.
At
Hi
I am notorious use vim with many splits.
Because my sloppy typing skills I have problem with
:only option
or rather shortucts
CTRL-W CTRL-O
To workaround that I added to .vimrc
block only one
nnoremap C-WO :echo You dont want thisCR
nnoremap C-Wo :echo You dont want thisCR
nnoremap C-WC-O
I am running netrw v146d in Windows XP.
The directory that I am in contains the following elements:
master1.bib
master1.bib.backup
master1.log
.master1.bib.un~
master1.bib~
When I marked the first file (master1.bib), all of the files in
directory were highlighted as marked except for
Hello all,
I have this annoying problem and I'm hoping some of the vim gurus out
there will be able to help me. I'm a C++ programmer and I love
working with vim. My new project is requiring C-style block comments
be used on our source files, and we also use doxygen. Herein lies the
problem.
On Fri, Apr 27, 2012 at 10:32 AM, Justin jrrand...@gmail.com wrote:
Hello all,
I have this annoying problem and I'm hoping some of the vim gurus out
there will be able to help me. I'm a C++ programmer and I love
working with vim. My new project is requiring C-style block comments
be used
On Friday, April 27, 2012 9:42:47 AM UTC-5, Justin wrote:
Sorry the text got garbled in the original example. Let me try again.
This is what I want:
class Test
{
public:
///**
* @brief
* This is the
I have two HP-UX machines say A and B with HP-UX 11.11 and 11.31
respectively. I'have compiled gvim 7.3 from source an B, and gvim 7.0
on A, both with same options for configure..
On A, gvim uses version with GTK GUI, Compilation with gcc (...) -
DFEAT_GUI_GTK and all works fine.
On B, gvim
I use this code in my .vimrc to use my dark colorscheme when I open a .vim page
and my light colorscheme when I open whatever other page:
augroup filetype_colorscheme
au BufEnter *
\ if !exists('b:colors_name')
\ | if ft == vim
\ | let b:colors_name =
Bart Baker wrote:
I am running netrw v146d in Windows XP.
The directory that I am in contains the following elements:
master1.bib
master1.bib.backup
master1.log
.master1.bib.un~
master1.bib~
When I marked the first file (master1.bib), all of the files in
directory were highlighted as marked
On Friday, April 27, 2012 10:02:11 AM UTC-5, Justin wrote:
Running :verbose set ft? autoindent? smartindent? cindent? cino?
from my Vim it says:
filetype=cpp
Last set from /usr/local/share/vim/vim70/filetype.vim
autoindent
Last set from ~/.vimrc
smartindent
On Friday, April 27, 2012 10:56:55 AM UTC-5, rameo wrote:
I use this code in my .vimrc to use my dark colorscheme when I open a .vim
page and my light colorscheme when I open whatever other page:
augroup filetype_colorscheme
au BufEnter *
\ if !exists('b:colors_name')
On Friday, April 27, 2012 6:18:29 PM UTC+2, Ben Fritz wrote:
On Friday, April 27, 2012 10:56:55 AM UTC-5, rameo wrote:
I use this code in my .vimrc to use my dark colorscheme when I open a .vim
page and my light colorscheme when I open whatever other page:
augroup filetype_colorscheme
2012/4/27 lith minil...@gmail.com
Hi,
I love how fast vim loads using tplugin and how it changes the runtime
path on demand.
But then I also found some limitations. Seems thare is no way to tell
the tool not to load some plugins, also the dependency system looks a
little but clunky
On 27/04/12 17:03, Arno Valentin wrote:
I have two HP-UX machines say A and B with HP-UX 11.11 and 11.31
respectively. I'have compiled gvim 7.3 from source an B, and gvim 7.0
on A, both with same options for configure..
On A, gvim uses version with GTK GUI, Compilation with gcc (...) -
2012/4/27 Marc Weber marco-owe...@gmx.de
Excerpts from Pablo Giménez's message of Thu Apr 26 20:00:23 +0200 2012:
I dont know exactly how it works but this is what it is doing ans is
great.
AFAIK in vam you have to activate the plugins manually using
ActivateAddons, then the plugin rather
On 27/04/12 17:45, rameo wrote:
I still have problems mapping keys.
On my keyboard I have these keys I want to map:
C-ò
C-à
C-è
C-ù
C-ì
Tony once told in a message these info:
ò = (0xF2, o-grave) and M-r (Alt+0x72, Alt-r)
à = (0xE0, a-grave) and M-` (Alt+0x60, Alt-backtick)
è = (0xE8, e-grave)
Marc Weber wrote:
Excerpts from Pablo Giménez's message of Thu Apr 26 20:00:23 +0200 2012:
I dont know exactly how it works but this is what it is doing ans is great.
AFAIK in vam you have to activate the plugins manually using
ActivateAddons, then the plugin rather than being waiting to be
On 27/04/12 18:34, rameo wrote:
On Friday, April 27, 2012 6:18:29 PM UTC+2, Ben Fritz wrote:
On Friday, April 27, 2012 10:56:55 AM UTC-5, rameo wrote:
I use this code in my .vimrc to use my dark colorscheme when I open a .vim page
and my light colorscheme when I open whatever other page:
I recently found this out:
Suppose you typed a longer command and you noticed that you had made several
mistakes, and wanted to do the correction in the vi editor itself. You can type
'v' to edit the command in the editor and not on the command line!
But after I edit the command in vim, how do
pixelterra, Fri 2012-04-27 @ 11:35:39-0700:
But after I edit the command in vim, how do I get that command back to
the command line? Or do I have to copy / paste manually?
When you save the buffer and quit the editor, the shell then executes
the contents of the saved buffer. So it happens
On 04/27/12 13:35, pixelterra wrote:
Suppose you typed a longer command and you noticed that you
had made several mistakes, and wanted to do the correction in
the vi editor itself. You can type 'v' to edit the command in
the editor and not on the command line!
Are you sure you mean typing v to
On 27/04/12 20:35, pixelterra wrote:
I recently found this out:
Suppose you typed a longer command and you noticed that you had made several
mistakes, and wanted to do the correction in the vi editor itself. You can type 'v' to
edit the command in the editor and not on the command line!
But
On Friday, April 27, 2012 2:48:06 PM UTC-4, Tim Chase wrote:
On 04/27/12 13:35, pixelterra wrote:
Suppose you typed a longer command and you noticed that you
had made several mistakes, and wanted to do the correction in
the vi editor itself. You can type 'v' to edit the command in
the
:x did the trick. What exactly is that command?
--
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
pixelterra, Fri 2012-04-27 @ 11:52:29-0700:
:x did the trick. What exactly is that command?
:help :x
*:x* *:xit*
:[range]x[it][!] [++opt] [file]
Like :wq, but write only when changes have been
made.
When
Sorry...I didn't see the entire subject line on my screen and
assumed you were talking about Vim. The bash vi mode (set -o
vi) is a separate beast.
But after I edit the command in vim, how do I get that command
back to the command line? Or do I have to copy / paste
manually?
Quitting vim
Actually, I was wrong, this doesn't work. Sorry for the confusion. Any other
options?
--
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
Minor correction.
On 2012-04-27, Tony Mechelynck wrote:
On 27/04/12 18:34, rameo wrote:
Where would you place this in above code?
Around your autocommand:
augroup filetype_colorscheme
au BufEnter *
\ if winnr('$') == 1
\ | if !exists('b:colors_name')
Sergey Khorev wrote:
Has anyone successfully built Vim for Windows 7 with support for 64 bit
perl? �It would be nice if VIM were 64 bit, but 32 bit VIM is OK; �embedded
perl must be 5.12 64 bit.
32bit application cannot use 64bit dll. Here is x64 Vim built with
ActivePerl 5.12.4.1205:
On 2012-04-27, pixelterra wrote:
Actually, I was wrong, this doesn't work. Sorry for the confusion.
Any other options?
What do you mean, this doesn't work? If you mean you still want
to have the edited command on the command line and not executed when
you exit vim, I don't think bash lets you
The problem is solved !
In this thread you can take a patch from Christian Brabandt which make
possible behavior described in Subject and test case.
http://groups.google.com/group/vim_dev/browse_thread/thread/1b50de7f4163dbb5/b36e113b3abebad9?lnk=gstq=vakulenkopli=1
On Apr 24, 8:33 am, Chris
On Friday, April 27, 2012 8:29:03 PM UTC+2, Tony Mechelynck wrote:
On 27/04/12 18:34, rameo wrote:
On Friday, April 27, 2012 6:18:29 PM UTC+2, Ben Fritz wrote:
On Friday, April 27, 2012 10:56:55 AM UTC-5, rameo wrote:
I use this code in my .vimrc to use my dark colorscheme when I open a
I originally noticed this in MacVim, but turns out this happens in the
terminal as well. If you have two tabs open and enter the Insert mode
in one, then switch to the other tab (by clicking on it in GUI, for
example), the Insert mode is still active. This wreaks havoc when I'm
editing something
On 27/04/12 23:45, Andrei Zmievski wrote:
I originally noticed this in MacVim, but turns out this happens in the
terminal as well. If you have two tabs open and enter the Insert mode
in one, then switch to the other tab (by clicking on it in GUI, for
example), the Insert mode is still active.
On Friday, April 27, 2012 4:45:29 PM UTC-5, Andrei Zmievski wrote:
I originally noticed this in MacVim, but turns out this happens in the
terminal as well. If you have two tabs open and enter the Insert mode
in one, then switch to the other tab (by clicking on it in GUI, for
example), the
That would probably be the simplest solution, since it's so simple to
enter the Insert mode when coming back to the tab.
-Andrei
On Apr 27, 4:22 pm, Ben Fritz fritzophre...@gmail.com wrote:
On Friday, April 27, 2012 4:45:29 PM UTC-5, Andrei Zmievski wrote:
I originally noticed this in MacVim,
37 matches
Mail list logo
