I'm having trouble understanding why there is a period before w in the
following command:
:'a,'b g/^Error/ .w errors.txt
Does it indicate the current directory? It's difficult searching the help for
just a .;)
--
You received this message from the vim_use maillist.
Do not top-post! Type
I'm trying to compile a huge version of Vim, including gVim, using Mercurial.
I've only managed to install console Vim, and that's a normal version, without
Python and Perl interface. I followed the instructions and issued these
commands:
hg clone https://vim.googlecode.com/hg/ vim
./configure
On Jan 24, 11:04 am, eNG1Ne wrote:
OK, normally I'd use :sav – but when I want to save from hard drive to
USB stick, and as an occasional Mac user, I'm a long way from sure
about how to navigate.
You can also use :browse confirm sav (which you could map to sth
shorter) to open the file
On Apr 26, 10:46 am, pa...@ezrider.co.uk wrote:
Hi All,
Basically, VIM remembers the CD (Current Directory) from a file ages
ago, and I simply cannot goad VIM into remembering a new one
snip
You could use a session (:mksession filename). The session file
stores a new current directory. So if
On Apr 7, 11:11 pm, Tim Gray tg...@protozoic.com wrote:
On Apr 07, 2011 at 04:15 PM -0400, Eric Weir wrote:
Still, as I imagine many are, I'm a bit intimidated complexity of the
commands and the steep learning curve. So, I'm wondering if there are any
ordinary, nonprogrammer writers here
On Mar 22, 9:23 am, Marco net...@lavabit.com wrote:
Hi,
I often use :wCR:bdCR. I wonder if there's a shortcut for this quite
common sequence. Or is it best to create a mapping?
Marco
There does not seem to be a built in command to do this so, yes, you
can do e.g.
:noremap \w :wCR: bdCR
You don't want the 't' item in guioptions. That's short for 'tearoff'
menu items. Even if you add:
finish
as the first line of /usr/share/vim/vim73/menu.vim, you still get a
sliver of a menu bar when the 't' is there.
(though I only realized what was happening when I couldn't reproduce
On Mar 6, 8:51 pm, Benjamin R. Haskell v...@benizi.com wrote:
snip
So, to John: I'd recommend keeping your .gvimrc exactly as you had it,
except wrapping the 'set tb=' command in the GUIEnter autocmd:
== .gvimrc ==
set vb t_vb=
set showcmd
set guioptions=aegiLt
au GUIEnter * set tb=
I have the following .gvimrc:
set vb t_vb=
set showcmd
set guioptions=aegiLt
set tb=
But after starting Gvim I still get a toolbar. :verbose set tb? says
~/.gvimrc and if I manually do :set tb= the toolbar disappears as
expected. Any ideas?
--
You received this message from the vim_use
On Mar 5, 4:16 pm, John Degen johnde...@gmail.com wrote:
I have the following .gvimrc:
set vb t_vb=
set showcmd
set guioptions=aegiLt
set tb=
But after starting Gvim I still get a toolbar. :verbose set tb? says
~/.gvimrc and if I manually do :set tb= the toolbar disappears as
expected
I managed to install Vim on FreeBSD 8.0 using AAP as per the
instructions on a-a-p.org. It worked well, except I now have a version
without Perl or Python integration. I don´t need this urgently but I
wonder how I could have installed the Big version with everything. Is
this done in the configure
I have set showcmd in my .vimrc and .gvimrc. Yet the option is
disabled if I start gVim or Vim. How can I tell where this option was
_not_ set? :showcmd works as expected.
My version is 7.1.138, +cmdline_info
The output of :script is
1: /usr/share/vim/vimrc
2:
12 matches
Mail list logo