From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: A question about Eshell
Date: Thu, 29 Jan 2004 09:30:02 +0100 [thread overview]
Message-ID: <87oesnkvhx.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: 87n08gi6vv.fsf@inspiron.nicundtas.de
"Tassilo Horn" <heimdall*REMOVETHIS*@uni-koblenz.de> writes:
> I really like using Eshell when having a console session but I have one
> problem. When I su to root I don't have highlighting of
> filetypes/directories and I don't have autocompletion, too. TAB makes
> real TABS instead.
> What can I do to have this features after suing?
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.
You could try to use Tramp to access files as root. In that case,
instead of su'ing to root, do "cd /root@localhost:/some/directory".
After this, find-file should edit files as root, and so on.
Alas, Tramp is not quite up to snuff regarding running commands. That
is, if you run a command then the command might not be run as root,
causing it to have too little permission. It's been this way for
quite a while, and it would be great to fix it, but I haven't had the
energy to do that. (In fact, I don't even know exactly in what way it
is broken.) Anyone?
Kai
next prev parent reply other threads:[~2004-01-29 8:30 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 [this message]
2004-01-29 10:59 ` Tassilo Horn
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=87oesnkvhx.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.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).