On 11/30/06, Jan Grant <[EMAIL PROTECTED]> wrote:
On Thu, 30 Nov 2006, Andrew Pantyukhin wrote:
> I think, I'll follow your advice. It's high time I forgot about
> csh, but I wonder if you tried to change root's shell to zsh?
You can; I haven't. ("exec zsh" is simple to type.) sudo works well fo
On Thu, 30 Nov 2006, Andrew Pantyukhin wrote:
> I think, I'll follow your advice. It's high time I forgot about
> csh, but I wonder if you tried to change root's shell to zsh?
You can; I haven't. ("exec zsh" is simple to type.) sudo works well for
single commands. I don't tend to spend much time
On Nov 29, 2006, at 1:51 PM, Andrew Pantyukhin wrote:
zsh is a pretty good interactive shell (it finally weaned me off
tcsh),
as well as supporting a full range of redirection and control
constructs. You should look at that, in particular the
set -o sharehistory
option (which does half
On 11/30/06, Jan Grant <[EMAIL PROTECTED]> wrote:
On Wed, 29 Nov 2006, Andrew Pantyukhin wrote:
> I want to be able to define groups of interactive
> shells (preferably even across different users)
> so they have one single shared command history.
> Any command executed in one of them should be
On Wed, 29 Nov 2006, Andrew Pantyukhin wrote:
> I want to be able to define groups of interactive
> shells (preferably even across different users)
> so they have one single shared command history.
> Any command executed in one of them should be
> available through all history mechanisms in the
>
On 11/29/06, Andrew Pantyukhin <[EMAIL PROTECTED]> wrote:
I want to be able to define groups of interactive
shells (preferably even across different users)
so they have one single shared command history.
Any command executed in one of them should be
available through all history mechanisms in the
