| delorie.com/archives/browse.cgi | search |
| Date: | Wed, 1 Aug 2001 11:36:41 +0300 (IDT) |
| From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
| X-Sender: | eliz AT is |
| To: | "Mark E." <snowball3 AT bigfoot DOT com> |
| cc: | djgpp-workers AT delorie DOT com |
| Subject: | Re: termios flag to control ecma-48 |
| In-Reply-To: | <3B668BFC.2438.201017@localhost> |
| Message-ID: | <Pine.SUN.3.91.1010801113601.14932E@is> |
| MIME-Version: | 1.0 |
| Reply-To: | djgpp-workers AT delorie DOT com |
| Errors-To: | nobody AT delorie DOT com |
| X-Mailing-List: | djgpp-workers AT delorie DOT com |
| X-Unsubscribes-To: | listserv AT delorie DOT com |
On Tue, 31 Jul 2001, Mark E. wrote: > This distinction matches what cygwin and linux do. The merge of the two tty > write function has the tab character work the same between raw and cooked > mode. > > The excerpt casts doubt on the current handling of the tab char by the tty > writer. It's output the same whether in raw or cooked mode. Perhaps tab in > raw mode should just go directly to the tab stop instead of spacing its way > there? I don't see how TAB is different from the other characters and escape sequences that are interpreted as commands to the terminal. Do you see any difference?
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |