From: Glenn Morris <rgm@gnu.org>
To: Art Werschulz <agw@dsm.fordham.edu>
Cc: 34017@debbugs.gnu.org
Subject: bug#34017: 26.1; emacs-w3m no longer works
Date: Tue, 08 Jan 2019 12:46:56 -0500 [thread overview]
Message-ID: <jy1s5nxcrz.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <2mo98ri0ah.fsf@sobolev.dsm.fordham.edu> (Art Werschulz's message of "Tue, 08 Jan 2019 11:25:42 -0500")
VM is not part of GNU Emacs or ELPA.
W3 is in GNU ELPA, but AFAICS is broken and unmaintained for years, ref
https://debbugs.gnu.org/25395#24
I would suggest you report this to the upstreams of these projects in
the first instance, and followup here if it turns out to be a core Emacs
issue.
next prev parent reply other threads:[~2019-01-08 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 16:25 bug#34017: 26.1; emacs-w3m no longer works Art Werschulz
2019-01-08 17:46 ` Glenn Morris [this message]
2019-01-08 17:48 ` Glenn Morris
2019-01-09 15:27 ` Filipp Gunbin
2019-08-21 15:45 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jy1s5nxcrz.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=34017@debbugs.gnu.org \
--cc=agw@dsm.fordham.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).