Martin BishopOct 25
The 1969 Multics Condensed Guide shows that #Multics already incorporated a number of features foundational to the development of #Unix. The Multics command interpreter was designed by Louis Pouzin and Glenda Schroeder; a key innovation was that the command interpreter operated as a user-level program, separate from the kernel (Pouzin is credited with coining the term “shell” ca. 1964–65).
Show threadMartin Bishop
For text editing, #Multics provided two editors, edm and qed; Thompson wrote the first version of ed for #Unix by simplifying the Multics qed editor. The command ‘runcom’ allowed a user to execute a sequence of commands from a file (an ASCII text segment). While these were not explicitly referred to as "scripts", they effectively automated command execution and inspired shell scripting in Unix.
Via @unix_byte
Oct 25 at 11:43amMoshidon
Show threadrestoranteOct 25

@toomanysecrets

'branch' is something new to me, since I had never used Multics before.

If a segment is something to hold a program and data into a single place. Then 'branch segment-name' is running segment-name program and opening the respective data in the segment.

It is still confusing to me. Never met such concept before.

Edit: Glenda Schroeder, curious whether she had something to do with Glenda of the Plan9.

About segment, now I understand, it is actually just 'file'. The file can be data or program. Multics also has directory as well.

#Multics #Unix #Plan9

Show threadMartin BishopOct 25
@restorante I have to admit that I am in a position quite similar to you, since I have quite a distance left and I do not dominate so much 🤔