Several instances were found of string operations being performed on
w3m-current-url without checking if the variable was a string.
When an external program calls emacs/emacs-w3m to open a URI that is
an image, and emacs-w3m is configured to view that filetype
externally, it still creates a new emac-w3m buffer.
This patch deletes the created buffer; however, wouldn't it be
better never to create it in the first place?
That might not be possible because the way asynchronous processes
need to be associated with a buffer, but even so the current
situation needlessly makesthe new buffer a copy of the most recent
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.