Re: outputing #\Tab the C way
- From: Pascal Bourguignon <spam@xxxxxxxxxxxxxxxx>
- Date: Wed, 23 Nov 2005 10:35:32 +0100
Vladimir Zolotykh <gsmith@xxxxxxxxxxxxx> writes:
> Marco Antoniotti wrote:
>> C-q Tab :)
> I thought of that, the reason why I didn't use it is that to
> me it lacks the benefit of visibility, I mean it's less obvious what's
> meant than something expressed explicitly like \t
TAB is not a good idea. The author of make has regretted it forever.
(BTW, I'm suprized GNU make doesn't accept spaces, since they intend
to do better than the competition...)
If you want to generate some indentation, ~T is correct in generating
spaces, you shouldn't use anything else than spaces (or markup such as
<indent>...</indent>).
If you have to send a byte = 9 for a communication protocol or a
binary file, then you can just write:
(write-sequence (concatenate 'vector
(list ascii:+tab+)
(string-to-ascii-bytes "data")
(list ascii:+cr+ ascii:+lf+)) binfile)
--
"This machine is a piece of GAGH! I need dual Opteron 850
processors if I am to do battle with this code!"
.
- Follow-Ups:
- Re: outputing #\Tab the C way
- From: verec
- Re: outputing #\Tab the C way
- From: Kaz Kylheku
- Re: outputing #\Tab the C way
- References:
- outputing #\Tab the C way
- From: Vladimir Zolotykh
- Re: outputing #\Tab the C way
- From: Marco Antoniotti
- Re: outputing #\Tab the C way
- From: Vladimir Zolotykh
- outputing #\Tab the C way
- Prev by Date: Re: How to save lists containing functions to disk
- Next by Date: Re: How to save lists containing functions to disk
- Previous by thread: Re: outputing #\Tab the C way
- Next by thread: Re: outputing #\Tab the C way
- Index(es):