Date: Wed, 21 Jan 2015 19:53:56 +0100
From: Franz Fellner <alpine.art.de@gmail.com>
To: Bartosz Telenczuk <telenczuk@unic.cnrs-gif.fr>
Message-ID: <54bff5c426e50_5b9d145d304d6@TP_L520.notmuch>
In-Reply-To: <54b45d071fd20_7f93fe5bd4401f087@bts-MacBook-Pro.local.notmuch>
References: <1412618116-27586-1-git-send-email-imain@stemwinder.org>
	<1413828111-2879-1-git-send-email-imain@stemwinder.org>
	<54b45d071fd20_7f93fe5bd4401f087@bts-MacBook-Pro.local.notmuch>
Subject: RE: [PATCH v3] VIM: Improve moving between messages in a thread
Mime-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: 7bit
Attach: 
Cc: notmuch@notmuchmail.org
Precedence: list

Bartosz Telenczuk wrote:
> Hi Ian,
> 
> The patch looks good. I tested it on my system and it works fine.  I just have one suggestion regarding coding style.
> 
> > +function! s:show_prev_msg()
> >  function! s:show_next_msg()
> 
> Since these functions are almost the same, you could avoid code repetition by replacing them by a function which takes (positive or negative) increment as an argument.

I think the API should be clear and easy to understand, because people will probably bind them to custom shortcuts. You should not have to think about what that weird extra parameter (-1, false, ...) means and go read the docs.
But I agree that the code duplication is not optimal. The code in Ians repo already has split out the ruby code. There is still code duplication. But that can easily be split out into a function on its own. 

Franz