[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Java buffers are randomly read-only

From: Coleman, Don
Subject: RE: Java buffers are randomly read-only
Date: Tue, 21 Nov 2000 16:48:11 -0500

Thanks for you answer.  My fix was a little different.  Based on what you said, I noticed that when a file was read-only the status bar said "(JDE CVS:DColeman:1.4)" as opposed to "(JDE CVS-1.4)"

DColeman is my NT login name (which is different from my cvs login)
I added the following to my .emacs --> (setq user-login-name "DColeman") ; case is important!
Note that if I set an incorrect username all CVS controlled buffers were read only.

This works on my machine and another user's machine.  We are both using emacs 20.6.1 for NT.

-Don Coleman

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden]
> Sent: Tuesday, November 21, 2000 3:27 PM
> To: address@hidden; address@hidden;
> address@hidden
> Subject: RE: Java buffers are randomly read-only
> I did a little work tracking down this problem and found it to be
> related to, believe it or not, an inconsistency in the way
> the CVS lisp
> code handles the users login name. I was stepping through the
> code, and
> found the name sometimes in all uppercase and sometimes in all lower
> case. I can't remember exaclty in which elisp file the
> problem resided,
> sorry. However, my workaround was rather simple and so far I
> haven't had
> any read-only buffers. The workaround was to put (setq user-login-name
> "MY_USER_NAME_IN_UPPER_CASE") in my .emacs file.
> My hunch is that this problem is due to an unexpected NT related side
> effect.
> Chuck Irvine
> Sprint
>    -----Original Message-----
>    From:       donald.coleman [mailto:address@hidden]
>    Sent:       Tuesday, November 21, 2000 1:55 PM
>    To:         jde
>    Subject:    Java buffers are randomly read-only
>  I don't know if this is a JDE specific problem. Java buffers
> seem to be
> randomly read-only when I open them. I am using JDE2.2.6beta5
> and WinNT.
> The files are read/write according to NT. M-x toggle-read-only is a
> temporary fix, but I'd like to find out what is causing this problem.
> Any ideas?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]