On Fri, Jun 01 2012, Jameson Graef Rollins
wrote:
> There's a bug in the configure script that is causing auto-reruns of
> ./configure to not inherit original command line options if there was
> more than one. For instance, if I run:
>
> ./configure --with-gmime-version=2.4
---
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20120602/b9814ba6/attachment.pgp>
Without proper quoting the DEFAULT_IFS was getting set incorrectly,
which was causing problems with the storage of some variables later in
the script. Quoting fixes the problem.
---
Thanks to Tomi for the inspiration for this fix. I don't know how I
missed such a simple solution initially.
Quoting David Bremner (2012-06-01 20:46:59)
> Jameson Graef Rollins writes:
>
> > I think the zeroth-order thing we have to do then is to have the build
> > include the bindings as well. Then everyone will be able to see
> > immediately if the bindings are broken. I wouldn't even make it an
>
Justus Winter <4winter at informatik.uni-hamburg.de> writes:
>
> I like the idea. The thing with the python bindings is that building
> them wont detect any errors, one has to import the module. Quick and
> dirty python oneliner that doesn't even require installing the
> bindings:
I guess the
On Fri, Jun 01 2012, Jameson Graef Rollins jroll...@finestructure.net wrote:
There's a bug in the configure script that is causing auto-reruns of
./configure to not inherit original command line options if there was
more than one. For instance, if I run:
./configure --with-gmime-version=2.4
Without proper quoting the DEFAULT_IFS was getting set incorrectly,
which was causing problems with the storage of some variables later in
the script. Quoting fixes the problem.
---
Thanks to Tomi for the inspiration for this fix. I don't know how I
missed such a simple solution initially.
On Sat, Jun 02 2012, Tomi Ollila tomi.oll...@iki.fi wrote:
I tried some alternatives on command line:
$ readonly FOO1=$IFS
$ echo $FOO1 | od -f x1
000 0a
001
$ readonly FOO2=$IFS
$ echo $FOO2 | od -f x1
000 20 09 0a 0a
004
$ FOO3=$IFS
$ readonly FOO3
$ echo $FOO4 |
On Fri, Jun 1, 2012 at 11:01 AM, Jameson Graef Rollins
jroll...@finestructure.net wrote:
On Fri, Jun 01 2012, David Bremner da...@tethera.net wrote:
I guess we should clarify what it means to accept some code into
contrib. Do we accept to maintain it even after the original contributor
loses
On Wed, May 23, 2012 at 4:15 AM, Michal Sojka sojk...@fel.cvut.cz wrote:
I think the current plan is to use the same decoding lookup table that
notmuch-show is using in reply too.
Which table do you refer to? notmuch-show-handlers-for?
Yep, that looks like the right thing.
I've been
10 matches
Mail list logo
