How to setup VIM

[Inny]

Leave a blank line between function declarations, and use the curly braces { and } to "jump paragraph"

There's more tips here: http://vim.wikia.com/wiki/Moving_around

[yetneverdone]

Leave a blank line between function declarations, and use the curly braces { and } to "jump paragraph"

There's more tips here: http://vim.wikia.com/wiki/Moving_around

Did you mean like this form?

function etc etc
--line
function etc etc etc
--line

[Inny]

Did you mean like this form?

No, like this:

Code: Select all

function name(args)
  -- body
end
  
local function other_name(args)
  -- body
end

this_is_okay_too = function(args)
  -- body
end

The key is there is an empty line between declarations, so vim knows where to jump to.

[yetneverdone]

Did you mean like this form?

No, like this:

Code: Select all

function name(args)
  -- body
end
  
local function other_name(args)
  -- body
end

this_is_okay_too = function(args)
  -- body
end

The key is there is an empty line between declarations, so vim knows where to jump to.

That was what i meant haha just got lazy typing in mobile. Well that works but not in all case jumps around functions since if there is also an empty line in between function and end,it will jump to that.

[davisdude]

Edit: Oh hey, that start cmd /c might be useful here. I guess I'll be doing that from now on. (This is the life of being a vim user, you're always learning a new tip)

Yeah, it took me a while to figure out something that really worked for my needs. For running single files, I actually use "!start cmd /c python % && pause" that way I can see the output of the console before it closes. I'm not completely sure if it works on Linux or not, though. I definitely second this, as well as the "Don't just blindly use them unless you understand them" bit.

Btw I figured out a better way to do this. With the old method, the console automatically quits on errors, which makes it hard to debug... So here's the improved version:

Code: Select all

<leader>r :silent !start cmd /c "lua % & pause"<CR>

The quotes surrounding it means to execute the first, then the second (pause), allowing you to see the error.

[yetneverdone]

You can use vim-dispatch to do that, and also to edit the code while the game is running (good for hot reloading)