all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: GNU emacs locks files modified with CVS
Date: Mon, 15 Dec 2003 11:04:42 -0700	[thread overview]
Message-ID: <3FDDF7BA.3090109@yahoo.com> (raw)
In-Reply-To: 3FDDA843.10800@tpd.tno.nl

Pepijn Kenter wrote:

> When loged in as user1 type:
> su user2
> emacs file.pro # edit, exit and save the changes
> emacs file.pro # file.pro is now read only.
> 
> I can not edit file.pro the second time because it is apperently locked 
> by user2 (as shown in the status line? of emacs). File permissions are 
> correct and the onwner of file.pro (still) is user2.
> 
> After some googling I think the possible cause is that emacs is 
> inconsistent in the way it handles the USER and LOGNAME variables.
> Indeed USER is set to user2 whereas LOGNAME is still user1. When I 
> change LOGNAME to user2 the problem disappears.
> 
> So, what to do?

If you want a login shell as user2, use `su - user2`.

-- 
Kevin Rodgers

  reply	other threads:[~2003-12-15 18:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-15 12:25 GNU emacs locks files modified with CVS Pepijn Kenter
2003-12-15 18:04 ` Kevin Rodgers [this message]
2003-12-16  9:44   ` Pepijn Kenter
2003-12-16 14:10     ` gebser
     [not found] <mailman.138.1071587578.868.help-gnu-emacs@gnu.org>
2003-12-16 14:51 ` Pepijn Kenter
2003-12-16 16:26   ` gebser
2003-12-17  6:42   ` Maurizio Loreti
2003-12-17 15:34     ` gebser
     [not found] <mailman.195.1071679031.868.help-gnu-emacs@gnu.org>
2003-12-17 16:26 ` Kevin Rodgers
2003-12-17 19:03   ` gebser
2003-12-17 16:41 ` Pepijn Kenter
2003-12-17 17:54 ` Maurizio Loreti
2003-12-18 17:19   ` Kevin Rodgers

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FDDF7BA.3090109@yahoo.com \
    --to=ihs_4664@yahoo.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.