Hmm that works, I guess its the
set cinoptions=:0g0
thing I'd set later on for just generic files.
On 4/29/06, Jean-Emmanuel Reynaud <[EMAIL PROTECTED]> wrote:
I tried to indent your piece of code using vim, and obtained the
indentation you like.
So what's the difference between your and my co
Yakov Lerner <[EMAIL PROTECTED]> wrote:
> On 4/29/06, Eric Crahen <[EMAIL PROTECTED]> wrote:
> > Is it possible to map CTRL-[ ? That generates the ESC code,
>
> In X11, you can use xmodmap to have Esc and Ctrl-[
> send different things, I think. But this is platform
Is it possible to map CTRL-[ ? That generates the ESC code,
:map something
:map
will show that was converted to Esc
something
I tried to do some other flavors of the map command but no dice.
--
- Eric
Thanks for all the help so far, one question on formatting. I've read
the help on cinoptions and I can't figure this one out.
I like my Java like this:
// WANTED
public void testNullConstructor()
throws Throwable {
try {
new ParameterTypeMatcher((Type[])null);
fail();
} ca
For some reason I get an empty hidden buffer that does show up when I
list buffers. Its the same one you'd get when you open vim w/ no
filenames. I'll poke around andd if there is a setting causing that
On 4/28/06, Yakov Lerner <[EMAIL PROTECTED]> wrote:
On 4/28/06, Eri
When I start vim from the command line and provide a filename, how can
I prevent a default scratch buffer from also being opened?
--
- Eric
When I open files from within vim its not a problem. Its the files
that are opened from the command line, a method I use every day.
On 4/27/06, Gerald Lai <[EMAIL PROTECTED]> wrote:
> On 4/27/06, Eric Crahen <[EMAIL PROTECTED]> wrote:
>
> > On 4/27/06, Gerald Lai &
I've tried all variation of BufEnter and autchdir commands to get the
cwd switched to that of the file that is open. None of them ever work
when I specify a file on the command line. The buffer for the file I
specify is open, but the cwd is right where I started vim. I have to
:bn|:bp to get the bu
