[emacs-w3m:13847] Re: Support MIME type application/emacs-lisp

I can't reproduce this bug, but I'm using (kind-of) the current (ie.
latest) commit, not the debian version from February. With the current
version, the page (and others similar) do *not* perform a download
operation for me, and *do* successfully display the elisp content in a
w3m browser buffer.

On 2021-09-16 12:35, [email protected] wrote:
>    I've found a small bug. When I went to a website with an emacs lisp
>    file, I got a strange message from emacs-w3m (version
>    1.4.632+0.20210201.2305.54c3ccd-1):
>    > Reading
>    [1]https://jblevins.org/projects/markdown-mode/markdown-mode.el ...
>    >
>    >    =E2=80=98C-c C-k=E2=80=99 to abort this operation, or
>    >    =E2=80=98S=E2=80=99 to perform a search in a new buffer, or
>    >    =E2=80=98G=E2=80=99 to visit a URL in a new buffer, or
>    >    do any emacs work in any other buffer, or just wait ...
>    The message was confusing. It said emacs-w3m is busy "reading".
>    However, the minibuffer said "Download" and showed a filename in the
>    ~/.w3m directory.

Can you perform the following? 1) Delete the emacs *Messages* buffer; 2)
Perform the emacs-w3m operation again; 3) Send us a copy of the contents
of the new emacs *Messages* buffer.

>    I did not wish to download the Emacs lisp file. I only wanted to
>    view it. When I hit C-g to cancel the download, the w3m buffer did
>    not change. I had to use C-c C-k to abort the operation.

That's what the message said to do.

>    In an older version of emacs-w3m (1.4.632+0.20181112-9), the
>    message was easier to understand:
>    >  This display does not support application/emacs-lisp:
>    > <[2]https://jblevins.org/projects/markdown-mode/markdown-mode.el>
>    That was better. It explains why emacs-w3m is attempting to download
>    the file. But, it still doesn't let me view the file.

The old message is (at least now) inaccurate. Emacs-w3m *does* support
the content, and does not (for me at least) attempt to perform a download.

>    Would you please make a change to improve emacs-w3m? When trying to
>    load a file of unsupported MIME type, please have emacs-w3m ask what =
to
>    do:

I think we already do that. I remember coding a version of that in a PR
of mine a few years ago, I think.

>    I apologize if this is an old bug. The two versions of emacs-w3m I us=
ed
>    are the ones that come bundled with the current stable version of
>    Debian GNU/Linux.

Hypothetically, let's say the issue is a bug, and we 'fix' it
immediately. If you are constrained to using only the Debian packages it
could take months before you see the fix. In the meantime, anyone
getting the package from MELPA would see the update immediately. What
I'm getting at is that if it's possible for you to install the package
from MELPA, you would benefit from the having the latest release,
probably would not have the issue in the first place, and if it did
exist, would see the fix immediately when pushed.

=2D-
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0