vim, g++ logs and stuff

So I got vim for on a school computer (running windows of course), works fine and everything, except for any commands requiring an exclamation mark in front of it (like :!q or :!sav). Whenever I try to do :!q, I get the following message in a new command prompt:

C:\WINDOWS\system32\cmd.exe /c q
'q' was not recognized as an internal or external command, an application or a batch-file.
shell returned 1
Hit any key to close this window...

Any idea as to how to solve this?

=====

And to finish off, I want to know if there's any way of telling g++ to print it's errors to a log file?
(To be used for launching a .txt file from xoblite menu)

=

cookies to everyone who helps

/bin/bash: line 1: q: command not found

The exclamation mark goes after the command. What the hell is this crap?

>>1
Sage for faggotry, and what a manner of it...

can't believe I'd forgotten that it's supposed to be :q! instead of :!q

I fail at komputer

(g++ log output would still be appreciated)

>>4 (g++ log output would still be appreciated)

You mean something like a Windows equivalent of "g++ foo.c > goatse.txt"?

exactly

>>6

I have fortunately no clue, but in 3 seconds Google gave me this:
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/redirection.mspx?mfr=true

You still suck cocks.

You mean something like a Windows equivalent of "g++ foo.c > goatse.txt"?

The Windows equivalent is "g++ foo.c > goatse.txt".  I don't know if that'll work though, as I think g++ sends all its output to 2, or stderr, in which case you'd have to use 2> instead of >.  I don't know if Windows supports 2> :/

There's a reason why no one uses vi.

Because almost everyone sucks cocks.

There's a reason why no one uses vi

It's no longer 1983.

>>10

That's why we use vim.

>>11
That's why we use emacs.

Fixed.

>>8
>I don't know if Windows supports 2>

It does - even DOS supported that.

According to http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/redirection.mspx, 2>&1 works these days as well...

Windows sucks sure there's an ebuild for Windows but it just get dropped to C:\, it's statically linked, and it's CLOSED SOURCE, which means that it is a BINARY package.

>>14
same-ol-same-ol
fail for not funny

>>12
That's why we nano.

Fix'd!

>>16
how do you failed grammar?

>>17
Where?

let's all just agree on joe and not worry about crappy text editors again.

No matter what editor you use, you still can't be as cool as this guy: http://video.google.com/videoplay?docid=-8734787622017763097

[pre]no[/pre]

FUCK

You Suck

ur gay

beware the army of 12 year old autistics

27 Name: Anonymous 2011-02-04 13:17