unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Shuguang Sun <shuguang@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: tramp and shell, problem on windows 7
Date: Sun, 5 Nov 2017 11:08:28 +0800	[thread overview]
Message-ID: <CACspjXeGaVRqv80QQXNjSjxdRw488zWno1+6pgoz=qMjUk8Jpw@mail.gmail.com> (raw)
In-Reply-To: <87lgjmgny3.fsf@gmx.de>

It works for command shell, but not for dired-do-shell-command, to set
explicit-shell-file-name to "/bin/sh". It confirms the
explicit-shell-file-name and shell-name are used in tramp dired.

On Sat, Nov 4, 2017 at 9:42 PM, Michael Albinus <michael.albinus@gmx.de>
wrote:

> Shuguang Sun <shuguang@gmail.com> writes:
>
> > Hi all,
>
> Hi,
>
> > Windows7,
> > GNU Emacs 27.0.50 (build 1, x86_64-w64-mingw32) of 2017-10-21
>
> I don't use Windows myself, so I can guess only.
>
> > - Problem 1: tramp and dired-do-shell-command:  start: Unknown job: /b
> > Why "start /b" is called remote side?
>
> Internally, `shell-command' will be called. This uses `shell-file-name'
> and `shell-command-switch'. I suppose, both variables are set to "start"
> and "/b", respectively, in your environment.
>
> > When I run tramp (plink) and go to a remote buffer (dired mode), run
> > dired-do-shell-command (!) on marked file (for example, R CMD BATCH * &).
> > It popup the buffer of * Async Shell Command *, and the command is not
> run
> > but a message "start: Unknown job: /b" which looks it runs the
> windows-like
> > command "start /b ..." on the remote shell.
>
> You will be served better if you set `explicit-shell-file-name' to a
> proper value, for example "/bin/sh". See the discussion in the Emacs
> manual, node "Interactive Subshell".
>
> > - Problem 2: tramp and shell: env: c:/bin/ : No such file or directory
> > where "c:/" comes?
> >
> > In a tramp dried buffer, call shell which suppose to raise the shell
> buffer
> > on remote server. However, I got error messge in the * shell * buffer
> that
> > "env: c:/bin/ : No such file or directory". I don't know where the "c:/"
> > comes from. When shell is called, it reads the remote path in the
> minibufer
> > with promotes
> > "/plink:user@host:/path/to/dired/C:/Users/username/emacs/
> libexec/emacs/27.0.50/x86_64-w64-mingw32/cmdproxy.exe",
> > and I change it to "/plink:user@host:/bin/", and then I got error
> message
> > above. Below is the tracking:
>
> This I cannot answer (yet). Try the setting above, and let's see what's
> happening.
>
> > Best Regards,
> > Shuguang Sun
>
> Best regards, Michael.
>


      parent reply	other threads:[~2017-11-05  3:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04  8:42 tramp and shell, problem on windows 7 Shuguang Sun
2017-11-04 13:42 ` Michael Albinus
2017-11-04 14:40   ` Eli Zaretskii
2017-11-04 15:25     ` Michael Albinus
2017-11-04 15:48       ` Eli Zaretskii
2017-11-04 15:46     ` Why are bugs discussed on this list? [was: tramp and shell ...] tomas
2017-11-04 16:13       ` Eli Zaretskii
2017-11-04 16:19         ` tomas
2017-11-05  3:08   ` Shuguang Sun [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACspjXeGaVRqv80QQXNjSjxdRw488zWno1+6pgoz=qMjUk8Jpw@mail.gmail.com' \
    --to=shuguang@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael.albinus@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).