6 Dec
2017
6 Dec
'17
1:22 a.m.
I tried a long time ago to set PS1 and PS2 to character sequences
which would permit cut-paste to work. I failed, but I didn't try very
hard.
The choice of "# " and "> " interests me. Because roots prompt of
"hash" has a side effect of making a cut-paste over it a comment in
most shells.
But.. it predates being *able* to cut-paste so it has to be a
side-effect, not a design choice.
"> " is more dangerous in cut-paste. Which again feels like a
side-effect both by anachronistic time effects, and intent: nobody
would be that suicidally mad to make cut-paste invoke shell
pre-forming the command sequence which neccessarily zeros out the >
targets before executing the cmd...
-G
6 Dec
6 Dec
1:28 a.m.
On Wed, Dec 06, 2017 at 11:22:52AM +1000, George Michaelson wrote:
I tried a long time ago to set PS1 and PS2 to
character sequences
which would permit cut-paste to work. I failed, but I didn't try very
hard.
I've used :; and ::; to good effect. Since : is a no-op, it just inserts
noise into the history.
khm
2:26 a.m.
On Dec 5, 2017, at 5:28 PM, Kurt H Maier
<khm(a)sciops.net> wrote:
I've used :; and ::; to good effect. Since : is a no-op, it just inserts
noise into the history.
This fragment lives in my ${HOME}/.env on pretty much every machine I log in to. If you
'export ENV=${HOME}/.env' in .profile, then configure sudo/doas to pass ENV
through unmolested, this will follow you as you switch uids.
_hostname=$(hostname | sed -e 's/\.hushmail\(inc\)*\.com$//')
awd=$(which awd 2>/dev/null)
if [ "${awd}" == "" ] ; then
awd=':'
fi
setprompt () { PS1=": $(id -un)@$_hostname:$(pwd); " ; }
cd () { command cd "$@" && setprompt && ${awd} ; }
setprompt
It works with pretty much every Bourne/Korn shell variant I've stumbled across.
Adjust the _hostname bit to match the domains of the systems you regularly log in to, and
drop the awd bits if you don't use plan9port.
--lyndon
1:30 a.m.
On Wed, 6 Dec 2017, George Michaelson wrote:
I tried a long time ago to set PS1 and PS2 to
character sequences
which would permit cut-paste to work. I failed, but I didn't try very
hard.
The choice of "# " and "> " interests me. Because roots prompt of
"hash" has a side effect of making a cut-paste over it a comment in
most shells.
But.. it predates being *able* to cut-paste so it has to be a
side-effect, not a design choice.
"> " is more dangerous in cut-paste. Which again feels like a
side-effect both by anachronistic time effects, and intent: nobody
would be that suicidally mad to make cut-paste invoke shell
pre-forming the command sequence which neccessarily zeros out the >
targets before executing the cmd...
-G
I think this is why rc used a ";" ?
Maybe use "; " for PS1 and " " for PS2?
-uso.
3:45 a.m.
On 12/05/2017 06:22 PM, George Michaelson wrote:
I tried a long time ago to set PS1 and PS2 to
character sequences
which would permit cut-paste to work. I failed, but I didn't try very
hard.
What do you mean by "permit cut (and) paste to work"? Do you want to be
able to cut (triple click the entire line in Xterm) and then paste it
(middle click a new line) and have it execute? Or do you mean that you
want it to not execute as a safety measure?
Or are you wanting to go one step further and have something that
toggles input interpretation off until a character sequence is provided,
possibly by the prompt? Ideally so that you would not accidentally copy
& paste swaths of screen output and have it executed.
--
Grant. . . .
unix || die
5:53 a.m.
George Michaelson <ggm(a)algebras.org> wrote:
The choice of "# " and "> "
interests me. Because roots prompt of
"hash" has a side effect of making a cut-paste over it a comment in
most shells.
"#" as the root prompt predates # as the comment in the Bourne shell,
not to mention predating copy/paste entirely. (My understanding is that
the do-nothing command, ":" was used for comments. Talk about minimalist!)
Same point for ">", since copy/paste didn't exist in the late 70s when
Bourne was doing the shell, it wasn't an issue.
Arnold
6:01 a.m.
So.. arnold.. you never used the ! command in ex or vi? because it
will treat a range command as the bounding set of lines to feed into
the command.. if you specify sh or /path/to/shell then its
functionally a cut-paste-exec sequence isn't it?
emacs has the same functionality (in some syntactic suger)
I used fmt all the time in vi, to get <72 for mail in MH. which led me
to find other things you can pipe the editor lines through...
-G
3:14 p.m.
On 2017-12-06 16:01, George Michaelson wrote:
I used fmt all the time in vi, to get <72 for mail
in MH. which led me
to find other things you can pipe the editor lines through...
Exactly! Just put a trivial script in front of the /bin/sh in the pipe
to strip the undesirable stuff like prompts. I do this for browsing
URLs in mail bodies which may be split across multiple lines or
otherwise mangled.
With emacs, you don't even need an extra process, because the demangling
can be programmed in lisp.
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.
6:19 a.m.
On Tue, 5 Dec 2017, arnold(a)skeeve.com wrote:
"#" as the root prompt predates # as the
comment in the Bourne shell,
not to mention predating copy/paste entirely. (My understanding is that
the do-nothing command, ":" was used for comments. Talk about
minimalist!)
And as a label for the dreaded "goto" command; it was a while before I
realised that ":" in and of itself did bugger-all...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will
suffer."
8 a.m.
Dave Horsfall <dave(a)horsfall.org> wrote:
On Tue, 5 Dec 2017, arnold(a)skeeve.com wrote:
"goto" was in the V6 shell, I think (next to no experience with the V6
shell, and it was a LONG time ago anyway). But there never was a goto
in the V7 shell.
"#" as the root prompt predates # as
the comment in the Bourne shell,
not to mention predating copy/paste entirely. (My understanding is that
the do-nothing command, ":" was used for comments. Talk about
minimalist!)
And as a label for the dreaded "goto" command; it was a while before I
realised that ":" in and of itself did bugger-all...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will
suffer."
11:57 p.m.
On Wed, 6 Dec 2017, arnold(a)skeeve.com wrote:
"goto" was in the V6 shell, I think (next to
no experience with the V6
shell, and it was a LONG time ago anyway). But there never was a goto
in the V7 shell.
Never got to use the V7 shell; we were stuck with 11/40s[*] :-( It was
certainly in the V6 shell, hence by bafflement at why labels were of the
form ": blah" instead of the sensible "blah: "...
[*]
Although I did shove as much of the V7 kernel into V6 as I could (such as
XON/XOFF), thereby earning me the sobriquet "Mr Unix 6.5" or something;
having the AUSAM buffer scheme helped a lot.
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will
suffer."
7 Dec
7 Dec
8:33 a.m.
On Wed, 6 Dec 2017, arnold(a)skeeve.com wrote:
> "goto" was in the V6 shell, I think (next to no experience with the V6
> shell, and it was a LONG time ago anyway). But there never was a goto
> in the V7 shell.
Dave Horsfall <dave(a)horsfall.org> wrote:
Never got to use the V7 shell; we were stuck with
11/40s[*] :-( It was
certainly in the V6 shell, hence by bafflement at why labels were of the
form ": blah" instead of the sensible "blah: "...
Come now, since then you've *never* used any kind of Bourne shell?
BSD on vax? SunOS? System III or System V on anything else? You've been
stuck in a time warp for 35 years? :-)
Arnold
9:46 p.m.
On Thu, 7 Dec 2017, arnold(a)skeeve.com wrote:
Sigh; there's one in every bunch :-) OK, I never got to use the V7 shell
on V7, because I never got to use V7 on my machines (and the use of "goto"
had been thoroughly beaten out of me by then, so I never thought to try
it).
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will
suffer."
Never got to
use the V7 shell; we were stuck with 11/40s[*] :-( It was
certainly in the V6 shell, hence by bafflement at why labels were of
the form ": blah" instead of the sensible "blah: "...
Come now, since then you've *never* used any kind of Bourne shell? BSD
on vax? SunOS? System III or System V on anything else? You've been
stuck in a time warp for 35 years? :-)
8 Dec
8 Dec
6:12 a.m.
Hi.
Dave Horsfall <dave(a)horsfall.org> wrote:
On Thu, 7 Dec 2017, arnold(a)skeeve.com wrote:
Sigh; there's one in every bunch :-)
Sorry. I tend to be too literal-minded sometimes. That can help for
doing software development, but can get in the way at other times.
Never got
to use the V7 shell; we were stuck with 11/40s[*] :-( It was
certainly in the V6 shell, hence by bafflement at why labels were of
the form ": blah" instead of the sensible "blah: "...
Come now, since then you've *never* used any kind of Bourne shell? BSD
on vax? SunOS? System III or System V on anything else? You've been
stuck in a time warp for 35 years? :-) OK, I never got to use the V7 shell on V7, because I
never got to use
V7 on my machines (and the use of "goto" had been thoroughly beaten out
of me by then, so I never thought to try it).
I see. Much better. :-)
Thanks,
Arnold
7 Dec
7 Dec
9:54 p.m.
On Wed, Dec 6, 2017 at 6:57 PM, Dave Horsfall <dave(a)horsfall.org> wrote:
Never got to use the V7 shell; we were stuck with 11/40s[*]
Dave I don't understand this statement. We ran Seventh Edition on 11/40
class processors more than anything else. The issue was lack of separate
I/D space and the kernel got large so you ran out of physical memory. The
later was solved with things like the Able ENABLE, which I admit I put one
couple of 11/34 and our 11/60 (which are 11/40 class). But V7 ran fine on
it.
Clem
8 Dec
8 Dec
12:31 a.m.
On Thu, 7 Dec 2017, Clem Cole wrote:
I tried, but no way it would work; the only non-DEC gear we ended up with
was extra memory (nothing special, but of course not covered by Field
Circus) and an Ampex[*] RP-03 clone (I think). For all intents and
porpoises it was a maxed-out 11/40 (then the /60 later on).
As I mentioned before, the AUSAM buffer scheme certainly helped, and we
kissed goodbye to deadlocks; we even modified character devices (LP. XY,
LV etc) to use the buffer pool instead of the character queues, and they
went damned fast.
I should mention that the /40s were originally specced to run RSX-11D
(yuck), and when the ACM article came out the rest was history...
[*]
My spell checker suggested "Tampax" for "Ampex"...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will
suffer."
Never got to
use the V7 shell; we were stuck with 11/40s[*]
Dave I don't understand this statement. We ran Seventh Edition on 11/40
class processors more than anything else. The issue was lack of separate
I/D space and the kernel got large so you ran out of physical memory. The
later was solved with things like the Able ENABLE, which I admit I put one
couple of 11/34 and our 11/60 (which are 11/40 class). But V7 ran fine on
it. 
16 Dec
16 Dec
5:42 p.m.
On Wed, Dec 06, 2017 at 11:22:52AM +1000, George Michaelson wrote:
I tried a long time ago to set PS1 and PS2 to
character sequences
which would permit cut-paste to work. I failed, but I didn't try very
hard.
h=spuggy$; ssh copper
h=copper$;
h=copper$; pwd
/usr/home/derek
h=copper$; h=copper$; pwd
/usr/home/derek
h=copper$;
.pdf
17 Dec
17 Dec
1:12 p.m.
I just put a newline at the end of my prompt, so the command has the whole next line to
itself and there’s no prompt to get in the way of copying and pasting.
-Don
On 16 Dec 2017, at 18:42, Derek Fawcus
<dfawcus+lists-tuhs(a)employees.org> wrote:
On Wed, Dec 06, 2017 at 11:22:52AM +1000, George Michaelson wrote:
I tried a long time ago to set PS1 and PS2 to
character sequences
which would permit cut-paste to work. I failed, but I didn't try very
hard.
h=spuggy$; ssh copper
h=copper$;
h=copper$; pwd
/usr/home/derek
h=copper$; h=copper$; pwd
/usr/home/derek
h=copper$;
.pdf
2329
days inactive
2340
days old
17 comments
11 participants
participants (11)
-
arnold＠skeeve.com -
Clem Cole -
Dave Horsfall -
Derek Fawcus -
Don Hopkins -
George Michaelson -
Grant Taylor -
Ian Zimmerman -
Kurt H Maier -
Lyndon Nerenberg -
Steve Nickolas