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 20:23:15 +0300 [thread overview]
Message-ID: <83wrgbta7w.fsf@gnu.org> (raw)
In-Reply-To: <40C7B1BFC291ED4E9D10436D07736A3346F8B2DDEB@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 09:03:42 -0700
>
> > Did you also change the RCS port you are using, since the last time this
> > worked for you? If so, where did you get your port of RCS? Was that last
> > time also on Windows Vista, or on some other OS?
>
> Sensible question - I use the Cygwin port. I just tried downgrading from 1.57-11 to 1.57-4 (the only older version I could find listed in the current Cygwin setup list), but this didn't change anything.
If you are using the Cygwin build of RCS with a native build of Emacs,
there could be problems that I'm not aware of. I don't use Cygwin.
> What version of RCS are you using?
The native Windows port I found on the GnuWin32 site.
> > > b. Now edit the file by adding a comment somewhere, say, after line 1,
> >
> > Wait a moment: isn't the buffer read-only after the initial registration and
> > check-in? It should be; it is for me (using RCS with Emacs 23.3 on Windows
> > XP). If so, you cannot just add a comment; you need to check-out the file
> > first, by typing "C-x v v" again. This checks out the file making it writable, and
> > then I can edit it.
>
> The buffer itself is not read-only, but the file seems to be.
That is already a sign of a problem. The buffer should be read-only.
What does "rlog test.tex" show after that initial checkin?
> > It's possible that the problem is with your username as RCS and Emacs
> > perceive it. Do you have USER or LOGNAME variables set in your
> > environment? If not, does it help to set one of them with the value returned
> > by `user-login-name' function inside Emacs?
>
> Doesn't seem to change anything.
What does user-login-name and user-real-login-name return inside
Emacs?
next prev parent reply other threads:[~2011-06-24 17:23 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 [this message]
2011-06-24 18:13 ` Richard Stanton
2011-06-24 19:14 ` Eli Zaretskii
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=83wrgbta7w.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).