Thursday, April 29, 2010

A non-Vim behavioural problem

Hi all,

Vim works so well for me, that I've only had the need to follow the list
and not post for a while ;)

However, I am having an issue that is becoming more frustrating over time.

I've got my .vimrc set up how I like it, but oftentimes when I get svn
diff reports of my code, or I send code snips via email to myself via
the command line, I end up with offsets. My code, in vim, appears as such:

$self->function_orders();

my $type = $params->{ type };
my $data = $params->{ data };
my $error = $params->{ error };

my $vardb = ISP::Vars->new();

# die right off the bat if either data is an invalid type,
# or no $error obj was passed in

if ( ! defined $error ) {
$error = ISP::Error->new();
$error->bad_api();
}

...however, in reports, emails and/or bug notifications, it will often
look like this:

$self->function_orders();

my $type = $params->{ type };
my $data = $params->{ data };
my $error = $params->{ error };

my $vardb = ISP::Vars->new();

# die right off the bat if either data is an invalid type,
# or no $error obj was passed in

if ( ! defined $error ) {
$error = ISP::Error->new();
$error->bad_api();
}

....which makes it difficult (ie. *very* frustrating) to review down the
road.

Is this a behavioural problem? If it is, can anyone offer any tips to
correct the behaviour, or better yet, any way to clean up what I'm
thinking could possibly be excessive whitespace?

Cheers!

Stee

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

No comments:

Post a Comment