help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

## Re: Problem quoting expression to be eval'ed by emacsclient

 From: Eli Zaretskii Subject: Re: Problem quoting expression to be eval'ed by emacsclient Date: Wed, 30 Oct 2013 20:55:10 +0200

```> From: "Sebastien Vauban" <address@hidden>
> Date: Wed, 30 Oct 2013 10:59:24 +0100
>
> So, here, in my case, I almost only use `emacsclient' from "sendpatch", a
> shell
> script (I wrote) which automates the sending of a diff per email, for other
> colleagues to review and see what we commit in our SVN server.

So you are using emacsclient as EDITOR, which is what it is for.

> >> - Cygwin (/usr/bin) is second in my PATH, after ~/bin
> >
> > Why do you need Cygwin executables on your PATH?
>
> You mean from PATH as seen in a CMD shell?  Or from a Bash shell?

Both, and also why you need that in Emacs.

> I need the Cygwin executables them all the time in my Bash sessions.

You can set up your Bash sessions so that when you are in Bash,
Cygwin's bin directory is on PATH, but when you are in cmd or Emacs,
it is not.  There's no necessity to have a single PATH in all your
sessions.

> And I need the Cygwin executables from Emacs as well (for the `M-x
> find-grep-dired' or `M-x rgrep' commands, among others, which I use quite
> extensively -- `rgrep', at least). And, there, I need them to be before the
> default Windows executable, because of `find' (which also exist in
> c:\Windows\system32).

To avoid the problem with 'find', have the directory where the GNU
'find' lives appear before c:\Windows\system32 in PATH.  After all,
chances of you wanting to invoke the Windows 'find' are nil, right?

As for grep, there's a native Windows port around, so no need to go
Cygwin when you use Emacs.

> > As for the v23 vs v24 emacsclient issue, you could have emacsclient23
> > and emacsclient24 (scripts, aliases, whatever) to DTRT for each one.
>
> Yes, but the question arises from the fact that `sendpatch' has no way to
> detect (does it?) which Emacs server version is currently running, so which
> `emacsclient' it has to call.

I presume that you already have some arrangements to work with 2 Emacs
versions, so that it should be easy to put something in the
environment in each case, such that 'sendpatch' could look at that and
decide.

```

reply via email to

 [Prev in Thread] Current Thread [Next in Thread]