unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: Patch: new function process-file (call-process with file handlers)
Date: Sun, 24 Oct 2004 22:06:54 +0200	[thread overview]
Message-ID: <86r7nnyj6p.fsf@ketchup.de.uu.net> (raw)
In-Reply-To: 200410241829.i9OITPZ25928@raven.dms.auburn.edu

Luc Teirlinck <teirllm@dms.auburn.edu> writes:

> I am using VC.
>
> If I do `C-x v v C-c C-c" I get:
>
> vc-do-command: Running cvs...FAILED (nil)
>
> My changes got committed OK to Savannah CVS, but the version number in
> the mode line got not updated.  Before your recent changes, it got
> updated.

Duh.  I apologize.  I confess, though, that I don't know what's
wrong.  I never used CVS with Tramp.  I just tried to open an
RCS-controlled file /sudo:root@localhost:/tmp/foo, and with this file,
C-x v = and C-x v v seemed to work in some fashion, though I also see
the error message "RCS/foo,v: no such file or directory".

Hm.  Now I also tested with a "local" CVS repository as follows:

    ssh testuser@localhost
    cvs -d $HOME/cvsrepo init
    mkdir $HOME/cvstest
    cd $HOME/cvstest
    echo bla > foo
    cvs add foo
    cvs ci -m'' foo

Then, I used Emacs to edit the file foo:

    C-x C-f /ssh:testuser@localhost:/home/testuser/cvstest/foo RET

Then, I made some changes, saved them, invoked C-x v =.  That
complained a bit ("no such file or directory" for foo.~1.1.~ and foo)
but did produce a diff.

Then, I committed the changes, and that also produced an error message
but did commit.

But this was the first time for me to use CVS via Tramp, so I can't
say whether what I saw was normal.

Can you show me how to reproduce the problem?

Kai

  reply	other threads:[~2004-10-24 20:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-17 15:53 Patch: new function process-file (call-process with file handlers) Kai Grossjohann
2004-10-17 16:57 ` David Kastrup
2004-10-17 16:58 ` Stefan Monnier
2004-10-18  8:28   ` Kim F. Storm
2004-10-18 10:24     ` David Kastrup
2004-10-24 13:27       ` Kai Grossjohann
2004-10-17 19:19 ` Kai Grossjohann
2004-10-17 20:48   ` Stefan Monnier
2004-10-18  6:44     ` Kai Grossjohann
2004-10-18 13:59     ` Richard Stallman
2004-10-19  6:37       ` Michael Albinus
2004-10-23 20:03       ` Kai Grossjohann
2004-10-24  1:17         ` Luc Teirlinck
2004-10-24  9:10           ` Kai Grossjohann
2004-10-24 15:09             ` Luc Teirlinck
2004-10-24 18:29             ` Luc Teirlinck
2004-10-24 20:06               ` Kai Grossjohann [this message]
2004-10-24 18:46             ` Luc Teirlinck
2004-10-24 19:30               ` Luc Teirlinck
2004-10-24 19:37               ` Luc Teirlinck
2004-10-24 20:08               ` Kai Grossjohann
2004-10-24 20:22                 ` Luc Teirlinck
2004-10-24 20:59                 ` Luc Teirlinck
2004-10-18 19:52   ` Michael Albinus
2004-10-23 20:00 ` Kai Grossjohann

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=86r7nnyj6p.fsf@ketchup.de.uu.net \
    --to=kai@emptydomain.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).