From: J-P Theberge <jphiltheberge@videotron.ca>
Subject: Re: buffer uid
Date: 10 Oct 2003 16:33:00 -0400 [thread overview]
Message-ID: <m38ynsal4z.fsf@megalon.localdomain> (raw)
In-Reply-To: mailman.1502.1065808219.21628.help-gnu-emacs@gnu.org
Arthur Davis <adavis@torrentnet.com> writes:
> Is it possible to open a buffer and edit it as a different user? In
> other words, if I have two user accounts, can I run emacs from one
> account and edit a file owned by the other account (and not writable
> by the account running emacs)?
Hi,
I use this:
(defun find-file-as-another-user (f u)
(interactive "sFind file: \ns as user: ")
(require 'tramp)
(find-file (concat "/su:" u "@localhost:" f)))
It require tramp
-jp
next prev parent reply other threads:[~2003-10-10 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1502.1065808219.21628.help-gnu-emacs@gnu.org>
2003-10-10 18:02 ` buffer uid Stefan Monnier
2003-10-10 20:33 ` J-P Theberge [this message]
[not found] <mailman.1794.1066311260.21628.help-gnu-emacs@gnu.org>
2003-10-18 7:05 ` Tim X
2003-10-16 13:30 andrew.maguire
-- strict thread matches above, loose matches on Subject: below --
2003-10-10 17:48 Arthur Davis
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=m38ynsal4z.fsf@megalon.localdomain \
--to=jphiltheberge@videotron.ca \
/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).