9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] rc: token buffer too short
Date: Tue, 11 Dec 2007 14:46:34 -0500	[thread overview]
Message-ID: <74D6B736-B261-44EC-B2AF-86ACC35E971A@mac.com> (raw)
In-Reply-To: <df49a7370712110532v236cf4bbx87678b4d67dc674c@mail.gmail.com>

Not in this case, no. The format of awk is

	awk 'program' files
	awk -f prgm files

What I could do instead is

	u=/tmp/$0$pid$apid$0
	cat > $u <<\END
	program
	END
	awk -f $u $*
	rm $u

but I'd rather not go that way to avoid possible collisions.

Here's another problem. The error check function cats to [1=2].  
However, instead of going to standard output, it makes a file [1=2]  
and writes the message there. How do I fix this?

On Dec 11, 2007, at 8:32 AM, roger peppe wrote:

> a reason to use here files? :-)
>
> On Dec 1, 2007 7:09 PM, Martin Neubauer <m.ne@gmx.net> wrote:
>> Apparrently in quoted strings each character (rune, actually)  
>> constitutes
>> one token. The lexical scanner only holds NTOK (==8192) tokens at  
>> a time and
>> sam and wc convince me you have a 8555 byte string you pass to  
>> awk. You
>> should probably put the awk stuff into a separate file eg.awk and  
>> just do
>> `awk -f eg.awk $*' in eg (cf. chem(1) ). You might have to fiddle  
>> with where
>> you put things, but that seems to be the easiest way out.
>>
>>         Martin
>>
>>
>> * Pietro Gagliardi (pietro10@mac.com) wrote:
>>> Run /n/sources/contrib/pietro/eg (a work-in-progress troff
>>> preprocessor for graphs of equations). You get the error described
>>> above on a line that contains simply "else". What happened?
>>


  reply	other threads:[~2007-12-11 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-01 17:43 Pietro Gagliardi
2007-12-01 19:09 ` Martin Neubauer
2007-12-11 13:32   ` roger peppe
2007-12-11 19:46     ` Pietro Gagliardi [this message]
2007-12-12 10:14       ` Douglas A. Gwyn
2007-12-12 11:04       ` roger peppe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=74D6B736-B261-44EC-B2AF-86ACC35E971A@mac.com \
    --to=pietro10@mac.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).