>>>>> Ted Zlatanov writes: >>>>> On Sat, 21 Dec 2013 21:51:49 +0000 Ivan Shmakov wrote: >>>>> "TZ" == Ted Zlatanov writes: […] TZ> I don't see a need for complicated variable passing as you TZ> described and I omitted, but have no strong opinion about it TZ> either. IS> Please note that eww-setup-buffer is called from the buffer filled IS> by url-retrieve, and /not/ from one of the EWW buffers. I see no IS> obvious way for it to deduce from which buffer the original command IS> (say, M-x eww) was called so to get back there. TZ> Right, OK. I will let you and Lars figure it out, but if you can TZ> propose a patch to accomplish what you describe, it will probably TZ> speed things up. Well, I’ve tried to contact assign at gnu dot org and copyright-clerk at fsf dot org once again some weeks ago, and got no reply again. I wonder if it has anything to do with the way my MXes work (though I clearly see the message being accepted by one of the FSF/GNU ones in the logs), or that I’ve requested a copyright /disclaimer/ (for I believe that these of my changes are non-copyrightable per se anyway.) Nevertheless, the patch that I use for quite some time is MIMEd. And just in case the changes I suggest /are/ copyrightable, here’s the license for them: To the extent possible under law, the author(s) have dedicated all copyright and related and neighboring rights to this software to the public domain worldwide. This software is distributed without any warranty. You should have received a copy of the CC0 Public Domain Dedication along with this software. If not, see . Note though that there’re a few changes not strictly necessary. For instance, eww-setup-buffer now uses set-buffer instead of switch-to-buffer, so that it’s possible to start eww-reload in several EWW buffers in a row, without being switched from one to another at some random point. Also, there’s a new eww-buffer-name variable. -- FSF associate member #7257 http://boycottsystemd.org/