I am experimenting with using notmuch remotely over ssh (as in the
NEWS file; i.e. with a script containing ssh user at host notmuch "$@")
This is mostly excellent but it seems to get confused by some queries.
For example those containing brackets or just consisting of *. I think
this is a problem
On Wed, 10 Nov 2010, Mark Walters wrote:
> I am experimenting with using notmuch remotely over ssh (as in the
> NEWS file; i.e. with a script containing ssh user at host notmuch "$@")
> This is mostly excellent but it seems to get confused by some queries.
> For example those containing brackets or
Unfortunately, expansion *is* performed by the remote shell, which is why
your shell quoting approach works (and is necessary). There's really no way
around this, since the ssh client simply joins all of its trailing arguments
with spaces and sends this single string to the ssh server, which exec(
On Fri, 19 Nov 2010, Austin Clements wrote:
> Unfortunately, expansion *is* performed by the remote shell, which is why
> your shell quoting approach works (and is necessary). There's really no way
> around this, since the ssh client simply joins all of its trailing arguments
> with spaces and sen
I am experimenting with using notmuch remotely over ssh (as in the
NEWS file; i.e. with a script containing ssh u...@host notmuch "$@")
This is mostly excellent but it seems to get confused by some queries.
For example those containing brackets or just consisting of *. I think
this is a problem wit
On Wed, 10 Nov 2010, Mark Walters wrote:
> I am experimenting with using notmuch remotely over ssh (as in the
> NEWS file; i.e. with a script containing ssh u...@host notmuch "$@")
> This is mostly excellent but it seems to get confused by some queries.
> For example those containing brackets or ju
Unfortunately, expansion *is* performed by the remote shell, which is why
your shell quoting approach works (and is necessary). There's really no way
around this, since the ssh client simply joins all of its trailing arguments
with spaces and sends this single string to the ssh server, which exec(
On Fri, 19 Nov 2010, Austin Clements wrote:
> Unfortunately, expansion *is* performed by the remote shell, which is why
> your shell quoting approach works (and is necessary). There's really no way
> around this, since the ssh client simply joins all of its trailing arguments
> with spaces and sen
