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 5E6C96DE0A53 for ; Sun, 30 Oct 2016 05:39:20 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.051 X-Spam-Level: X-Spam-Status: No, score=0.051 tagged_above=-999 required=5 tests=[AWL=-0.079, 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 8biwyFYgKWbS for ; Sun, 30 Oct 2016 05:39:17 -0700 (PDT) Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by arlo.cworth.org (Postfix) with ESMTPS id 69E096DE0962 for ; Sun, 30 Oct 2016 05:39:17 -0700 (PDT) Received: by mail-wm0-f53.google.com with SMTP id t79so6546352wmt.0 for ; Sun, 30 Oct 2016 05:39:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version; bh=lWmB3Xc0K77AAAXOW+eHgEfNwSmGMl3r1ssKGXBUi7M=; b=Wy/V9Wvddfs4naLe9HJnVbwgfi02r0IwSTaWRAnXSE6GL6evT8dg77kDqEGo0KvOHI OQ1XCHVt+QmOWOp+7nU0kkrbADaH8IjiocUdHYv1McZFFYU7k7XvmwSJbVIvvGekkXRy 8T0FzAKcWOFmtWI4IRRapwFhlDzcExvqfNMm7E2ak8U+iIyiOKzWiPFA8O1Yudj/oawX STIoPbGKrVXBx6L8SeBN4q/jN2Zc3b+XHm9yhSbrxyg6HPQbB2vuaS8ImR38LCmpicgc VPjuIbqYDU7BulCTBFRW59JDcl/vHkpryxH/ovRbT6OGRh7RMUTlmPHzM5R8ag7vfLWe MiLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references :user-agent:date:message-id:mime-version; bh=lWmB3Xc0K77AAAXOW+eHgEfNwSmGMl3r1ssKGXBUi7M=; b=UiuzK0YHM1AUU+2sSZlqnx8+1yXtyBnLZc39+XY38pz8WkML8oJ456f8e7u1oLMDuh MB+++M4cPQ8NIxvdbqAg7fIq5isVP4eEVXh7EH3/kcgM+DtbgD3qsfg6gOthV5l+y9M7 b3iRJX6ADzbd1p04di4X8bNrtchp1YpkTPAPyGTywrEJuiO+gwTBNVPxsLSCkA/yCyUN l7abLvdOhBgxcrY3ralSnjDKu1yRi/lxzIPbYLYGV/VlYLDIiYTWhKX1iFPEyVuenMrG I0NXYBilArirYsglnYnAFga9l1aRbCpOrx+ZyCaCKcMmD75Sx3Z0gCnCemlKvTQt7zjP PPWg== X-Gm-Message-State: ABUngvdZisCOKE4qoZaZrP14/HCHjdfWQvYloaqsnFi3eoPedVTA2k8fIwW0FiN93s6fSA== X-Received: by 10.28.67.68 with SMTP id q65mr6910210wma.119.1477831155346; Sun, 30 Oct 2016 05:39:15 -0700 (PDT) Received: from localhost (5751dfa2.skybroadband.com. [87.81.223.162]) by smtp.gmail.com with ESMTPSA id m5sm19274404wmd.17.2016.10.30.05.39.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Oct 2016 05:39:14 -0700 (PDT) From: Mark Walters To: David Bremner , Jani Nikula , Tomi Ollila Cc: Notmuch Mail Subject: Re: rfc for notmuch remote access script In-Reply-To: <87pomit6j6.fsf@tethera.net> References: <87lgx9ln56.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me> <874m3wvjzx.fsf@tethera.net> <8760oa41s6.fsf@nikula.org> <87pomit6j6.fsf@tethera.net> User-Agent: Notmuch/0.22+86~ga823f40 (https://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Sun, 30 Oct 2016 12:39:14 +0000 Message-ID: <87zilmxb7x.fsf@qmul.ac.uk> 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: Sun, 30 Oct 2016 12:39:20 -0000 On Sun, 30 Oct 2016, David Bremner wrote: > Jani Nikula writes: > >> >> Personally, I prefer a simple script that assumes a certain type of ssh >> client configuration. We can typically reference documentation written >> by others how to do that, and just say "put that stuff under a Host >> notmuch section in ~/.ssh/config". Hi The only possible downside I can see with this is if the address for the notmuch-server varies. For example my router does NAT the address from inside and outside my home network is different. I don't know if that is a common setup, and quite plausibly I could configure things better. I only mention it as it might be easier to change an environment variable, than change the .ssh/config file. Quite plausibly though the simpler common case outweighs that. If we did want to support my use case above, maybe we could have an environment variable to say which .ssh/config section to use, which most people could completely ignore? > OK, I misunderstood, and thought you wanted to edit the script after > installation. Hence my question about installing into $HOME. > > I'm not using remote access, and I don't really have opinions about the > best way to do it. I do have 2 concerns about the overall idea > > 1. I worry about the maintenance burden of extra code ./configure > 2. I worry about promoting remote-notmuch for non-experts when the > situation with gpg seems quite broken, at least for people not > willing to store private key material on the server. I wonder if we could do the following -- 1) have 2 separate config targets for notmuch-cli and notmuch-emacs so you can install one without the other. 2) Have things under contrib which config/make can install. Then this script could go in contrib, which would be a clear signal that it is not fully supported. Moreover, point 2 would go very nicely with Jani's other patch id:1477140605-3011-1-git-send-email-jani@nikula.org for notmuch prefixed commands. It would mean we could have various notmuch extensions in contrib and the user could install any they wanted. Best wishes Mark