On 22 September 2014 16:55, MM <[email protected]> wrote:

> On 19 September 2014 10:36, Michael Albinus <[email protected]>
> wrote:
> > MM <[email protected]> writes:
> >
> >> Also, with M-x compile, i actually need to do remotely:    "cd <dir>
> >> && ./build.sh"
> >> So change to some dir and start a script that will launch the compiler.
> >>
> >> But then cd is interpreted as local cd, not remote cd.
> >
> > How do you call "cd"? From the minibuffer? Then you would need to give
> > the whole Tramp name. From a *shell* buffer? Then it should work. From
> > an *eshell* buffer? Then you would need the Tramp name as well.
> >
> > In order to avoid this struggle, it is recommend to use relative file
> > names. Something like "cd ../../src".
>
> I have tried:
> M-x compile
> In minibuffer:  cd /plink:..:<pathToGoTo>  && ./build.sh
> It failed because the sh shell actually tried to find the /plink directory
>
> Then I tried
> M-x compile
> cd <pathToGoTo> && ./build.sh
>
> Then it failed with:
> No such dir found via CDPATH env variable (I assume this is my local
> windows box)
>
> MM
>

Hello,

My usage is now well established after a few weeks. I waited for your
return to continue with further questions:-)

I need to type my password every time I issue a new command like compile or
grep.
Is there a way to cache it?

reminder: I have the win version emacs 24.3 32bit. Tramp logs in through a
gateway, with a subprocess plink.

MM,
_______________________________________________
Tramp-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/tramp-devel

Reply via email to