| To: | "Geoff Clare" <gwc@xxxxxxxxxxxxx>, <austin-group-l@xxxxxxxxxxxxx> |
|---|---|
| Subject: | RE: XSH ERN 217 |
| From: | "Schwarz, Konrad" <konrad.schwarz@xxxxxxxxxxx> |
| Date: | Fri, 20 Jul 2007 14:46:26 +0200 |
| References: | <20070720114439.GA26686@xxxxxx> |
| Thread-index: | AcfKxod0mGgyYQ0/Tuu9RK5Sf0/FowABGmTw |
| Thread-topic: | XSH ERN 217 |
> -----Original Message----- > From: Geoff Clare [mailto:gwc@xxxxxx] > Sent: Friday, July 20, 2007 1:45 PM > To: austin-group-l@xxxxxx > Subject: XSH ERN 217 > > In yesterday's teleconference we agreed to resolve XSH ERN > 217 by adding a special constant to be used with tcsetattr() > to initialise a terminal to conforming settings after "first open". The BSD 2.9.1 intro(3J) man page (on http://www.freebsd.org/cgi/man.cgi?query=intro&apropos=0&sektion=3&manpa th=2.9.1+BSD&format=html) describes the protocol required to be implemented by processes that wish to modify the terminal state in a job-controlled environment. Although the system interfaces have changed, it could be that the underlying protocol is still relevant. In particular, processes are always required to save the original terminal state before changing anything (restoring the original state when being put in the background and restoring the process's state when being put into the foreground). Would the requirement that processes use a read/modify/write protocol to update terminal settings make XSH ERN 217 obsolete? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | XSH ERN 217, Geoff Clare |
|---|---|
| Next by Date: | fmemopen questions, Eric Blake |
| Previous by Thread: | XSH ERN 217, Geoff Clare |
| Next by Thread: | Re: XSH ERN 217, Geoff Clare |
| Indexes: | [Date] [Thread] [All Lists] |