You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- 2And they're ancient relics (really, shells/text applications are still interacting over a device that emulates a tele-type writer over a serial line like they worked 40 years ago...) We still need them because there is no replacement :-(nos– nos2011-09-20 17:55:22 +00:00Commented Sep 20, 2011 at 17:55
- Well, if you consider the terminal, I don't think you need much more than a stream of letters comming and going...Diego Sevilla– Diego Sevilla2011-09-20 17:59:28 +00:00Commented Sep 20, 2011 at 17:59
- 5@Diego Sevilla The original unix inventor did away with tty/ptys in Plan 9 , and there a terminal pretty much does just use a stream of in/out data. But in *nix, the ttys are still around and used by consoles and terminal emulators to e.g. control terminal size, flow control, line buffering, special key events, and other stuff.nos– nos2011-09-20 18:06:21 +00:00Commented Sep 20, 2011 at 18:06
- 7@nos: It turns out they're not the ancient relics we're lead to believe. Trying to do without them in Windows is rather painful in the end. The use of powershell remoting is hampered by one thing: interactive console programs don't work and can't be fixed to work right. There is no possibility of a reasonable text editor like either DOS EDIT or vi.Joshua– Joshua2015-12-15 17:43:30 +00:00Commented Dec 15, 2015 at 17:43
- 2@Joshua Another evidence to the contrary is the original designers of Unix created the Plan 9 OS, where they completely did away with ttys, yet they achieved remoting in that manner (and much more) just fine.nos– nos2015-12-15 19:23:27 +00:00Commented Dec 15, 2015 at 19:23
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. shell-script), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you