Jani Nikula writes:
>
> Heh, I just wanted to see what the response was first before putting in
> the effort to document it. The code comes easy. :)
>
It turns out this series is actually needed (or would be useful) to fix
a bug in the emacs interface; see id:874nguxbvq.fsf at tu-dortmund.de
So
Jani Nikula j...@nikula.org writes:
Heh, I just wanted to see what the response was first before putting in
the effort to document it. The code comes easy. :)
It turns out this series is actually needed (or would be useful) to fix
a bug in the emacs interface; see
> Jameson Graef Rollins writes:
>
>> But don't get me wrong, the CLI is one of the things that makes notmuch
>> so incredibly awesome. It's an email swiss army knife that's there when
>> you need it. But given that even I often need to look at the man page
>> during my occasional CLI usage, I
On Tue, 12 Feb 2013, Jameson Graef Rollins
wrote:
> But don't get me wrong, the CLI is one of the things that makes notmuch
> so incredibly awesome. It's an email swiss army knife that's there when
> you need it. But given that even I often need to look at the man page
> during my occasional
Jameson Graef Rollins writes:
> But don't get me wrong, the CLI is one of the things that makes notmuch
> so incredibly awesome. It's an email swiss army knife that's there when
> you need it. But given that even I often need to look at the man page
> during my occasional CLI usage, I just
On Tue, Feb 12 2013, David Bremner wrote:
> I don't know if this last is just an off the cuff remark, or it
> highlights a difference of opinion. In my view "normal" users of notmuch
> use the CLI frequently. Arguably that means we should take even more
> care over the design of the UI, if we
Jameson Graef Rollins writes:
> But you're right that I'm making a pretty arbitrary distinction. The
> notmuch CLI already includes options to handle output formatting,
> etc. that normal users are probably never going to use in their
> infrequent use of the CLI.
I don't know if this last is
Jameson Graef Rollins jroll...@finestructure.net writes:
But you're right that I'm making a pretty arbitrary distinction. The
notmuch CLI already includes options to handle output formatting,
etc. that normal users are probably never going to use in their
infrequent use of the CLI.
I
On Tue, Feb 12 2013, David Bremner da...@tethera.net wrote:
I don't know if this last is just an off the cuff remark, or it
highlights a difference of opinion. In my view normal users of notmuch
use the CLI frequently. Arguably that means we should take even more
care over the design of the
Jameson Graef Rollins jroll...@finestructure.net writes:
But don't get me wrong, the CLI is one of the things that makes notmuch
so incredibly awesome. It's an email swiss army knife that's there when
you need it. But given that even I often need to look at the man page
during my occasional
On Tue, 12 Feb 2013, Jameson Graef Rollins jroll...@finestructure.net wrote:
But don't get me wrong, the CLI is one of the things that makes notmuch
so incredibly awesome. It's an email swiss army knife that's there when
you need it. But given that even I often need to look at the man page
On Thu, Feb 07 2013, David Bremner da...@tethera.net wrote:
In my experience the environment variable is somewhat dangerous to use
while testing. If left set to the wrong value, it can lead the loss of
tag information.
I have never noticed this to be an issue, but if it is variables can be
On Wed, 06 Feb 2013, Jameson Graef Rollins
wrote:
> On Tue, Jan 29 2013, Jani Nikula wrote:
>> Hi all, the goal here is to add support for --config=FILE option at the
>> notmuch top level (e.g. 'notmuch --config=FILE search foo'). In order to
>> achieve this neatly, I ended up moving config
Jameson Graef Rollins jroll...@finestructure.net writes:
Is there some benefit to having a command line option for this that I
don't see?
In my experience the environment variable is somewhat dangerous to use
while testing. If left set to the wrong value, it can lead the loss of
tag
On Tue, Jan 29 2013, Jani Nikula j...@nikula.org wrote:
Hi all, the goal here is to add support for --config=FILE option at the
notmuch top level (e.g. 'notmuch --config=FILE search foo'). In order to
achieve this neatly, I ended up moving config open/close to main() from
subcommands. This
On Wed, 06 Feb 2013, Jameson Graef Rollins jroll...@finestructure.net wrote:
On Tue, Jan 29 2013, Jani Nikula j...@nikula.org wrote:
Hi all, the goal here is to add support for --config=FILE option at the
notmuch top level (e.g. 'notmuch --config=FILE search foo'). In order to
achieve this
Hi all, the goal here is to add support for --config=FILE option at the
notmuch top level (e.g. 'notmuch --config=FILE search foo'). In order to
achieve this neatly, I ended up moving config open/close to main() from
subcommands. This isn't a bad thing, because all notmuch commands opened
the
Hi all, the goal here is to add support for --config=FILE option at the
notmuch top level (e.g. 'notmuch --config=FILE search foo'). In order to
achieve this neatly, I ended up moving config open/close to main() from
subcommands. This isn't a bad thing, because all notmuch commands opened
the
18 matches
Mail list logo
