From: thibault@gmvhdl.com (Scott Thibault)
Subject: NTemacs doesn't understand RCS
Date: 4 Nov 2004 08:19:34 -0800 [thread overview]
Message-ID: <921d670a.0411040819.4a3a5f5d@posting.google.com> (raw)
Hi,
I'm using a version of RCS that allows you to create a text file
called RCS that contains a pointer to the RCS directory rather than a
real directory - a work around for not having links on Windows.
So, the question is how do I get emacs to understand these link files?
Out-of-the-box, when I try C-x v v, the ci command fails with the
message \src\RCS\file.c,v already exists. I assume because emacs
doesn't recognize the RCS "link" and tries to do a ci -i.
Any ideas??
--Scott
next reply other threads:[~2004-11-04 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 16:19 Scott Thibault [this message]
2004-11-04 18:46 ` NTemacs doesn't understand RCS Kevin Rodgers
2004-11-09 20:29 ` Scott Thibault
2004-11-09 23:03 ` Stefan Monnier
2004-11-10 0:45 ` Kevin Rodgers
2004-11-10 11:22 ` Scott Thibault
-- strict thread matches above, loose matches on Subject: below --
2004-12-22 5:47 Jonathan Freidin
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=921d670a.0411040819.4a3a5f5d@posting.google.com \
--to=thibault@gmvhdl.com \
/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).