switch buffer variable context after (push-button)?

switch buffer variable context after (push-button)?

[Christopher Howard]

Hi, I'm trying to automate some various procedures I do — private tasks, not of general interest. One was to navigate to a button in a buffer, and then run (push-button) which opens a link to a Web page in EWW. (The button target may vary.) After that, I wanted to run (eww-readable), but it gives me an error. After some debugging, I figured out the eww-readable was trying to use the value of the eww-data variable from the previous buffer — which is nil — rather than the value of it in the EWW buffer.

Is there a function that I have to call first, so that my elisp function sees the variable values from the second buffer instead of the original one?

-- 
📛 Christopher Howard
🚀 gemini://gem.librehacker.com
🌐 http://gem.librehacker.com

בראשית ברא אלהים את השמים ואת הארץ

Re: switch buffer variable context after (push-button)?

[Joel Reicher]

Christopher Howard <christopher@librehacker.com> writes:

> Hi, I'm trying to automate some various procedures I do ― 
> private tasks, not of general interest. One was to navigate to a 
> button in a buffer, and then run (push-button) which opens a 
> link to a Web page in EWW. (The button target may vary.) After 
> that, I wanted to run (eww-readable), but it gives me an 
> error. After some debugging, I figured out the eww-readable was 
> trying to use the value of the eww-data variable from the 
> previous buffer ― which is nil ― rather than the value of it in 
> the EWW buffer.
>
> Is there a function that I have to call first, so that my elisp 
> function sees the variable values from the second buffer instead 
> of the original one?

You can use `with-current-buffer' to do it scoped/statelessly, or 
`set-buffer' to do it statefully.

Regards,

        - Joel