Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 58108431FBC for ; Fri, 17 Oct 2014 09:35:35 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.799 X-Spam-Level: X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PdAYmct0yHvO for ; Fri, 17 Oct 2014 09:35:29 -0700 (PDT) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id A9492431FB6 for ; Fri, 17 Oct 2014 09:35:29 -0700 (PDT) Received: by mail-wi0-f178.google.com with SMTP id h11so1903469wiw.11 for ; Fri, 17 Oct 2014 09:35:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:message-id:from:to:cc:subject:in-reply-to:references :mime-version:content-type:content-disposition :content-transfer-encoding; bh=7b3UbHc9YTzQrpFpLGKOEedQjEQ65XlIsLgBlL7OGHo=; b=EMdx2TguYmjwSxRfx6fure7w5RkA1IUmeChISgnCk4LykGG/TjD6ueTnyGjomqiREG sYxHS3VHm52Bo5xEuZRQ/N9jQ7JHmH+NHe5+tUIGeaFM/xHI7C0aWxH7Qwei0YQtMTUd 7B9N7Qwfi/idGxGSVIauC/kTgfluslPdwGDcUygUwOplbe4HR/Bg5Pw8pMXY0Sh26uGM c/N7PkfgyrBdeC74uYx+A2nBPRybPz405Nv/PE41LwmzFucr9TVDZ62r46msQUSvUDAN KmucyWNmcMwLknho/1ZwOWgLYeOSSXaF9r3lC+2ZD8uX9qkbhMiXNsqfYajja4ftvEMr ja6Q== X-Received: by 10.194.90.175 with SMTP id bx15mr11490521wjb.25.1413563728334; Fri, 17 Oct 2014 09:35:28 -0700 (PDT) Received: from localhost (p5B00C8AC.dip0.t-ipconnect.de. [91.0.200.172]) by mx.google.com with ESMTPSA id om1sm2221815wjc.42.2014.10.17.09.35.26 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 17 Oct 2014 09:35:27 -0700 (PDT) Date: Fri, 17 Oct 2014 18:35:38 +0200 Message-ID: <20141017183538.GI20696@TP_L520.localdomain> From: Franz Fellner To: Ian Main Subject: Re: notmuch vim patches In-Reply-To: <544046f358233_2c291569e8c76@ovo.mains.priv.notmuch> References: <543ecf59e21b8_2c291569e8c7e@ovo.mains.priv.notmuch> <20141016144109.GB3471@TP_L520.localdomain> <544046f358233_2c291569e8c76@ovo.mains.priv.notmuch> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Cc: notmuch@notmuchmail.org X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2014 16:35:35 -0000 On Thu, 16 Oct 2014 15:30:11 -0700, Ian Main wrote: > Franz Fellner wrote: > > > > > > > I'm starting to realize that I could default to using 'enter' to both > > > open URI's and view attachments. Any other ideas welcome. > > > > - make some of the functions public so users can bind them to keys they > > want > > - introduce show_[prev,next]_unread_msg, probably factor out > > "show_scroll_to_msg()" and implement prev/next msg with that? > > You know I was just reading a thread and hit 'a' to archive a message > within the thread and for some reason it hung for a few seconds.. but it > made me think we should be able to press 'a' (or whatever archive key) > and have it archive and move to next unread. That seems to me to be a > good behavior with a natural flow. Yes, sounds good. Today I thought of a more generic approach: pass a query that a message should match. :notmuch-show-next-message tag:unread # go to the next unread message in thread :notmuch-show-next-message from:"Ian Main" # got to the next message in thread sent by "Ian Main" ... The user then can map keys to custom commands. Good or too generic? Furthermore I thought of rearranging the sources: - Put files in Vundle/*-compatible dirs, would simplify development. (Currently I have several files symlinked from notmuch-src into .vim) - Put the "heavy" ruby code into its own file. Today I got an error I could not deal with because line numbers did not match. Also I read about the possibility that the ruby interpreter might optimize only seperate files. This could lead to better performance. Franz