From: Eli Zaretskii <eliz@gnu.org>
To: Richard Stanton <stanton@haas.berkeley.edu>
Cc: 8924@debbugs.gnu.org
Subject: bug#8924: 23.3; Editing is rather difficult using vc with RCS backend
Date: Fri, 24 Jun 2011 22:14:36 +0300 [thread overview]
Message-ID: <83tybft52b.fsf@gnu.org> (raw)
In-Reply-To: <40C7B1BFC291ED4E9D10436D07736A3346F8B2DE20@EXMAIL7.haas.uc.berkeley.edu>
> From: Richard Stanton <stanton@haas.berkeley.edu>
> CC: "8924@debbugs.gnu.org" <8924@debbugs.gnu.org>
> Date: Fri, 24 Jun 2011 11:13:31 -0700
>
> I may well be missing something obvious, but I can't find an RCS port at the GnuWin32 site.
Looks like they removed it. Perhaps because I reported a few bad bugs
with their port. I actually use a fixed port I built myself; I should
have mentioned that, sorry.
> > What does "rlog test.tex" show after that initial checkin?
>
> C:\projects\test\version\rcstest>rlog test.tex
>
> RCS file: RCS/test.tex,v
> Working file: test.tex
> head: 1.1
> branch:
> locks: strict
> access list:
> symbolic names:
> keyword substitution: kv
> total revisions: 1; selected revisions: 1
> description:
> ----------------------------
> revision 1.1
> date: 2011/06/24 18:10:25; author: stanton; state: Exp;
> Initial revision
> =============================================================================
>
> > What does user-login-name and user-real-login-name return inside Emacs?
>
> user-login-name: "stanton"
> user-real-login-name: "stanton"
Bummer.
The only thing I can suggest is step with Edebug through vc-rcs.el and
see what's wrong.
next prev parent reply other threads:[~2011-06-24 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 21:20 bug#8924: 23.3; Editing is rather difficult using vc with RCS backend Richard Stanton
2011-06-24 9:14 ` Eli Zaretskii
2011-06-24 16:03 ` Richard Stanton
2011-06-24 17:23 ` Eli Zaretskii
2011-06-24 18:13 ` Richard Stanton
2011-06-24 19:14 ` Eli Zaretskii [this message]
2011-06-24 20:46 ` Richard Stanton
2011-06-25 6:31 ` Eli Zaretskii
2011-06-24 18:20 ` Ken Brown
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=83tybft52b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=8924@debbugs.gnu.org \
--cc=stanton@haas.berkeley.edu \
/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).