From: Yakov ZAYTSEV <iakovz@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: TRAMP on Windows and CVS issue
Date: Wed, 20 Feb 2008 05:03:17 -0800 (PST) [thread overview]
Message-ID: <7946c337-51a3-4c13-a9d4-b8fef73afe46@t66g2000hsf.googlegroups.com> (raw)
In-Reply-To: 304a9269-4d5c-4d09-8e1b-0621cc6eea8b@p43g2000hsc.googlegroups.com
Issue has been solved. I've implemented another version of vc-cvs-
command using complete path to cvs binary.. Personally, I wonder why
it's impossible to customize cvs executable..
On Feb 20, 12:48 am, Yakov ZAYTSEV <iak...@gmail.com> wrote:
> Hello,
>
> I'm using TRAMP 2.1.12-pre with NTEMACS 22.1.50.1 (i386-mingw-
> nt5.1.2600)
>
> I can't do Show History on a TRAMP accessed file. I added path to CVS
> binary to tramp-remote-path variable, but unfortunately I see ``sh:
> cvs: command not found'' in *vc-change-log* buffer after an attempt to
> Show History on a file..
>
> Could you please help me?
>
> PS
> I'm using plink to access my remote machine and I have whole bunch of
> PuTTY tools in my local (windows) path
>
> Thanks in advance!
prev parent reply other threads:[~2008-02-20 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 8:48 TRAMP on Windows and CVS issue Yakov ZAYTSEV
2008-02-20 13:03 ` Yakov ZAYTSEV [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=7946c337-51a3-4c13-a9d4-b8fef73afe46@t66g2000hsf.googlegroups.com \
--to=iakovz@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).