Talk:Terminal control/Preserve screen: Difference between revisions
Content added Content deleted
m (indentation for readability) |
(So this draft task doesn't have any successful impls at all?) |
||
| Line 8: | Line 8: | ||
:[[User:Markhobley|Markhobley]] 19:23, 21 March 2011 (UTC) |
:[[User:Markhobley|Markhobley]] 19:23, 21 March 2011 (UTC) |
||
:: So the Javascript code (which preserves the browser state, not a terminal) is way off? It's rare for Javascript engines to be connected to a real terminal in any useful way. –[[User:Dkf|Donal Fellows]] 22:03, 2 May 2011 (UTC) |
|||
Revision as of 22:03, 2 May 2011
Does "screen" include character decorations, fonts, kerning, and so on, or not?
These terminal control tasks have long bothered me, because of the heavy ambiguity in their descriptions, and when we do not even have a working example my imagination runs wild. --Rdm 14:53, 21 March 2011 (UTC)
- There is no requirement to change the font or kerning in this task, however character decorations and attributes are expected to be preserved. If the task implementer decides to change the font or kerning during the display of the temporary screen, then these settings need to be restored prior to exit.
- Working examples of applications that preserve the screen are the unix less command and sidekick for msdos.
- Markhobley 19:23, 21 March 2011 (UTC)
- So the Javascript code (which preserves the browser state, not a terminal) is way off? It's rare for Javascript engines to be connected to a real terminal in any useful way. –Donal Fellows 22:03, 2 May 2011 (UTC)