all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: I'am root user, but 'emacs /etc/sudoers' still report Buffer is read-only: #<buffer sudoers> in modeline
Date: Fri, 01 May 2015 03:23:19 +0200	[thread overview]
Message-ID: <87twvxozug.fsf@debian.uxu> (raw)
In-Reply-To: mailman.2062.1430429791.904.help-gnu-emacs@gnu.org

Bob Proulx <bob@proulx.com> writes:

> And so we have vipw and visudo which both would have
> originally spawned vi on the respective files.
> But now the vi part of the name of those classic
> tools is used generically to mean edit the file.
> Anything else would require changing the name and
> that would be egregiously breaking scripts and
> things that used the previous name.

No, hands off "visudo"! :)

>> If you are dead set on using Emacs, try
>> 
>>     sudo EDITOR='/usr/bin/emacs -u USER' visudo
>
> Not necessary when using the typical sudo
> configuration. Really! :-) What does this say
> for you?
>
>   $ sudo printenv HOME

Indeed:

    /root

Nice catch! I wonder how that happened. Probably my
hacker friends in the FSB. Investigating...

-- 
underground experts united
http://user.it.uu.se/~embe8573


  parent reply	other threads:[~2015-05-01  1:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29  6:27 I'am root user, but 'emacs /etc/sudoers' still report Buffer is read-only: #<buffer sudoers> in modeline Show Dont
2015-04-29  8:25 ` Bob Proulx
2015-04-29  8:36 ` tomas
2015-04-29  9:24 ` Alex Kost
2015-04-29 10:33 ` tomas
     [not found] ` <mailman.1889.1430298251.904.help-gnu-emacs@gnu.org>
2015-04-29 20:08   ` Emanuel Berg
2015-04-29 20:29     ` Emanuel Berg
2015-04-30 21:36       ` Bob Proulx
     [not found]       ` <mailman.2062.1430429791.904.help-gnu-emacs@gnu.org>
2015-05-01  1:23         ` Emanuel Berg [this message]
2015-05-01  2:31         ` Emanuel Berg

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=87twvxozug.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=help-gnu-emacs@gnu.org \
    /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.