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 1A8F36DE02AC for ; Thu, 13 Oct 2016 15:40:50 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.131 X-Spam-Level: X-Spam-Status: No, score=0.131 tagged_above=-999 required=5 tests=[AWL=0.141, 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 pdCd8iXwYHBA for ; Thu, 13 Oct 2016 15:40:49 -0700 (PDT) Received: from picnicpark.org (picnicpark.org [130.94.181.238]) by arlo.cworth.org (Postfix) with ESMTP id 5F8216DE0297 for ; Thu, 13 Oct 2016 15:40:49 -0700 (PDT) Received: (qmail 23643 invoked by uid 13806); 13 Oct 2016 22:40:48 -0000 Received: from unknown (HELO gw.picnicpark.org) (camalot@[108.225.17.54]) (envelope-sender ) by 130.94.181.238 (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 13 Oct 2016 22:40:48 -0000 Received: from kea-tablet.picnicpark.org (gw.picnicpark.org [127.0.0.1]) by gw.picnicpark.org (Postfix) with ESMTPSA id 6BDB212A0B37 for ; Thu, 13 Oct 2016 15:40:40 -0700 (PDT) Message-ID: <1476398420.2162.1.camel@picnicpark.org> Subject: Re: [PATCH] Expand docstrings about fcc using notmuch-insert From: Keith Amidon To: notmuch@notmuchmail.org Date: Thu, 13 Oct 2016 15:40:20 -0700 In-Reply-To: <20161011045222.15723-1-camalot@picnicpark.org> References: <20161011045222.15723-1-camalot@picnicpark.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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: Thu, 13 Oct 2016 22:40:50 -0000 Did my attempt to submit via git send-email the documentation patch quoted below somehow not get forwarded by the list server? I never got a copy forwarded by the list but just assumed that it was suppressing copies to the authors. Having observed that folks here are usually very good about reviewing patch submissions quickly and not having gotten any feedback, I'm wondering if something went wrong after all... --- Keith On Mon, 2016-10-10 at 21:52 -0700, Keith Amidon wrote: > This commit expands docstrings for notmuch-fcc-dirs and > notmuch-maildir-fcc-with-notmuch-insert to describe how quoted > strings > are processed and make the ability to configure sent folders > containing > whitespace more discoverable. > --- >  emacs/notmuch-maildir-fcc.el | 13 ++++++++++--- >  1 file changed, 10 insertions(+), 3 deletions(-) > > diff --git a/emacs/notmuch-maildir-fcc.el b/emacs/notmuch-maildir- > fcc.el > index 95e5650..cfe1931 100644 > --- a/emacs/notmuch-maildir-fcc.el > +++ b/emacs/notmuch-maildir-fcc.el > @@ -54,7 +54,10 @@ If `notmuch-maildir-use-notmuch-insert' is set > (the default) then >  the header should be of the form \"folder +tag1 -tag2\" where >  folder is the folder (relative to the notmuch mailstore) to store >  the message in, and tag1 and tag2 are tag changes to apply to the > -stored message. > +stored message.  This string is split using `split-string-and- > unquote', > +so a folder name containing whitespace can be specified by > +quoting the whitespace with an immediately preceeding backslash > +or surrounding the entire folder name in double quotes. >   >  If `notmuch-maildir-use-notmuch-insert' is nil then the Fcc >  header should be the directory where the message should be > @@ -230,8 +233,12 @@ should be a list of tag changes to apply to the > inserted message." >  The fcc-header should be of the form \"folder +tag1 -tag2\" where >  folder is the folder (relative to the notmuch mailstore) to store >  the message in, and tag1 and tag2 are tag changes to apply to the > -stored message. If CREATE is non-nil then create the folder if > -necessary." > +stored message. This string is split using `split-string-and- > unquote', > +so a folder name containing whitespace can be specified by quoting > +the whitespace with an immediately preceeding backslash or > +surrounding the entire folder name in double quotes. > + > +If CREATE is non-nil then create the folder if necessary." >    (let* ((args (split-string-and-unquote fcc-header)) >    (folder (car args)) >    (tags (cdr args)))