Emacs-w3m launches an external w3m executable. On Linux, that gives a convenient place to apply a SOCKS route to this browser alone.

For an existing Proxychains-NG and dynamically linked w3m setup, an executable wrapper might contain:

#!/bin/sh
exec proxychains4 -f "$HOME/.config/proxychains/w3m.conf" /usr/bin/w3m "$@"

Use the actual w3m path and provide the named Proxychains configuration. A one-proxy example has this shape:

strict_chain
proxy_dns
[ProxyList]
socks5 127.0.0.1 1080

The example assumes a SOCKS5 listener already exists on that local port. Make the wrapper executable and select it before loading emacs-w3m:

(setq w3m-command
      (expand-file-name "~/.local/bin/w3m-via-proxy"))

Restart Emacs after changing the command when following the manual’s initialization model. Quoted "$@" preserves the argument boundaries supplied by emacs-w3m, and exec leaves the launched process as the wrapped browser.

This route concerns the external process’s hookable TCP connections. It does not change EWW, the URL library or unrelated Emacs package downloads. A w3m binary that cannot load the Proxychains library needs another supported routing method.

Аффингæй хæстæг статьялтæ