[PATCH] Implement a simple read-eval-print loop.

2010-11-22 Thread Michael Hudson
On Sun, 21 Nov 2010 22:51:29 +0100, Michal Sojka wrote: > On Sun, 21 Nov 2010, Michal Sojka wrote: > > This is a great idea. Now I use this script to invoke notmuch remotely > > and I don't have to create master connection manually. > > > > #!/bin/bash > > socket="$HOME/.ssh/notmuch-connection"

[PATCH] Implement a simple read-eval-print loop.

2010-11-21 Thread Michal Sojka
On Sun, 21 Nov 2010, Michal Sojka wrote: > This is a great idea. Now I use this script to invoke notmuch remotely > and I don't have to create master connection manually. > > #!/bin/bash > socket="$HOME/.ssh/notmuch-connection" > if [[ ! -S $socket ]]; then > # Create master connection in

[PATCH] Implement a simple read-eval-print loop.

2010-11-21 Thread Michal Sojka
On Sun, 21 Nov 2010, Austin Clements wrote: > Out of curiosity, why not simply use SSH control mastering? I use control mastering, but it still takes about five seconds to display notmuch hello screen. > You could even make that part of the "standard" remote notmuch script, > without requiring

[PATCH] Implement a simple read-eval-print loop.

2010-11-21 Thread Austin Clements
What about notmuch count query1; notmuch count query2; ... all as a single command issued by notmuch-hello? That should give exactly the same output, but eliminates the network round-trips without special support from count. It would be interesting to see how this compares with your modified

[PATCH] Implement a simple read-eval-print loop.

2010-11-21 Thread Austin Clements
Out of curiosity, why not simply use SSH control mastering? You could even make that part of the "standard" remote notmuch script, without requiring the user to change anything in their ssh configuration. This should be just as fast as a remote notmuch shell, but retains the ability to run

Re: [PATCH] Implement a simple read-eval-print loop.

2010-11-21 Thread Austin Clements
Out of curiosity, why not simply use SSH control mastering? You could even make that part of the standard remote notmuch script, without requiring the user to change anything in their ssh configuration. This should be just as fast as a remote notmuch shell, but retains the ability to run

Re: [PATCH] Implement a simple read-eval-print loop.

2010-11-21 Thread Michal Sojka
On Sun, 21 Nov 2010, Michal Sojka wrote: This is a great idea. Now I use this script to invoke notmuch remotely and I don't have to create master connection manually. #!/bin/bash socket=$HOME/.ssh/notmuch-connection if [[ ! -S $socket ]]; then # Create master connection in background

Re: [PATCH] Implement a simple read-eval-print loop.

2010-11-21 Thread Michael Hudson
On Sun, 21 Nov 2010 22:51:29 +0100, Michal Sojka sojk...@fel.cvut.cz wrote: On Sun, 21 Nov 2010, Michal Sojka wrote: This is a great idea. Now I use this script to invoke notmuch remotely and I don't have to create master connection manually. #!/bin/bash

Re: [PATCH] Implement a simple read-eval-print loop.

2010-11-21 Thread Austin Clements
What about notmuch count query1; notmuch count query2; ... all as a single command issued by notmuch-hello? That should give exactly the same output, but eliminates the network round-trips without special support from count. It would be interesting to see how this compares with your modified

[PATCH] Implement a simple read-eval-print loop.

2010-11-20 Thread Michal Sojka
On Sat, 20 Nov 2010, servilio wrote: > This implementation uses GNU readline for the prompt and command > history, with the default file completion enabled. GLib is used to > split the read line into an arguments list. Hi, I haven't tested it yet, but it seems to be exactly the piece of code I

[PATCH] Implement a simple read-eval-print loop.

2010-11-20 Thread servilio
Hi Michal, On 20 November 2010 16:15, Michal Sojka wrote: > On Sat, 20 Nov 2010, servilio wrote: >> This implementation uses GNU readline for the prompt and command >> history, with the default file completion enabled. GLib is used to >> split the read line into an arguments list. > > Hi, > > I

[PATCH] Implement a simple read-eval-print loop.

2010-11-20 Thread servilio
This implementation uses GNU readline for the prompt and command history, with the default file completion enabled. GLib is used to split the read line into an arguments list. --- Makefile.local |2 +- configure | 40 ++- notmuch.c | 115

[PATCH] Implement a simple read-eval-print loop.

2010-11-20 Thread servilio
This implementation uses GNU readline for the prompt and command history, with the default file completion enabled. GLib is used to split the read line into an arguments list. --- Makefile.local |2 +- configure | 40 ++- notmuch.c | 115

Re: [PATCH] Implement a simple read-eval-print loop.

2010-11-20 Thread Michal Sojka
On Sat, 20 Nov 2010, servilio wrote: This implementation uses GNU readline for the prompt and command history, with the default file completion enabled. GLib is used to split the read line into an arguments list. Hi, I haven't tested it yet, but it seems to be exactly the piece of code I

Re: [PATCH] Implement a simple read-eval-print loop.

2010-11-20 Thread servilio
Hi Michal, On 20 November 2010 16:15, Michal Sojka sojk...@fel.cvut.cz wrote: On Sat, 20 Nov 2010, servilio wrote: This implementation uses GNU readline for the prompt and command history, with the default file completion enabled. GLib is used to split the read line into an arguments list.