On 9/21/2016 7:30 AM, Richard Owlett wrote:
On 9/21/2016 7:06 AM, David wrote:
On 21 September 2016 at 21:59, Richard Owlett
wrote:
I'm learning the shell.
Which shell?
That may be an an even better question than meets the eye.
I have two use cases:
1. the immediate one being whatever
Gregg writes:
> imadev:~$ csh
> % echo "$0"
> No file for $0.
Well, that tells you that you are running something weird and
nonstandard such as csh. But if you are running csh you already knew
that.
If
echo $0
doesn't produce satisfactory results run
ps
and examine the output
On Wed, Sep 21, 2016 at 08:18:36AM -0500, John Hasler wrote:
> To find out what shell you are running type
>
> echo $0
imadev:~$ csh
% echo "$0"
No file for $0.
The world's a much bigger place than just the Bourne family of shells,
unfortunately.
ps -p $$ # works in csh too
Richard writes:
> When in an arbitrary terminal of an arbitrary Desktop Environment, how
> would I determine which shell is in use?
To find out what shell is the login shell type
echo $SHELL
To find out what shell you are running type
echo $0
To run the Korn shell type
ksh
To kill the shell
On Wed, Sep 21, 2016 at 07:30:50AM -0500, Richard Owlett wrote:
> 1. the immediate one being whatever shell MATE terminal uses.
Unless it's completely diverging from Unix standards, it should launch
your user account's shell as defined either by the $SHELL environment
variable, or by your entry
On 9/21/2016 7:06 AM, David wrote:
On 21 September 2016 at 21:59, Richard Owlett wrote:
I'm learning the shell.
Which shell?
That may be an an even better question than meets the eye.
I have two use cases:
1. the immediate one being whatever shell MATE terminal uses.
Sub-question: W
On Wed, 21 Sep 2016 07:18:50 -0500
Richard Owlett wrote:
Hello Richard,
>Is this a systemd thing?
No, it's a bash thing. If you're not using bash (IDK what Mate's
terminal is based on) then it won't exist. Look for something like
equivalent to see what you've got, if anything.
--
Regards
Hello,
Not a bug, but a feature since the first C shell release in 1978 [1],
which was copied to pretty much every shell created since (Korn
shell/ksh, Bourne again shell/bash, Z shell/zsh, …). The reason behind
it is that – since Unix predates most graphical user interfaces, and
most of the time
On 9/21/2016 7:04 AM, humbert.olivie...@free.fr wrote:
De: "Richard Owlett"
Workaround?
rm ~/.bash_history
HTH
It didn't :<
No such file seems to exist in any directory.
Is this a systemd thing?
On 21 September 2016 at 21:59, Richard Owlett wrote:
> I'm learning the shell.
Which shell?
Try 'man whatever.shell.you.are.using' and read what it says about "history".
In bash for example, you can set HISTFILESIZE to zero.
De: "Richard Owlett"
> Workaround?
rm ~/.bash_history
HTH
I'm learning the shell.
I experiment with test cases in "MATE Terminal"
The "up arrow" key is useful to recall previous command for editing.
I hadn't expected it when I found all instances of "MATE
Terminal" share same history.
*HOWEVER* I found that history remains after a "power off",
"boot"
12 matches
Mail list logo