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 91D426DE12DD for ; Sun, 1 Oct 2017 23:49:05 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.097 X-Spam-Level: X-Spam-Status: No, score=0.097 tagged_above=-999 required=5 tests=[AWL=0.158, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.211, SPF_PASS=-0.001] 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 mGKbHdl8BplL for ; Sun, 1 Oct 2017 23:49:04 -0700 (PDT) Received: from mail-wr0-f178.google.com (mail-wr0-f178.google.com [209.85.128.178]) by arlo.cworth.org (Postfix) with ESMTPS id 529466DE12DC for ; Sun, 1 Oct 2017 23:49:04 -0700 (PDT) Received: by mail-wr0-f178.google.com with SMTP id p10so1317092wrc.6 for ; Sun, 01 Oct 2017 23:49:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:in-reply-to:references:date:message-id:mime-version; bh=rGU+WR1TQdz8rV2z2TnKXIiQeCsnI6j5OKcjyDiC7lw=; b=MTyB88yk1GkAjGvdTjwHnlrpkrkttugFwIWd7RxsnX7Rccy84Moa70K+v30nco2G2H hL8Vd72qLoDYQLn5r3sT0jz2yQRf/H4QQaLfURXLd48/iNSTeiwileUVxn4ktBXS8oVZ T1Ubuxj0Q9wkngFoXdB0iPMAWnkky6EnPMXyytPHIp9mSlYlMxeYso7I0BIatdIumQxC ynQxS3XtOMsffIZ3/LsH9BbQNG0YWKCjqJivW+wXiVvyKbRCbDwN+biKSRIoCt/4cDvw dAXHTfGky49rqic3NZp02TlP3eiJYr/l0s3mPxGaVPrOVjeXmxpxVlH82+0QcFvqFTSn IiKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version; bh=rGU+WR1TQdz8rV2z2TnKXIiQeCsnI6j5OKcjyDiC7lw=; b=cj1fb/5+t2XXcrr8DgrUifallJ/PhFU7XU6v8jCFQXoL/9/IXLz8DsjOc04Ii7sT3V +JoXPs9nteDVr247pECYM+0orTohP5pZJcz/Dsh76H9LrhcUu92EwKrKHnAFks9tUpSS m3taO6n/HLjPXH1OBh0L8KTuyDWVsvHuuBfnaAipKIw5oHqa+5TfiNQokoyXARX/2FbN vxfv8lxVkgpabg7p5pjOjRJR/poT1dAADSZ2ZgAJ6Q4KFYjaksrnAKJw2k9Ze7vApf7R oWv3VhiEH2AQIQHKTUVthMHum1ljy9N/CgVjdmr0LK6XP59HhJ/wL7J1o2CJy/TGxQqs QjsQ== X-Gm-Message-State: AHPjjUjrXPIMkriEY/qCOXtKoy3w7C1vJzpUrBd/mCjGrV7T1tAYgIZi ibS0PnG3R9fTeCRplxdbUjY= X-Google-Smtp-Source: AOwi7QBuVkhxyEzgvt/KwxcM+l3C5daZVpra5RFe3Lzlq+lehGg7MMxmSqwQbfpvYxlnEBfzBzRbYA== X-Received: by 10.223.145.163 with SMTP id 32mr13191303wri.279.1506926941481; Sun, 01 Oct 2017 23:49:01 -0700 (PDT) Received: from localhost (188.28.158.20.threembb.co.uk. [188.28.158.20]) by smtp.gmail.com with ESMTPSA id l37sm9226918wrl.47.2017.10.01.23.49.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Oct 2017 23:49:00 -0700 (PDT) From: Mark Walters To: Arun Isaac , notmuch@notmuchmail.org Subject: Re: notmuch-emacs: Fcc to top-level directory given by database.path In-Reply-To: <41bd216a.ADkAADT7Si8AAAAAAAAAAAPvrI0AAAACwQwAAAAAAAW9WABZ0Tyw@mailjet.com> References: <87fubd7ibl.fsf@tethera.net> <09e68393.AEEAQ2wzaJcAAAAAAAAAAAPvrI0AAAACwQwAAAAAAAW9WABZxnU0@mailjet.com> <87a81k70pr.fsf@tethera.net> <874lrkn1ps.fsf@qmul.ac.uk> <41bd216a.ADkAADT7Si8AAAAAAAAAAAPvrI0AAAACwQwAAAAAAAW9WABZ0Tyw@mailjet.com> Date: Mon, 02 Oct 2017 07:48:54 +0100 Message-ID: <87h8vi11ux.fsf@qmul.ac.uk> 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: Mon, 02 Oct 2017 06:49:05 -0000 Hi On Sun, 01 Oct 2017, Arun Isaac wrote: > Mark Walters writes: > >> Incidentally, I think "/" is an alternative for the fcc line which >> already works, which is "\"/\" in notmuch-fcc-dirs. > > Perhaps, notmuch should be made to tolerate a "/" at the beginning of the > Fcc folder argument. That is, notmuch should not complain about absolute > paths, and it should interpret these as relative to the root. To > maintain backward compatibility, we could add a "/" at the beginning if > it is not already there. > > So, > > "/" => database.path > "/sent" => database.path/sent > "sent" => database.path/sent > > etc. > > Is this a better idea? The reason for the warning is that this behaviour is completely different from what you would get with normal file fcc. Given that, I am a little reluctant to drop the warning. Best wishes Mark