eval-last-sexp in other window

eval-last-sexp in other window

[Bob Babcock]

Is there a way to have eval-last-sexp (typically bound to C-xC-e) run in a 
different window?  This would be convenient when developing a macro that 
reformats text - I want the part of the macro I'm testing to be applied to 
the file being reformatted, not to my macro.

Re: eval-last-sexp in other window

[Pascal J. Bourguignon]

Bob Babcock <wssddc@nospam.gis.net> writes:

> Is there a way to have eval-last-sexp (typically bound to C-xC-e) run in a 
> different window?  This would be convenient when developing a macro that 
> reformats text - I want the part of the macro I'm testing to be applied to 
> the file being reformatted, not to my macro.

You may use M-:  to apply a form to the current buffer. 


Otherwise:

(with-current-buffer (get-buffer "The Other Buffer Name")
   (do-what-you-want)) C-x C-e

-- 
__Pascal Bourguignon__

Re: eval-last-sexp in other window

[Bob Babcock]

pjb@informatimago.com (Pascal J. Bourguignon) wrote in
news:87d4bzbfky.fsf@galatea.local: 

>> Is there a way to have eval-last-sexp (typically bound to C-xC-e) run
>> in a different window?  This would be convenient when developing a
>> macro that reformats text - I want the part of the macro I'm testing
>> to be applied to the file being reformatted, not to my macro.
> 
> You may use M-:  to apply a form to the current buffer. 
> 
> 
> Otherwise:
> 
> (with-current-buffer (get-buffer "The Other Buffer Name")
>    (do-what-you-want)) C-x C-e

Thanks.  After several false starts, I have a simple macro that seems to do 
what I want:

(defun last-sexp-other-window()
"Get last sexp and run it in other window.
If there isn't another window, use current window."
  (interactive)
  (setq ow-sexp (preceding-sexp))
  (other-window 1) (eval ow-sexp) (other-window -1) )

This doesn't call the debugger on error, but that's ok.

Re: eval-last-sexp in other window

[Pascal J. Bourguignon]

Bob Babcock <wssddc@nospam.gis.net> writes:

> pjb@informatimago.com (Pascal J. Bourguignon) wrote in
> news:87d4bzbfky.fsf@galatea.local: 
>
>>> Is there a way to have eval-last-sexp (typically bound to C-xC-e) run
>>> in a different window?  This would be convenient when developing a
>>> macro that reformats text - I want the part of the macro I'm testing
>>> to be applied to the file being reformatted, not to my macro.
>> 
>> You may use M-:  to apply a form to the current buffer. 
>> 
>> 
>> Otherwise:
>> 
>> (with-current-buffer (get-buffer "The Other Buffer Name")
>>    (do-what-you-want)) C-x C-e
>
> Thanks.  After several false starts, I have a simple macro that seems to do 
> what I want:
>
> (defun last-sexp-other-window()
> "Get last sexp and run it in other window.
> If there isn't another window, use current window."
>   (interactive)
>   (setq ow-sexp (preceding-sexp))
>   (other-window 1) (eval ow-sexp) (other-window -1) )

At the very least, use let, not setq!

(defun last-sexp-other-window()
 "Get last sexp and run it in other window.
If there isn't another window, use current window."
   (interactive)
   (let ((ow-sexp (preceding-sexp)))
      (other-window 1)
      (eval ow-sexp)
      (other-window -1)))

-- 
__Pascal Bourguignon__

Re: eval-last-sexp in other window

[Bob Babcock]

pjb@informatimago.com (Pascal J. Bourguignon) wrote in
news:87bpri9lhd.fsf@galatea.local: 

>> (defun last-sexp-other-window()
>> "Get last sexp and run it in other window.
>> If there isn't another window, use current window."
>>   (interactive)
>>   (setq ow-sexp (preceding-sexp))
>>   (other-window 1) (eval ow-sexp) (other-window -1) )
> 
> At the very least, use let, not setq!
> 
> (defun last-sexp-other-window()
>  "Get last sexp and run it in other window.
> If there isn't another window, use current window."
>    (interactive)
>    (let ((ow-sexp (preceding-sexp)))
>       (other-window 1)
>       (eval ow-sexp)
>       (other-window -1)))

I will admit that I was surprised when setq worked in this context.
Perhaps there are cases where setq would fail?

Re: eval-last-sexp in other window

[Pascal J. Bourguignon]

Bob Babcock <wssddc@nospam.gis.net> writes:

