From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 51A696DE00F5 for ; Wed, 14 Jun 2017 04:06:35 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.371 X-Spam-Level: X-Spam-Status: No, score=0.371 tagged_above=-999 required=5 tests=[AWL=-0.362, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_SBL=0.644, URIBL_SBL_A=0.1] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l0KpfKpUvFYO for ; Wed, 14 Jun 2017 04:06:34 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 7556B6DE0008 for ; Wed, 14 Jun 2017 04:06:34 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1dL658-0005rL-No; Wed, 14 Jun 2017 07:03:26 -0400 Received: (nullmailer pid 27812 invoked by uid 1000); Wed, 14 Jun 2017 11:06:31 -0000 From: David Bremner To: Damien Cassou , notmuch@notmuchmail.org Subject: imenu support In-Reply-To: <87r2ymj3m9.fsf@cassou.me> References: <87bmpuokl1.fsf@tethera.net> <20170612133010.13579-1-damien@cassou.me> <878tkvtlat.fsf@tethera.net> <87r2ymzyx1.fsf@tethera.net> <87r2ymj3m9.fsf@cassou.me> X-List-To: notmuch Date: Wed, 14 Jun 2017 08:06:31 -0300 Message-ID: <87k24ezv48.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 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: Wed, 14 Jun 2017 11:06:35 -0000 Damien Cassou writes: > David Bremner writes: > >> David Bremner writes: >> >>>> I did that in the patch even though I liked it with >>>> indentation better. >>> >>> I haven't had a chance to test the new version yet, but I think >>> I know what you mean from testing counsel-imenu. Is it worth >>> adding a customization variable so that the user can choose >>> indentation if they have a more sophisticated imenu front end? >> >> So this version is ok with both builtin and counsel imenu front >> ends. It's up to you. Do you want to leave the question of >> controllable indentation for a later commit or add it now? > > if you are ok to merge that right now, that would be perfect for > me. Thanks. OK, done. By the way, I notice a certain overlap of functionality between counsel-imenu support and the way I use tree-view (Z) from show mode. Given the small amount of code I think it's fine to support imenu as well, but I thought I'd mention it. d