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 A633C6DE0B2B for ; Fri, 2 Dec 2016 17:58:11 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.006 X-Spam-Level: X-Spam-Status: No, score=-0.006 tagged_above=-999 required=5 tests=[AWL=0.005, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 gSmBBs33iB4H for ; Fri, 2 Dec 2016 17:58:10 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id A483C6DE0B25 for ; Fri, 2 Dec 2016 17:58:10 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1cCzaE-0007M9-CC; Fri, 02 Dec 2016 20:57:46 -0500 Received: (nullmailer pid 19770 invoked by uid 1000); Sat, 03 Dec 2016 01:58:06 -0000 From: David Bremner To: Matthew Lear Cc: notmuch@notmuchmail.org Subject: Re: some issues with emacs 25 In-Reply-To: <583564F9.9020800@bubblegen.co.uk> References: <58126A0E.8030702@bubblegen.co.uk> <05B6BA4C-5810-4351-AAA9-AEBC2F59D1A9@bubblegen.co.uk> <582364C7.5060805@bubblegen.co.uk> <87lgws6wf3.fsf@tethera.net> <87vavow31u.fsf@tethera.net> <87inrhvs2b.fsf@tethera.net> <58345525.1050805@bubblegen.co.uk> <583564F9.9020800@bubblegen.co.uk> Date: Fri, 02 Dec 2016 21:58:06 -0400 Message-ID: <87lgvxu635.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 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: Sat, 03 Dec 2016 01:58:11 -0000 Matthew Lear writes: > > I'd happily post some debug info to help analyse this if somebody could > give me a few pointers about what would be needed and the emacs-fu > needed to generate this. > I think the best thing at this point would be to find (or create) another public message where you can duplicate the problem. d