Hello Mutt team!
I installed Mutt on AntiX Linux and can read my Yahoo mail. When sending
though, I’m asked for a passphrase. I don’t have one, so then I get “no key
specified” and I can’t send.
My muttrc is basic with nothing on passphrase or SMIME.
Any suggestions? Thanks!
Hi,
https://unix.stackexchange.com/questions/108485/send-email-written-in-markdown-using-mutt
I see the following muttrc command is used to compose an HTML message
on the above URL. I just want to inspect the mime message in the
command line without using the GUI.
macro compose \e5 "F pandoc -s
Hi Peng,
the y^T^U means:
The first "command" of the macro is `F` which is default binding for
. This is how You process message through pandoc and it
asks a question about overwriting the original message in tempfile
that's why there's a `y` to confirm the question. When you execute it on
Hello Peng,
While this might not be the answer for how to use pandoc, it is an answer
to the question in the subject, so I hope it's right.
I'm the author of https://github.com/amitramon/plainMail2HTML - this
is a simple tool that allows for generating HTML mime part from any
email sent from Mut
I just want to generate the HTML mine message. The instruction
requires the set up of mutt, which I want to avoid. Is
`bin/plain2html` for generating HTML mime message from a plain text?
Can you make the plain2html module installable so that the following
command will work? Thanks.
$ bin/plain2htm
On Sun, Jan 24, 2021 at 10:04:50PM -0600, boB Stepp wrote:
> 1) Mutt erratically loses connection with Gmail and I have to
> manually reconnect. Sometimes this happens rather frequently as in
> multiple instances within an hour. I am confident it is not my
> Internet connection, which is normal
I've winnowed my failing pattern down to
~( !~>(~P) )
which is not accepted. A bare:
!~>(~P)
is accepted.
What I'm trying to do is colour yellow messages in threads which are
either:
- flagged
or:
- personal, and not replied, and not from %info, and without an
immediate child from
On Mon, Feb 08, 2021 at 12:49:32PM +1100, Cameron Simpson wrote:
I've winnowed my failing pattern down to
~( !~>(~P) )
which is not accepted. A bare:
I think this is from a small bug with trailing whitespace inside
parentheses. Try
~(!~>(~P))
I'll work on fixing that quirk.
--
Kevin
