How did Bourne shell solve missing teletype keys problem?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












3














I've learned recently from DigitalRoss's answer that certain teletypes such as ASR-33 lacked certain keys; for instance |. For that purpose in C there exist trigraph operators that can be substituted for | and some others.



Now, this begs the question what was done in Bourne shell back in the day to solve this problem ?










share|improve this question

















  • 3




    Possible duplicate of Use of ^ as a shell metacharacter
    – roaima
    Dec 29 '18 at 9:39






  • 1




    Trigraphs in C were not introduced because of the Teletype Model 33, they came much later. The reason for trigraphs were the ISO-646 character set, which allowed certain characters like to be replaced by national characters like äöå.
    – Johan Myréen
    Dec 29 '18 at 12:22










  • The proposed duplicate does not answer the question of how one entered these characters (more than just |) when that sort of teletype was a Unix terminal. Unfortunately this question is written as if the shell were all that one interacted with on a terminal.
    – JdeBP
    Dec 29 '18 at 17:35















3














I've learned recently from DigitalRoss's answer that certain teletypes such as ASR-33 lacked certain keys; for instance |. For that purpose in C there exist trigraph operators that can be substituted for | and some others.



Now, this begs the question what was done in Bourne shell back in the day to solve this problem ?










share|improve this question

















  • 3




    Possible duplicate of Use of ^ as a shell metacharacter
    – roaima
    Dec 29 '18 at 9:39






  • 1




    Trigraphs in C were not introduced because of the Teletype Model 33, they came much later. The reason for trigraphs were the ISO-646 character set, which allowed certain characters like to be replaced by national characters like äöå.
    – Johan Myréen
    Dec 29 '18 at 12:22










  • The proposed duplicate does not answer the question of how one entered these characters (more than just |) when that sort of teletype was a Unix terminal. Unfortunately this question is written as if the shell were all that one interacted with on a terminal.
    – JdeBP
    Dec 29 '18 at 17:35













3












3








3







I've learned recently from DigitalRoss's answer that certain teletypes such as ASR-33 lacked certain keys; for instance |. For that purpose in C there exist trigraph operators that can be substituted for | and some others.



Now, this begs the question what was done in Bourne shell back in the day to solve this problem ?










share|improve this question













I've learned recently from DigitalRoss's answer that certain teletypes such as ASR-33 lacked certain keys; for instance |. For that purpose in C there exist trigraph operators that can be substituted for | and some others.



Now, this begs the question what was done in Bourne shell back in the day to solve this problem ?







history bourne-shell






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 29 '18 at 9:28









Sergiy KolodyazhnyySergiy Kolodyazhnyy

8,53312254




8,53312254







  • 3




    Possible duplicate of Use of ^ as a shell metacharacter
    – roaima
    Dec 29 '18 at 9:39






  • 1




    Trigraphs in C were not introduced because of the Teletype Model 33, they came much later. The reason for trigraphs were the ISO-646 character set, which allowed certain characters like to be replaced by national characters like äöå.
    – Johan Myréen
    Dec 29 '18 at 12:22










  • The proposed duplicate does not answer the question of how one entered these characters (more than just |) when that sort of teletype was a Unix terminal. Unfortunately this question is written as if the shell were all that one interacted with on a terminal.
    – JdeBP
    Dec 29 '18 at 17:35












  • 3




    Possible duplicate of Use of ^ as a shell metacharacter
    – roaima
    Dec 29 '18 at 9:39






  • 1




    Trigraphs in C were not introduced because of the Teletype Model 33, they came much later. The reason for trigraphs were the ISO-646 character set, which allowed certain characters like to be replaced by national characters like äöå.
    – Johan Myréen
    Dec 29 '18 at 12:22










  • The proposed duplicate does not answer the question of how one entered these characters (more than just |) when that sort of teletype was a Unix terminal. Unfortunately this question is written as if the shell were all that one interacted with on a terminal.
    – JdeBP
    Dec 29 '18 at 17:35







3




3




Possible duplicate of Use of ^ as a shell metacharacter
– roaima
Dec 29 '18 at 9:39




Possible duplicate of Use of ^ as a shell metacharacter
– roaima
Dec 29 '18 at 9:39




1




1




Trigraphs in C were not introduced because of the Teletype Model 33, they came much later. The reason for trigraphs were the ISO-646 character set, which allowed certain characters like to be replaced by national characters like äöå.
– Johan Myréen
Dec 29 '18 at 12:22




Trigraphs in C were not introduced because of the Teletype Model 33, they came much later. The reason for trigraphs were the ISO-646 character set, which allowed certain characters like to be replaced by national characters like äöå.
– Johan Myréen
Dec 29 '18 at 12:22












The proposed duplicate does not answer the question of how one entered these characters (more than just |) when that sort of teletype was a Unix terminal. Unfortunately this question is written as if the shell were all that one interacted with on a terminal.
– JdeBP
Dec 29 '18 at 17:35




The proposed duplicate does not answer the question of how one entered these characters (more than just |) when that sort of teletype was a Unix terminal. Unfortunately this question is written as if the shell were all that one interacted with on a terminal.
– JdeBP
Dec 29 '18 at 17:35










0






active

oldest

votes











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491432%2fhow-did-bourne-shell-solve-missing-teletype-keys-problem%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491432%2fhow-did-bourne-shell-solve-missing-teletype-keys-problem%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay