Re: EmacsClient: using both --eval and --alternate-editor, possible?

Re: EmacsClient: using both --eval and --alternate-editor, possible?

[Pascal J. Bourguignon]

Elena <egarrulo@gmail.com> writes:

> Hello,
>
> I think there is a conflict between --eval and --alternate-editor
> option in EmacsClient.  If Emacs is not running and thus --eval fails,
> the EDITOR indicated with --alternate-editor is called instead.
> However, such EDITOR gets an ELisp expression, which it can't handle.
> Is there a way around this, other than wrapping EmacsClient into a
> script?

Obviously, you need to patch this other editor to make it understand
elisp.  This is indeed an awful but that need immediate action.  Either
you integrate elisp in that alternate editor, or you rm it.  

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

Re: EmacsClient: using both --eval and --alternate-editor, possible?

[Richard Riley]

pjb@informatimago.com (Pascal J. Bourguignon) writes:

> Elena <egarrulo@gmail.com> writes:
>
>> Hello,
>>
>> I think there is a conflict between --eval and --alternate-editor
>> option in EmacsClient.  If Emacs is not running and thus --eval fails,
>> the EDITOR indicated with --alternate-editor is called instead.
>> However, such EDITOR gets an ELisp expression, which it can't handle.
>> Is there a way around this, other than wrapping EmacsClient into a
>> script?
>
> Obviously, you need to patch this other editor to make it understand
> elisp.  This is indeed an awful but that need immediate action.  Either
> you integrate elisp in that alternate editor, or you rm it.  

Or alternatively, and much more useful and helpful, if emacs uses the
alternative editor then it doesnt pass the eval statement to that other
editor since it knows the elisp eval statement is useless..

Re: EmacsClient: using both --eval and --alternate-editor, possible?

[Pascal J. Bourguignon]

Richard Riley <rileyrg@googlemail.com> writes:

> pjb@informatimago.com (Pascal J. Bourguignon) writes:
>
>> Elena <egarrulo@gmail.com> writes:
>>
>>> Hello,
>>>
>>> I think there is a conflict between --eval and --alternate-editor
>>> option in EmacsClient.  If Emacs is not running and thus --eval fails,
>>> the EDITOR indicated with --alternate-editor is called instead.
>>> However, such EDITOR gets an ELisp expression, which it can't handle.
>>> Is there a way around this, other than wrapping EmacsClient into a
>>> script?
>>
>> Obviously, you need to patch this other editor to make it understand
>> elisp.  This is indeed an awful but that need immediate action.  Either
>> you integrate elisp in that alternate editor, or you rm it.  
>
> Or alternatively, and much more useful and helpful, if emacs uses the
> alternative editor then it doesnt pass the eval statement to that other
> editor since it knows the elisp eval statement is useless..

This is silly.  Obviously, the alternate editor is also an emacs.

For example:

/opt/local/bin/emacsclient --alternate-editor=/usr/bin/emacs -e '(emacs-version)'

if for some reason the X11 emacs provided by MacPorts is not available,
I fallback to the bare terminal emacs provided by Apple.


-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

Re: EmacsClient: using both --eval and --alternate-editor, possible?

[Elena]

While looking for ways to cut out the Elisp code and passing just the
file-name, I found out that you can customize `server-*' functions and
variables, thus achieving the goal of moving the Elisp code from
EmacsClient's command line to Emacs itself.

Once again, Emacs had it sorted out already ^_^