#vim

02 January 2008

Total 7 pages. You are browsing page 1/7.

First :: Prev :: [1] [2] [3] [4] [5] [...] :: Next :: Last

--- Log opened Wed Jan 02 00:00:06 2008
00:03 <****> hello
00:04 <****> I'm having problems with expandtab in both versions 7.1.123 and 7.1.164
00:05 <****>
00:05 <****> anybody else seen this?
00:15 <****> hello
00:16 <****> so ich geh mal pennen! :)
00:50 <****> what do i do with a vba file that looks like a vimball but vimball says otherwise?
00:51 <****> oh, now it works - how confusing
00:53 <****> jdv79: Line up in the queue of people wanting to kill the vimball-inventor.
00:54 <****> when i first learned of it i thought it a bad idea.
00:55 <****> And the first thought usually is right, as we all know :)
00:57 <****> Hum. Ich denke, ich geh schlafen. Gute Nacht.
00:57 <****> Sorry, wrong channel. ^-^
00:58 <****> harlekin: good night :P
00:58 <****> whats wrong with vimballs?
00:59 <****> daniel: Thanks. :D
00:59 <****> nanothief: They're useless, incompatible in every small revision, can fuck up your whole system and are implemented stupidly.
01:00 <****> daniel: haha ok, i've only ever used a few of them, but i might try to dodge them in the future
01:00 <****> That worst thing about it is that you sometimes can't exactly do that, because the package is only provided as a salty vimball
01:01 <****> I wonder why Bram approved it
01:02 <****> We certainly was drunk :-)
01:03 <****> :)
01:04 <****> s/We/He/
01:04 <****> I wonder if he regrets it. :)
01:05 <****> he will ... in time :)
01:31 <****> is there a way that vim can pretend that expanded-tabs (sets of spaces) are really tabs so that I don't have to backspace or move as much?
01:32 <****> See Ctrl-D or << for deindenting the line, so you won't need to backspace them
01:32 <****> kibab: :he 'sts'
01:33 <****> LeoNerd | Nyoxi : thanks, I'll take a look
01:34 <****> though using backspace is genrealy bad idea, there are usually better ways
01:36 * kibab thinks carefully to try to figure out what he really needs
01:47 <****> anyone know how the tail plugin is supposed to be used? http://www.vim.org/scripts/script.php?script_id=1714
01:51 <****> i thought google summer of code projects had to pass some sort of tests or quality threshold...
01:53 <****> I'm using the command line switch /ErrorStdOut when launching any AutoHotkey script
01:53 <****> I want vim to show errors in a small split window (as it does with perl support) so I can click and go to the error directly
01:53 <****> jdv79: as a former SoC student, I can say for certain, no.
01:53 <****> jdv79: its probably not a google summer of code project, its just on the google code site
01:54 <****> you just have to convince the reviewer that you did "enough" to pass the review.
01:54 <****> Anyone knows how to tell vim to capture STDOUT?
01:54 <****> i thought i read somewhere it was a SoC thing
01:55 <****> maybe, i could have missed it
01:55 <****> s/STDOUT/STDERR/
01:55 <****> urlwolf, i'm not sure what you mean
01:56 <****> have you used the plugin perl-support?
01:56 <****> no
01:56 <****> it lets you run the scripts from vim
01:56 <****> and if there are any errors, it displays them in a small window
01:56 <****> urlwolf: oh you mean the perl/python/ruby etc programming interfaces
01:56 <****> like :perl Vim::Msg("hello")
01:57 <****> hmm
01:57 <****> I think those run the built-in interpreter (if vim is compiled with ruby+ etc)?
01:58 <****> urlwolf: yep, so you mean something else
01:58 <****> i don't know then
01:58 <****> yes the normal interpreter. one you can set up yourself
01:58 <****> in this case, autohotkey
01:59 <****> i didn't even know autohotkey had an interpretor
02:00 <****> well, it's an interpreted language, right? I mean autohotkey.exe
02:04 <****> how about having a the * buffer (clipboard) showing in a window (that autorrefreshes)?
02:04 <****> then you can pipe the output to the clipboard
02:05 <****> urlwolf: i'm still confused as to what you want to do. Are you trying to write a script where you enter a autohotkey command, it feeds it to autohotkey.exe, and displays the result?
02:06 <****> well autohotkey dies with a msgBox if there's an error
02:06 <****> Some editors (PSPad) can do a more IDE-like behavior
02:06 <****> F9 - run the script
02:07 <****> then the errors are captured in a window, and you can click on them to go to the line number
02:07 <****> I'm trying to replicate that in vim
02:07 <****> oh okay
02:07 <****> I know vim can be convinced to do that
02:07 <****> when coding perl long ago, there was a pluigin that did exactly that
02:08 <****> urlwolf, it does that for c, cpp, java, and many more
02:08 <****> the problem with autohotkey is that it outputs messages to a msgbox, not to stdout
02:08 <****> The part where F9 calls the interpreter (without popping out a DOS window) is important too
02:08 <****> yes, but how do the PSPad guys do it?
02:09 <****> there's this: http://www.autohotkey.com/docs/commands/_ErrorStdOut.htm
02:09 <****> there must be a command somewhere to tell autohotkey to direct errors to stdout instead of a msgbox
02:09 <****> thats it then
02:10 <****> but once you redirect output, how do you make vim catch it?
02:11 <****> you need to use a combination of makeprg and errorformat (use :help)
02:15 <****> hmm looks hard
02:16 <****> it is, unfortunately
02:17 <****> not the makeprg part, the erroformat part
02:17 <****> however, sometimes the default errorformat works well enought, so you could still give it a go
02:22 <****> what's the symbol for 'currently open filename'?
02:22 <****> %?
02:22 <****> i.e.
02:22 <****> "C:\Program Files\AutoHotkey\AutoHotkey.exe" /ErrorStdOut %?
02:22 <****> Yes
02:22 <****> % is the current file name
02:25 <****> that's great
02:25 <****>^1 in the error window
02:26 <****> getting there
02:26 <****> both with /ErrorStdOut and without the result is the same
02:30 <****> so it's not working yet :(
02:34 <****> what flavor is vim's regular expresions? POSIX? Is there any way to match multi-line patterns (e.g. function()\n\{ )?
03:02 <****> http://bux.to/?r=ikichi it's very cool
03:12 <****> urlwolf: :help regex
03:12 <****> how do you determine what directories vim searches for plugins?
03:20 <****> load-plugins
03:23 <****> holst: thanks (i actually needed :help runtimepath, but load-plugins lead me to it)
03:54 <****> any1 here

Total 7 pages. You are browsing page 1/7.

First :: Prev :: [1] [2] [3] [4] [5] [...] :: Next :: Last