> pjb@informatimago.com (Pascal J. Bourguignon) wrote in
> news:87bpri9lhd.fsf@galatea.local: 
>
>>> (defun last-sexp-other-window()
>>> "Get last sexp and run it in other window.
>>> If there isn't another window, use current window."
>>>   (interactive)
>>>   (setq ow-sexp (preceding-sexp))
>>>   (other-window 1) (eval ow-sexp) (other-window -1) )
>> 
>> At the very least, use let, not setq!
>> 
>> (defun last-sexp-other-window()
>>  "Get last sexp and run it in other window.
>> If there isn't another window, use current window."
>>    (interactive)
>>    (let ((ow-sexp (preceding-sexp)))
>>       (other-window 1)
>>       (eval ow-sexp)
>>       (other-window -1)))
>
> I will admit that I was surprised when setq worked in this context.
> Perhaps there are cases where setq would fail?

For example in this case:

(defun evaluate-sexps-in-other-windows ()
  (let ((ow-sexp 0)) ; count the sexps we evaluate.
     (while (< (point) (max-point))
        (incf ow-sexp)
        (forward-sexp)
        (last-sexp-other-window))
    ow-sexp))


Remember that in emacs lisp, all the bindings are special (dynamic).
When you use setq on a variable for which you don't provide a local
binding, you are actually destroying the binding of the caller (or the
caller of the caller...), therefore introducing bugs in unrelated code.

In some occasions it might be easier to use setq/setf, but do it only
on a locally rebound variable:

  (let ((var init-value))
     (setf var (f1 var))
     (loop 
        while (condp var)
        do (setf var (f2 var)))
     (setf var (f3 var))
     var)


[ which, in the case of loop can also be rewritten as:

    (loop
       with var = init-value
       initially (setf var (f1 var))
       while (condp var)
       do (setf var (f2 var))
       finally (return (f3 var)))
].



But it may be clearer to write it as:

  (f3 (fix (function f2) (function condp) (f1 init-value)))


with:

(defun fix (fun predicate value)
  (if (funcall predicate value)
     (fix fun predicate (funcall fun value))
     value))


-- 
__Pascal Bourguignon__

Re: eval-last-sexp in other window

[Xavier Maillard]

   pjb@informatimago.com (Pascal J. Bourguignon) wrote in
   news:87d4bzbfky.fsf@galatea.local: 

   >> Is there a way to have eval-last-sexp (typically bound to C-xC-e) run
   >> in a different window?  This would be convenient when developing a
   >> macro that reformats text - I want the part of the macro I'm testing
   >> to be applied to the file being reformatted, not to my macro.
   > 
   > You may use M-:  to apply a form to the current buffer. 
   > 
   > 
   > Otherwise:
   > 
   > (with-current-buffer (get-buffer "The Other Buffer Name")
   >    (do-what-you-want)) C-x C-e

   Thanks.  After several false starts, I have a simple macro that seems to do 
   what I want:

   (defun last-sexp-other-window()
   "Get last sexp and run it in other window.
   If there isn't another window, use current window."
     (interactive)
     (setq ow-sexp (preceding-sexp))
     (other-window 1) (eval ow-sexp) (other-window -1) )

Why not use let instead of setq ?

	Xavier
-- 
http://www.gnu.org
http://www.april.org
http://www.lolica.org

Re: eval-last-sexp in other window

[Pascal J. Bourguignon]

Xavier Maillard <xma@gnu.org> writes:

>    pjb@informatimago.com (Pascal J. Bourguignon) wrote in
>    news:87d4bzbfky.fsf@galatea.local: 
>
>    >> Is there a way to have eval-last-sexp (typically bound to C-xC-e) run
>    >> in a different window?  This would be convenient when developing a
>    >> macro that reformats text - I want the part of the macro I'm testing
>    >> to be applied to the file being reformatted, not to my macro.
>    > 
>    > You may use M-:  to apply a form to the current buffer. 
>    > 
>    > 
>    > Otherwise:
>    > 
>    > (with-current-buffer (get-buffer "The Other Buffer Name")
>    >    (do-what-you-want)) C-x C-e
>
>    Thanks.  After several false starts, I have a simple macro that seems to do 
>    what I want:
>
>    (defun last-sexp-other-window()
>    "Get last sexp and run it in other window.
>    If there isn't another window, use current window."
>      (interactive)
>      (setq ow-sexp (preceding-sexp))
>      (other-window 1) (eval ow-sexp) (other-window -1) )
>
> Why not use let instead of setq ?

À mon avis, c'est par pure méchanceté.

-- 
__Pascal Bourguignon__