unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Dieter Wilhelm <dieter@duenenhof-wilhelm.de>
To: help-gnu-emacs@gnu.org
Subject: Re: SU commands from Emacs
Date: Fri, 24 Aug 2007 22:20:40 +0200	[thread overview]
Message-ID: <873ay8y99j.fsf@debby.local.net> (raw)
In-Reply-To: <87y7g1s6qx.fsf@lion.rapttech.com.au> (Tim X.'s message of "Fri\, 24 Aug 2007 17\:59\:18 +1000")

Hi Tim,

normally I'm also using commands which require root privileges from
the shell buffer.  But I'm forcing myself to use more and more Emacs
inbuilt functionality.  In this line of reasoning using find-grep on
/etc was actually inattentiveness on my side.  Reading the su command
thread I was wondering if Emacs could even do privileged operations on
directories.  And low and behold it can! Emacs never ceases to amaze.

Michael Albinus and Peter Dyballa, as you probably already have read,
explained that the new tramp version in CVS is able to do this via a
dired buffer and the sudo prefix as you hinted at.  Even though it
might turn out to be a bit dangerous for inattentive users ;-).

The idea of you with multiple Emacs processes seems not so far fetched
in general.  I read that some users are doing this quite comfortably.
But as I'm only occasionally dabble with computers it's clearly not
necessary.  But I'll check the tramp method when I'm in the mood to
download the CVS version.

Also thank you for the hints with the lisp shells, good to know that
they exist.  Why do you mention Scheme as well, how it is related to
Emacs and Elisp?

-- 
    Best wishes

    H. Dieter Wilhelm
    Darmstadt, Germany

  reply	other threads:[~2007-08-24 20:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17 17:38 SU commands from Emacs Joel J. Adamson
2007-08-17 18:23 ` Emilio Lopes
2007-08-17 19:38   ` Joel J. Adamson
2007-08-18  9:55     ` Emilio Lopes
2007-08-17 19:04 ` David Hansen
2007-08-17 19:27 ` Peter Dyballa
     [not found] ` <mailman.4925.1187378874.32220.help-gnu-emacs@gnu.org>
2007-08-17 20:23   ` Joel J. Adamson
2007-08-17 20:37     ` Sven Joachim
     [not found] ` <mailman.4924.1187377704.32220.help-gnu-emacs@gnu.org>
2007-08-17 20:28   ` Joel J. Adamson
2007-08-24  6:38     ` Dieter Wilhelm
2007-08-24  9:37       ` Michael Albinus
2007-08-24 20:32         ` Dieter Wilhelm
2007-08-24 22:16           ` Peter Dyballa
2007-08-25  2:45             ` Dieter Wilhelm
2007-08-25 19:35             ` Joel J. Adamson
2007-08-26  8:49               ` Michael Albinus
2007-08-27 13:28                 ` Joel J. Adamson
     [not found]         ` <mailman.5288.1187987493.32220.help-gnu-emacs@gnu.org>
2007-08-24 21:55           ` David Kastrup
2007-08-25  3:00             ` Dieter Wilhelm
2007-08-26 10:55               ` Michael Albinus
2007-08-24  9:51       ` Peter Dyballa
     [not found]     ` <mailman.5238.1187937431.32220.help-gnu-emacs@gnu.org>
2007-08-24  7:59       ` Tim X
2007-08-24 20:20         ` Dieter Wilhelm [this message]
     [not found]         ` <mailman.5305.1188026786.32220.help-gnu-emacs@gnu.org>
2007-08-25  9:28           ` Tim X
2007-08-25 13:57             ` Dieter Wilhelm

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=873ay8y99j.fsf@debby.local.net \
    --to=dieter@duenenhof-wilhelm.de \
    --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.
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).