On Thu, Feb 14, 2013 at 03:13:22PM +0100, Profpatsch wrote:
>Plus it still takes about 10 steps to configure a new account with
>offlineimap, mutt and msmtp, there is nothing to automate this and
>every config is different. Whoa.
Mutt was designed with the UNIX philosophy in mind. When users
Michael Elkins writes:
> On Thu, Feb 14, 2013 at 03:13:22PM +0100, Profpatsch wrote:
>>Plus it still takes about 10 steps to configure a new account with
>>offlineimap, mutt and msmtp, there is nothing to automate this and
>>every config is different. Whoa.
>
> Mutt was designed with the UNIX
On Jo, 14 feb 13, 00:36:58, Profpatsch wrote:
So much for copying a basic rc from someone else.
There's no problem with that, as long as you take the time to read and
understand what each option does.
Kind regards,
Andrei
--
If you can't explain it simply, you don't understand it well
On Thu, Feb 14, 2013 at 12:36:58AM +0100, Profpatsch wrote:
On 13-02-13 02:35pm, Kevin J. McCarthy wrote:
A more likely idea is to check whether you have $pipe_decode set.
BRILLIANT!
So much for copying a basic rc from someone else.
Of course, that was it and I’m officially an idiot.
On Thu, Feb 14, 2013 at 09:37:13AM +0100, Stefano Zacchiroli wrote:
I guess it would also be nice to actually disable $pipe_decode in the
relevant Mutt macros, but I'm not sure about to do that without
interfering with user desired configuration. Kevin: do you know if there
is a common Mutt
On 13-02-14 09:37am, Stefano Zacchiroli wrote:
More isolation for this kind of
things in Mutt would definitely be welcome...
Maybe it’s time for an overhaul of the mutt configuration from the
ground up. I know, it’s “configure once and be done with it”, but it
took me two hard weeks to get that
On Thu, Feb 14, 2013 at 03:13:22PM +0100, Profpatsch wrote:
Plus it still takes about 10 steps to configure a new account with
offlineimap, mutt and msmtp, there is nothing to automate this and
every config is different. Whoa.
Mutt was designed with the UNIX philosophy in mind. When users
Stefano Zacchiroli wrote:
Right, but still a more graceful failure model would be nice.
Please find attached a patch that in such cases should 1) give a
supposedly nice error message explaining what's going on and 2) empty
the results dir to avoid showing you unrelated results. It works for
Hi Kevin and others,
On Thu, Feb 14, 2013 at 03:06:51PM -0800, Kevin J. McCarthy wrote:
Here are some proposed improved macros. (I'll attach a patch file in
another email.) Despite my earlier warning about not line-breaking
macros, these are getting a bit unreadable. We may want to see
Profpatsch wrote:
Since I don’t get your bug tracking system (d’oh ;), here is a bug I
encountered with notmuch-mutt using this macro I guess was from the
“official” tutorial:
# Construct a thread ouf of the marked mail (or something like that,
# doesn’t work atm (errors out))
macro
On 13-02-13 02:35pm, Kevin J. McCarthy wrote:
A more likely idea is to check whether you have $pipe_decode set.
If you have this set, you need to make sure you are not weeding out
message-id with 'ignore'.
In fact, I've just tried this, and I can replicate the problem and exact
error
[ many thanks to David Bremner for the forward ]
On Tue, 12 Feb 2013 01:58:01 +0100, Profpatsch wrote:
# Construct a thread ouf of the marked mail (or something like that,
# doesn’t work atm (errors out))
snip
I hope this still works, best to put it on one line I guess.
Error message:
Use
On Tue, Feb 12, 2013 at 05:55:31PM +0100, Profpatsch wrote:
Do you still have the mail in question? Can you verify if it is the
case or not?
That’s my problem: It works with no mail.
I initialized notmuch and this one works:
I'm sorry, but I still don't get it. What do you mean with no
13 matches
Mail list logo
