| 1 |
On 05/22/2018 03:06 PM, David M. Fellows wrote: |
| 2 |
> As a terminal emulator that has a lot of configurabilty. |
| 3 |
|
| 4 |
I'm quite curious what sort of configuration you use in (what I |
| 5 |
understand to be) a text based communications package in your day to day |
| 6 |
activities. |
| 7 |
|
| 8 |
I do so much via SSH that I don't even think of anything other than |
| 9 |
XTerm and SSH. |
| 10 |
|
| 11 |
Please enlighten me to what I might be missing. |
| 12 |
|
| 13 |
> Yes, but.. you can do some neat things with it. |
| 14 |
|
| 15 |
<monotone>ya...</monotone> |
| 16 |
|
| 17 |
I know. |
| 18 |
|
| 19 |
I'm thinking about something that is very much so expect adjacent. |
| 20 |
|
| 21 |
I agree that expect does have it's use cases, and that very little else |
| 22 |
will do when you truly need it. |
| 23 |
|
| 24 |
I ran in to too many people that would try to do things like use expect |
| 25 |
to call commands to create users and deal with the failure cases instead |
| 26 |
of actually looking to see if the user existed first. Read: expect was |
| 27 |
the wrong tool for that job. |
| 28 |
|
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Grant. . . . |
| 33 |
unix || die |
Archives