Date: Sat, 26 Jan 2019 11:38:35 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-arch@freebsd.org Subject: Re: Importing mksh in base Message-ID: <7c863100-0b5c-368e-e433-9caaf32e98d0@FreeBSD.org> In-Reply-To: <B3F3D854-847B-4731-9CEC-3E7BBDEDD8EC@vangyzen.net> References: <20190125165751.kpcjjncmf7j7maxd@ivaldir.net> <CALH631keUjj8qUomFY4nT2Mij9T7AWwFEGLDok=6zaaPx4T8DQ@mail.gmail.com> <CAG6CVpV5xY3KV_YVDuGBGt9Vt_xJA%2BGSX4g9zyFWcnTZvZrmpg@mail.gmail.com> <B3F3D854-847B-4731-9CEC-3E7BBDEDD8EC@vangyzen.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2zaivqmcoffFxZTGosWl9IbL1bs1fEiwR Content-Type: multipart/mixed; boundary="3XKCYUR2y2jq38VCN8i7F3rlYTm60tnAH"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-arch@freebsd.org Message-ID: <7c863100-0b5c-368e-e433-9caaf32e98d0@FreeBSD.org> Subject: Re: Importing mksh in base References: <20190125165751.kpcjjncmf7j7maxd@ivaldir.net> <CALH631keUjj8qUomFY4nT2Mij9T7AWwFEGLDok=6zaaPx4T8DQ@mail.gmail.com> <CAG6CVpV5xY3KV_YVDuGBGt9Vt_xJA+GSX4g9zyFWcnTZvZrmpg@mail.gmail.com> <B3F3D854-847B-4731-9CEC-3E7BBDEDD8EC@vangyzen.net> In-Reply-To: <B3F3D854-847B-4731-9CEC-3E7BBDEDD8EC@vangyzen.net> --3XKCYUR2y2jq38VCN8i7F3rlYTm60tnAH Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 25/01/2019 19:10, Eric van Gyzen wrote: > Ditto, except only 2 years on Linux before coming to FreeBSD. I > tried tcsh, since it was the default and in base, but I hated it for > interactive use. Notably absent are one-line =E2=80=9Cfor" loops. On = new > installs, after networking is up, my very first command is =E2=80=9Cpkg= > install bash [and others]=E2=80=9D. I have the opposite experience. I use tcsh as my interactive shell, mostly because I've used it for a long time and my fingers remember the command sequences. If I'm using bash interactively I tend to get frustrated by not being able to type 'foo<Esc>p' to replay the last command starting 'foo'. Yes, I know about <Ctrl>r but it just isn't the same. If it's for programming though, it's straight to /bin/sh -- and I will admit to dropping into sh to write for-loops at the command prompt. I'd be happy enough to see the default root shell changed to mksh. I'd be pretty happy to see the root shell switched to our current /bin/sh for that matter. Actually, what advantages does mksh have over /bin/sh? Cheers, Matthew --3XKCYUR2y2jq38VCN8i7F3rlYTm60tnAH-- --2zaivqmcoffFxZTGosWl9IbL1bs1fEiwR Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAlxMRrxfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDE5 RjE1NEVDQkYxMTJFNTA1NDRFM0YzMDAwNTEzRjEwRTBBOUU0RTcACgkQAFE/EOCp 5Ocs1g/+JwOhoJ7SG4GEZU2DXmabJcpfMYfZE7V5W4nREBJuWHpS+1PrAZoaDf9u HnJZPX/6mrEwdjn65yVOjkZGvTuq4FA0OEPQWH/NGHYQywpvcWQLPLst6XsxbFre abEifirx6JkfSU4VBPUQuDFl6qTLasxchH5NpbcLuHa1RlyG9KTuE0Dayy+tGigp R0+HQ/kGlYlI+cHue+LKgIgYuwHzKghXRzXUxruQgwE7m1v0pCz5HXlPRR2399bX CZj1X5S1lsaXjupMb36uNGGxODwESmShv0ARD54ubTX7utn7QL52eXD2ssEd7oV/ 16pmHPSPpw5DbtaCVfcJjZJh5WbaDaXCAzjdqRk84pmgkGk/UW2hzRAYYqJusYKX IF+FYFXGdOQpCsFwuMH1c2PZl5+0pnuakQhb1BKNESCS45IWOAvbIeoiURdZwuoT yCkT5V8wIi4rnDTx9feJNLbxE0wieY7sqENCOJdmcr1bt91VZGGJWAoLkWGvJTkV kARZ77gew3/qBURhlC2vU2cX3xcXfud1SvWZ3kUoxtzbLbiPaeF4CQL1iZcB8CdJ BsWDtCXRz0mSjwv+lT0PEmQebtV+vjQDY5Y+k9/YSqNE1UPs90QQH15munE9T5SC awWogODcVYXhyq63fTUzrCw6ID+wQytWO15NX0mz0u1Xr57Oedo= =bb7t -----END PGP SIGNATURE----- --2zaivqmcoffFxZTGosWl9IbL1bs1fEiwR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7c863100-0b5c-368e-e433-9caaf32e98d0>