From: "Tassilo Horn" <heimdall*REMOVETHIS*@uni-koblenz.de>
Subject: Re: A question about Eshell
Date: Thu, 29 Jan 2004 11:59:54 +0100 [thread overview]
Message-ID: <87llnrxbo5.fsf@inspiron.nicundtas.de> (raw)
In-Reply-To: 87oesnkvhx.fsf@emptyhost.emptydomain.de
Kai Grossjohann <kai@emptydomain.de> writes:
> Eshell does not run a real shell. Instead, it interprets each command
> as you type it. Now, if you type su, then eshell will start a su
> process and send subsequent input to it. It will not interpret the
> I/O itself.
>
> That's why su and normal usage are different.
>
> [Tramp stuff]
Thanks for the tipps. Instead of this I now use sudo to do the root-only
tasks. I really don't need a root shell but some commands like
fetchnews. And for this sudo seems to be the easiest solution.
> Kai
Much thanks,
Tassilo
--
If riding in an airplane is flying, then riding in a boat is swimming.
If you want to experience the element, then get out of the vehicle
- skydive! www.fscnrw.de
prev parent reply other threads:[~2004-01-29 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 11:01 A question about Eshell Tassilo Horn
2004-01-29 8:30 ` Kai Grossjohann
2004-01-29 10:59 ` Tassilo Horn [this message]
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=87llnrxbo5.fsf@inspiron.nicundtas.de \
--to=heimdall*removethis*@uni-koblenz.de \
/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).