Message238390
| Author | Martin Sekera |
|---|---|
| Recipients | Martin Sekera, arigo, ezio.melotti, martin.panter, pitrou, r.david.murray |
| Date | 2015-03-18.09:21:55 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1426670516.2.0.379002119564.issue23441@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
But tab characters are rendered by the terminal into spaces. During stdout processing, when the term encounters a \t (0x09), it inserts (into the term buffer that is displayed to the user) as many spaces (0x20) as needed to move the cursor to the nearest tab-stop (setterm --tabs will display them for you). Why do we need to duplicate this inside Python? There are no copy&paste issues either, try it yourself: when you copy and paste tab-indented text from the terminal, your text will contain spaces instead of tabs (at whatever width you have your terminal tab stops configured for). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-03-18 09:21:56 | Martin Sekera | set | recipients: + Martin Sekera, arigo, pitrou, ezio.melotti, r.david.murray, martin.panter |
| 2015-03-18 09:21:56 | Martin Sekera | set | messageid: <1426670516.2.0.379002119564.issue23441@psf.upfronthosting.co.za> |
| 2015-03-18 09:21:56 | Martin Sekera | link | issue23441 messages |
| 2015-03-18 09:21:55 | Martin Sekera | create | |