From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 10B62431FAF for ; Sat, 14 Jun 2014 05:24:06 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] 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 J6lK3NSRcrmI for ; Sat, 14 Jun 2014 05:23:58 -0700 (PDT) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id B8AFB431FBD for ; Sat, 14 Jun 2014 05:23:53 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1Wvmzw-00059E-9O; Sat, 14 Jun 2014 09:23:52 -0300 Received: (nullmailer pid 6737 invoked by uid 1000); Sat, 14 Jun 2014 12:23:48 -0000 From: David Bremner To: Anye Li , notmuch@notmuchmail.org Subject: Re: debian emacs flavor? In-Reply-To: <878uoz6atd.fsf@zancas.localnet> References: <87ppiwp0xf.fsf@mint.i-did-not-set--mail-host-address--so-tickle-me> <878uoz6atd.fsf@zancas.localnet> User-Agent: Notmuch/0.18+13~g1adde01 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Sat, 14 Jun 2014 09:23:48 -0300 Message-ID: <8761k365nv.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain 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: Sat, 14 Jun 2014 12:24:06 -0000 David Bremner writes: > > Hi Anye; > > I don't think that error message is fatal. The flavour "emacs" is for > the source files (un-bytecompiled) as far as I recall. In any case the > same message is received on Debian, so it isn't raspian specific. > As a followup, if you try the current 'release' branch, that message should be gone. d