Derek Martin wrote:
> On Tue, Jun 11, 2019 at 01:45:18PM -0700, Kevin J. McCarthy wrote:
> > On Tue, Jun 11, 2019 at 06:43:25AM -0700, Kevin J. McCarthy wrote:
> > I've pushed a branch up to gitlab, kevin/fcc-before-send. It adds
> > $fcc_before_send, default unset.
>
> Obviously you don't need
On Tue, Jun 11, 2019 at 01:45:18PM -0700, Kevin J. McCarthy wrote:
> On Tue, Jun 11, 2019 at 06:43:25AM -0700, Kevin J. McCarthy wrote:
> I've pushed a branch up to gitlab, kevin/fcc-before-send. It adds
> $fcc_before_send, default unset.
Obviously you don't need to listen to me, but I do want
On Tue, Jun 11, 2019 at 06:43:25AM -0700, Kevin J. McCarthy wrote:
Something like $fcc_order or $fcc_before_send is possible,
I've pushed a branch up to gitlab, kevin/fcc-before-send. It adds
$fcc_before_send, default unset.
The caveats to enabling are as mentioned: message manipulation is
On Tue, Jun 11, 2019 at 08:11:33PM +0200, Nicolas Rachinsky wrote:
> > I hesitate to go far as to say that if you think saving the message
> > first is the right behavior, you are simply wrong... but I'm
> > definitely thinking it. =8^)
>
> You might consider it wrong but I do not seem to be the
Hi Mutters,
I haven't been following the thread but just to reply to a few points
with the names of the posters removed in order to focus on content
rather than who said what:
> > It's not your
> > mail client's job to protect you from every conceibable system
> > failure which might cause data
* Derek Martin [2019-06-11 12:47 -0500]:
> Not only that, but I neglected the fact that if the send fails, the
> file your editor produced in order for it to be passed to Mutt will
> still be on disk, so you do IN FACT still have a copy of the message.
I did just (using my old mutt) set sendmail
* Derek Martin [2019-06-11 12:36 -0500]:
> On Tue, Jun 11, 2019 at 10:04:25PM +1000, Erik Christiansen wrote:
> > In the event that send fails, the local copy is essential for a resend
> > attempt. No ifs, no buts, no maybes. I'm at a loss to imagine any
> > scenario in which mutt should risk
* Derek Martin [2019-06-11 12:16 -0500]:
> On Mon, Jun 10, 2019 at 11:24:11AM +0200, Nicolas Rachinsky wrote:
> > * Jack M [2019-06-04 10:20 -0500]:
> > > On Tue, June 4, 2019 5:30 am, Nicolas Rachinsky wrote:
> > > > The other one (mail sent, but no local copy)
> > >
> > > Why would this
On Tue, Jun 11, 2019 at 12:36:00PM -0500, Derek Martin wrote:
> But also, just because the message failed to send, your ideas and the
> impetus for writing them down didn't vanish. Your brain is the
> back-up.
Not only that, but I neglected the fact that if the send fails, the
file your editor
On Tue, Jun 11, 2019 at 10:04:25PM +1000, Erik Christiansen wrote:
> In the event that send fails, the local copy is essential for a resend
> attempt. No ifs, no buts, no maybes. I'm at a loss to imagine any
> scenario in which mutt should risk inability to write that Fcc, through a
> hang-up or
On Mon, Jun 10, 2019 at 11:24:11AM +0200, Nicolas Rachinsky wrote:
> * Jack M [2019-06-04 10:20 -0500]:
> > On Tue, June 4, 2019 5:30 am, Nicolas Rachinsky wrote:
> > > The other one (mail sent, but no local copy)
> >
> > Why would this situation would ever occur?
>
> A power failure at the
On Tue, Jun 11, 2019 at 10:04:25PM +1000, Erik Christiansen wrote:
If developers insist on the backwards method for themselves, then is an
fcc_order config option possible for the benefit of users seeking the
old reliability?
Something like $fcc_order or $fcc_before_send is possible, but with
Martin wrote:
> Hello everyone,
> I'm using mutt on Debian with several accounts and Firefox as a
> browser. When I click on a mailto: link it opens a new terminal with
> mutt and from all I see it does pick up my muttrc correctly, but the
> new email has "Fcc:" as ~/sent and "From" as myuser
> .
On 10.06.19 11:20, Nicolas Rachinsky wrote:
> * "Kevin J. McCarthy" [2019-06-04 09:44 -0700]:
> > On Tue, Jun 04, 2019 at 12:30:59PM +0200, Nicolas Rachinsky wrote:
> > > Does anybody know the reason of this change?
> >
> > The most recent discussion on mutt-dev was
> >
* Ben Boeckel [2019-06-10 11:56 -0400]:
> If you're this paranoid, the only real fix is to have your editor save a
> backup somewhere before handing it off to mutt in the first place
> anyways. After all, mutt could segfault and lose it before the Fcc!
There is one big difference. If mutt
15 matches
Mail list logo
