1. Missing quotes
#
[me@linuxbox me]$ ./trouble.bash
./trouble.bash: line 8430: unexpected EOF while looking for matching "
./trouble.bash: line 8440 systax error: unexpected end of file
#
We have 2017, please add s
I'm not even sure if cd is part of Bash?
anyway - if you type any of the following:
cd / ; pwd
cd /// ; pwd
cd ; pwd
the CLI always reports
/
but, if you do this:
cd // ; pwd
then the CLI reports
//
--
Kae Verens
http://kvsites.ie/
On 7/14/17 7:14 AM, Kae Verens wrote:
> I'm not even sure if cd is part of Bash?
It is. It's a regular shell builtin.
> anyway - if you type any of the following:
> cd / ; pwd
> cd /// ; pwd
> cd ; pwd
>
> the CLI always reports
> /
>
> but, if you do this:
> cd // ; pwd
>
> then the CLI
On Fri, Jul 14, 2017 at 11:09:25AM +0200, t wrote:
> #
> [me@linuxbox me]$ ./trouble.bash
> ./trouble.bash: line 8430: unexpected EOF while looking for matching "
> ./trouble.bash: line 8440 systax error: unexpected end of file
Your problem is that your scri
Date:Thu, 13 Jul 2017 23:02:49 -0400
From:Chet Ramey
Message-ID: <102d254a-d321-20c0-b8d6-9f2257861...@case.edu>
| Posix, the closest thing we have to a standard description of SHELL, says:
It does, but POSIX doesn't say the shell is intended to set it.
That is, it
On Sat, Jul 15, 2017 at 02:59:41AM +0700, Robert Elz wrote:
> IMO, if SHELL gets unset (it is usually initialised by login, or its
> equivalent), it should simply stay unset, and not be set to anything,
> until some user (or script) decides to set it again.
wooledg:~$ unset SHELL
wooledg:~$ bash -
On 07/14/2017 03:13 PM, Greg Wooledge wrote:
> On Sat, Jul 15, 2017 at 02:59:41AM +0700, Robert Elz wrote:
>> IMO, if SHELL gets unset (it is usually initialised by login, or its
>> equivalent), it should simply stay unset, and not be set to anything,
>> until some user (or script) decides to set i
