Re: GPGME error

[Kevin J. McCarthy]

On Thu, Mar 15, 2018 at 10:03:22AM +, Darac Marjal wrote:
> I managed to see it read "[setting sender] mailbox ...". That was
> enough for me to find the function "void mutt_gpgme_set_sender()".
> 
> I can see that this function sets the sender for gpgme (presumably so it
> knows who to sign as), but my question is why is the message "[setting
> sender] mailbox: %s" displayed using mutt_error()?

Hi Darac,

Thanks for the report.  As you guessed, it shouldn't be using
mutt_error() here.  I don't think the message has much utility, given
how quickly it flies by, so I will change it to use a debug statement
instead.

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


signature.asc
Description: PGP signature

Re: View HTML without autoview

[David Woodfall]

On (15/03/18 22:32), Erik Christiansen  put forth the 
proposition:

On 14.03.18 23:23, David Woodfall wrote:

On (14/03/18 16:01), Ian Zimmerman  put forth the 
proposition:
> On 2018-03-14 13:13, David Woodfall wrote:
>
> > > Previously, I used elinks and it works fine with autoview, however
> > > when I try to pipe to it it also renders the headers instead of just
> > > the body.
>
> When you try a pipe, is that piping the message (as a pipe command would
> do in the index view) or just the html MIME part (as a pipe command in
> the attachment view would do)?

It does the whole message. I seem to get messages where the entire
message is html with no separate html part. Mostly from ebay.co.uk,
even though I set to receive mail in plain text only.


To strip headers there, is pipe_decode useful? The manual says: "When
set, Mutt will weed headers and will attempt to decode the messages
first." Whether an "ignore *" is also needed to make it weed out all
headers, I haven't tested.

Erik


That works quite well and has the benefit of running elinks
interactively, which means I can open links in an external app.

I made a macro:

":unauto_view text/html:set pipe_decodeelinks 
-force-html:auto_view text/html"

The only problem is that for some reason if I run it on an attachment
it marks the attachment for deletion. I can't figure out why it's
doing it. I first used D for the macro, then changed it to Z in case
somehow D was being confused with d, but the problems remains. I only
ever use lowercase d for delete (s+Trash\n). Nothing shows in the help
menu that looks like it would do it.

Re: View HTML without autoview

[Erik Christiansen]

On 14.03.18 23:23, David Woodfall wrote:
> On (14/03/18 16:01), Ian Zimmerman  put forth the 
> proposition:
> > On 2018-03-14 13:13, David Woodfall wrote:
> > 
> > > > Previously, I used elinks and it works fine with autoview, however
> > > > when I try to pipe to it it also renders the headers instead of just
> > > > the body.
> > 
> > When you try a pipe, is that piping the message (as a pipe command would
> > do in the index view) or just the html MIME part (as a pipe command in
> > the attachment view would do)?
> 
> It does the whole message. I seem to get messages where the entire
> message is html with no separate html part. Mostly from ebay.co.uk,
> even though I set to receive mail in plain text only.

To strip headers there, is pipe_decode useful? The manual says: "When
set, Mutt will weed headers and will attempt to decode the messages
first." Whether an "ignore *" is also needed to make it weed out all
headers, I haven't tested.

Erik

Re: Reply with another email as attachment?

[Erik Christiansen]

On 14.03.18 10:48, Tim Chase wrote:
> On 2018-03-15 00:37, Erik Christiansen wrote:
> > Yup, forward:
> > View the email to attach.
> > Hit 'f', and mutt will prompt: Forward as attachment? ([yes]/no):
> > Hit Enter, compose the accompanying email, with forward address,
> > etc.
> 
> I just tried this (both with an individual message as well as tagging
> multiple and using ";f" to forward the tagged messages) and they
> ended up in-line by default.  It looks like you might have to fiddle
> with the mime_forward quad-option which defaults to "no", setting it
> to an "ask*" option.

Uh-oh, you're right. Dusting off my .muttrc, I see that I set
mime_forward to ask-yes.

Erik

GPGME error

[Darac Marjal]

Hello all,

For a while now, when I sign messages with GPG, I see an error message 
flash up briefly before being replaced by the signing prompt. Up until 
now, I'd not been able to read the message before it disappeared, but 
today (perhaps my terminal was being a bit slow) I managed to see it 
read "[setting sender] mailbox ...". That was enough for me to find the 
function "void mutt_gpgme_set_sender()".


I can see that this function sets the sender for gpgme (presumably so it 
knows who to sign as), but my question is why is the message "[setting 
sender] mailbox: %s" displayed using mutt_error()? Is it *actually* an 
error to set the sender? Should this have been implied elsewhere, for 
example? Or is this just a bit of debugging information that's being 
rather too loudly logged?


Thanks.
--
For more information, please reread.


signature.asc
Description: PGP signature