Re: Patch for bug in w3m-generate-new-buffer

[Boruch Baum <boruch_baum@xxxxxxx>]

On 2018-02-08 02:51, Vladimir Sedach wrote:
> Hello,
>
> There was a serious bug introduced on 2017-10-13 to
> w3m-generate-new-buffer: new buffers would always get number 1, there
> would be duplicate buffers with number 1. You can verify this by opening
> a new w3m buffer (via w3m-search-new-session, for example) when multiple
> w3m buffers are already open, and trying to use w3m-previous-buffer.
>
> This bug also masked a problem with the new LAST parameter to
> w3m-copy-buffer in w3m-view-this-url-1.
>
> A patch is attached.
>
> Thank you,
> Vladimir

Hi Vladimir,

Just browsing the patch, and when I saw `w3m-fb-mode', I decided to look
it up, because I wasn't aware of it. The documentation includes a
warning, "Setting this variable directly does not take effect; either
customize it (see the info node ‘Easy Customization’) or call the
function ‘w3m-fb-mode’."

So, is the documentation wrong?



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