Simplest mailcap entries like 'image /*; xv %s'
amitsis@gmail.com wrote:
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.
Am Samstag, 8. Dezember 2018 18:40:55 UTC+1 schrieb Eef Hartman:
amitsis@gmail.com wrote:
Simplest mailcap entries like 'image /*; xv %s'
Use no space between image and the /
That's not the cause.
I installed 1.10.1 from a regular RPM package and rebuilt 1.11.1 from a source tarball!
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!
* amitsis@gmail.com, 2018-12-08 18:47 UTC:
Am Samstag, 8. Dezember 2018 18:40:55 UTC+1 schrieb Eef Hartman:
amitsis@gmail.com wrote:
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*.
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/
* amitsis@gmail.com, 2018-12-08 22:20 UTC:
This it whast really shows and is in my .mailcap file:
$ 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.
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
--
Your lucky number is 3552664958674928. Watch for it everywhere.
Am Samstag, 8. Dezember 2018 18:17:12 UTC+1 schrieb ami...@gmail.com:
No matching mailcap entry found. Viewing as text.All this applies to mutt 1.11.1 (The "A Chorus Line" release):
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?
* amitsis@gmail.com, 2018-12-11 15:14 UTC:
Am Samstag, 8. Dezember 2018 18:17:12 UTC+1 schrieb ami...@gmail.com:
No matching mailcap entry found. Viewing as text.All this applies to mutt 1.11.1 (The "A Chorus Line" release):
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)
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.
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.
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.
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'.
Am Samstag, 8. Dezember 2018 18:40:55 UTC+1 schrieb Eef Hartman:
amitsis@gmail.com wrote:
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.
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
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 44:55:06 |
| Calls: | 6,648 |
| Files: | 12,197 |
| Messages: | 5,329,767 |