No matching mailcap entry found. Viewing as text.

[a***@gmail.com]

Hello everyone,

Simplest mailcap entries like 'image /*; xv %s'
do not work with mutt-1.11.1 (even though they
will work with mutt-1.10.1)

There is a message like:

No matching mailcap entry found. Viewing as text.

on the status bar!

$HOME/.mailcap with entry is available as always.

Where should one look and what should be done?

Andreas

[Eef Hartman]

Post by a***@gmail.com
Simplest mailcap entries like 'image /*; xv %s'

Use no space between image and the /
I do not know if that is the problem, though, I'm still using 1.10.1
but my mailcap entry is:
image/*; xv %s
so the same as yours but without the space.

[a***@gmail.com]

Post by Eef Hartman

Post by a***@gmail.com
Simplest mailcap entries like 'image /*; xv %s'

Use no space between image and the /
I do not know if that is the problem, though, I'm still using 1.10.1
image/*; xv %s
so the same as yours but without the space.

That's not the cause. I installed 1.10.1 from a regular RPM package and rebuilt 1.11.1 from a source tarball!

It must have something to do with the code itself!!

Fortunately, I can still run both versions side by side because the old version is in /usr/bin and the latest version resides in $HOME/bin.

But I am always keen in running the latest and greatest! :-)

Andreas

[Eike Rathke]

Post by a***@gmail.com

Post by Eef Hartman

Post by a***@gmail.com
Simplest mailcap entries like 'image /*; xv %s'

Use no space between image and the /

That's not the cause.

However, a space within the MIME type *will* cause trouble *somewhere*.

Post by a***@gmail.com
I installed 1.10.1 from a regular RPM package and rebuilt 1.11.1 from a source tarball!

I'm building and running mutt master all the time, currently 1.11.1+27,
and never had a problem with viewing attachments with proper MIME types.

Eike

[a***@gmail.com]

Post by Eike Rathke

Post by a***@gmail.com

Post by Eef Hartman

Post by a***@gmail.com
Simplest mailcap entries like 'image /*; xv %s'

Use no space between image and the /

That's not the cause.

However, a space within the MIME type *will* cause trouble *somewhere*.

Post by a***@gmail.com
I installed 1.10.1 from a regular RPM package and rebuilt 1.11.1 from a source tarball!

I'm building and running mutt master all the time, currently 1.11.1+27,
and never had a problem with viewing attachments with proper MIME types.
Eike
--
OpenPGP/GnuPG encrypted mail preferred in all private communication.
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
Use LibreOffice! https://www.libreoffice.org/

Not to be misunderstood!

This it whast really shows and is in my .mailcap file:

$ cat .mailcap | grep xv
image/*; xv %s

So my first post on Google Groups (Usenet?) had a typo!!

So it *should* work even with Mutt master but it does not!

Somebody could correct me if I am wrong.

Andreas

[Eike Rathke]

Post by a***@gmail.com
$ cat .mailcap | grep xv
image/*; xv %s

Ok. Apart from that you should quote the file name and maybe even test
whether for xv the terminal actually has a graphical display. I'd also
give the full path to the xv executable. So like this:

image/*; /usr/bin/xv '%s'; test=test "$DISPLAY" != ""

The only difference in my case is I use eog instead of xv.

Post by a***@gmail.com
So my first post on Google Groups (Usenet?) had a typo!!

This is still Usenet, however you access it.

Post by a***@gmail.com
So it *should* work even with Mutt master but it does not!

It *does* work here.

Eike

[Jorgen Grahn]

Post by Eike Rathke

Post by a***@gmail.com
$ cat .mailcap | grep xv
image/*; xv %s

Ok. Apart from that you should quote the file name and maybe even test
whether for xv the terminal actually has a graphical display. I'd also
image/*; /usr/bin/xv '%s'; test=test "$DISPLAY" != ""
The only difference in my case is I use eog instead of xv.

Nice to see that someone besides me still uses xv, though!

For what it's worth, my .mailcap says:

image/gif; xv '%s'; test=test -n "$DISPLAY"
image/jpeg; xv '%s'; test=test -n "$DISPLAY"
image/png; xv '%s'; test=test -n "$DISPLAY"

However, the machine where I read mail doesn't have a $DISPLAY
these days.

/Jorgen

[downtime]

Post by a***@gmail.com

Post by Eef Hartman

Post by a***@gmail.com
Simplest mailcap entries like 'image /*; xv %s'

Use no space between image and the /
I do not know if that is the problem, though, I'm still using 1.10.1
image/*; xv %s
so the same as yours but without the space.

That's not the cause. I installed 1.10.1 from a regular RPM package and rebuilt 1.11.1 from a source tarball!
It must have something to do with the code itself!!
Fortunately, I can still run both versions side by side because the old version is in /usr/bin and the latest version resides in $HOME/bin.
But I am always keen in running the latest and greatest! :-)
Andreas

Are you sure that's not the cause? This works for me:

image/*; feh %s

[a***@gmail.com]

Post by a***@gmail.com
Hello everyone,
Simplest mailcap entries like 'image /*; xv %s'
do not work with mutt-1.11.1 (even though they
will work with mutt-1.10.1)
No matching mailcap entry found. Viewing as text.
on the status bar!
$HOME/.mailcap with entry is available as always.
Where should one look and what should be done?
Andreas
--
Your lucky number is 3552664958674928. Watch for it everywhere.

All this applies to mutt 1.11.1 (The "A Chorus Line" release):

Well, it's very strange, because if I open an old message that already contained a jpg attachment, I can open that attachment with an external call!

Which means that the mailcap entry is read and processed normally!

However, when I write a new message, it does *not* work for me (eg, postponed messages that I reopen, or simply just create a message and check by opening the attachment there).

In this case, I get the error message in the status bar.

Can someone tell me what it can be?

Thanks,
Andreas

[Eike Rathke]

Post by a***@gmail.com

Post by a***@gmail.com
No matching mailcap entry found. Viewing as text.

However, when I write a new message, it does *not* work for me (eg, postponed messages that I reopen, or simply just create a message and check by opening the attachment there).
In this case, I get the error message in the status bar.

Again, also that works for me (now at Mutt 1.11.1+32)

Post by a***@gmail.com
Can someone tell me what it can be?

As you said you built 1.11.1 from source, what --prefix=... directory do
you use (i.e. where is it installed to with make install) and how does
the default configuration differ (i.e. /etc/Muttrc vs
${PREFIX}/etc/Muttrc)?

If nothing helps and you know how to use gdb then build mutt with debug,
i.e. add the --debug option to ./prepare and run mutt in gdb, place
a breakpoint in attach.c on line 380 and step into the
rfc1524_mailcap_lookup() call and see where and why that fails.

Eike

[a***@gmail.com]

Post by Eike Rathke

Post by a***@gmail.com

Post by a***@gmail.com
No matching mailcap entry found. Viewing as text.

However, when I write a new message, it does *not* work for me (eg, postponed messages that I reopen, or simply just create a message and check by opening the attachment there).
In this case, I get the error message in the status bar.

Again, also that works for me (now at Mutt 1.11.1+32)

Post by a***@gmail.com
Can someone tell me what it can be?

As you said you built 1.11.1 from source, what --prefix=... directory do
you use (i.e. where is it installed to with make install) and how does
the default configuration differ (i.e. /etc/Muttrc vs
${PREFIX}/etc/Muttrc)?

Just did actually install the binary into the default path and it works!

Well, I recently used the binary and just made a copy of it
to the bin directory of my home directory. That's why it failed.

Post by Eike Rathke
If nothing helps and you know how to use gdb then build mutt with debug,
i.e. add the --debug option to ./prepare and run mutt in gdb, place
a breakpoint in attach.c on line 380 and step into the
rfc1524_mailcap_lookup() call and see where and why that fails.

Won't bother now. Not on a stripped binary at all! ;-)

What's more, since I use smime. Where are all the the rc samples?
They are missing now!

They are normally installed via the rpm package 'mutt-doc'.

Thanks,
Andreas

[Eike Rathke]

Post by a***@gmail.com

Post by Eike Rathke
As you said you built 1.11.1 from source, what --prefix=... directory do
you use (i.e. where is it installed to with make install) and how does
the default configuration differ (i.e. /etc/Muttrc vs
${PREFIX}/etc/Muttrc)?

Just did actually install the binary into the default path and it works!

If you previously used your system's package manager to install the .rpm
then by overwriting things with the new version you grinded the system
packager's checksum handling useless and it will/should refuse
installing any new version from the distribution.

Post by a***@gmail.com
Well, I recently used the binary and just made a copy of it
to the bin directory of my home directory. That's why it failed.

I rather prefer to have the installation target in a completely
different directory that I also specify with --prefix=... and make
install and then use an override-bin/mutt script that sits in the PATH
to execute the individually compiled version.

Post by a***@gmail.com

Post by Eike Rathke
If nothing helps and you know how to use gdb then build mutt with debug,
i.e. add the --debug option to ./prepare and run mutt in gdb, place
a breakpoint in attach.c on line 380 and step into the
rfc1524_mailcap_lookup() call and see where and why that fails.

Won't bother now. Not on a stripped binary at all! ;-)
What's more, since I use smime. Where are all the the rc samples?
They are missing now!

They are in the mutt source's ./contrib/ directory.

Post by a***@gmail.com
They are normally installed via the rpm package 'mutt-doc'.

Again, I recommend to not mess up the rpm installation with the
self-compiled version. If with a different --prefix=... you still want
to pull in the system's default /etc/Muttrc or files from the new mutt
version then rather source them explicitly.

Eike

[Jorgen Grahn]

On Thu, 2018-12-13, Eike Rathke wrote:
...

Post by Eike Rathke
If nothing helps and you know how to use gdb then build mutt with debug,
i.e. add the --debug option to ./prepare and run mutt in gdb, place
a breakpoint in attach.c on line 380 and step into the
rfc1524_mailcap_lookup() call and see where and why that fails.

Another often helpful thing is to run 'strace -o strace.log mutt'.
You can verify what mailcap file(s) it's trying to read.

/Jorgen