Best of Jokes Current Jokes RHF Home Search Sponsor RHF?
Fun Stuff & Jokes
Previous | RHF Joke Archives | Next

Irish/Mexican cuisine? MacBurrito! (Pete Gontier)
(smirk, computers, long)

Following is the documentation for a computer program which lives at
Adobe (PostScript/fonts/Acrobat/Photoshop/Illustrator) in Mountain
View, California. I got permission from the author to re-post it for

Some background: La Costena is a Mexican restaurant local to Adobe.
Everything is made to order, and the cooks follow you down a sort of
burrito assembly line in order to customize your meal.  Not
surprisingly, the place is very popular, and there are often long
lines. Mr. Thompson has thus enlisted the aid of technology to avoid
wasting too much time in queue.


From Wed Aug 18 07:05:38 1993
Message-Id: <>
To: (Pete Gontier)
Subject: Re: Burritos 
Date: Wed, 18 Aug 93 07:04:48 MDT

Here you go.  You may want to add some editorial notes for those
unfortunate to live outside the Bay area.  By the way, this is a real

- Ross


Tired of standing in line at La Costena?  This file documents an
automatic facility for sending a fax to La Costena that orders 1 or
more burritos, quesadillas, tacos, and whatever.  The command will
compose the fax, and send it to your favorite PostScript fax printer,
for direct transmission to La Costena, and no paper at this end will
be generated.  Then, when you get there, your food will be waiting.
No worries.

To use this, you will want to add the following lines to your .cshrc

setenv BURRITOPRINTER = <printer>
alias burrito /user/thompson/public/burrito<mach>

where <mach> is dec, sun, or sparc, as appropriate.  Requests to
support other machine types will be greeted with enthusiasm if the
following conditions are met:
 1) I can get the code to compile with a minimum of effort.
	(I expect no difficulties, but you never know).
 2) I am provided with the name of a machine on which to do the build.

<printer> should be the name of a PostScript level 2 printer that
supports fax and is connected to an external phone line. I use
radiant, which is located in building E.

You will also probably want to create a .costenarc file, to define
your burrito macros in.  The one in /user/thompson/.costenarc is
designed to stand as an example that you can use.  Feel free to copy,
modify, whatever.  I think the syntax should be pretty
straightforward, if you understand how to describe a burrito.

In keeping with long standing Unix tradition, the syntax for
specifying burritos is somewhat obscure. Here is an attempt at
explanation, with some examples at the end.  For a better
understanding, the energetic reader will attempt to thoroughly
comprehend the contents of my .costenarc file.

burrito [-n "name"] [-t <time>] [-p phone#] [-9] [-d] [-x] [FoodSpec [...]]

    -n  specify the name at the top of the order blank.
	   This should be the name of the person who will pick
	   up the order.  Default is current user, as defined in
    -t  specify the time at which you will pick up the order.
    	   time may be absolute 24 hour time or +delta. Default is +1:00.
    	   Note that La Costena specifies a 20 minute on small orders
	   and 60 minute on large orders minimum notification time.
    -p  specify callback number in case La Costena has questions.
	   default is as found in /usr/local/adobe/phones/adobe.phones.
	   If your phone number is not specified, and burrito can't
	   figure it out by looking in adobe.phones, an error will result,
	   and the order will not be transmitted.
	   syntaxes for phone numbers:
		    entry		interpretation
		(408)123-4567		(408)123-4567
		123-4567		(415)123-4567
		x4567			(415)962-4567
	    If you are entering the phone number on the command line
	    (instead of using a macro) please note that the ()'s need
	    to be escaped: \\(408\\)....
    -9	dial "9" before dialing the La Costena number.
  The following two options are installed primarily to help me debug
  the code.  There is probably no reason for general use of these options,
  unless you have some perverse desire to see the guts of this thing
  in operation.
    -d  debug: print the file locally rather than faxing it.
    -x  xmit off: don't run the shell script at all.  PostScript file
	will be left in ~/

Up to six FoodSpecs can be specified:

<type> ::= [b|t|m|q|T]
    (burrito, taco, mexico city, quesadilla, Taqitaco)
    +g  gucamole
    +c  cheddar
    +cc cotija
    +cl cilantro
    +cm monterey
    +i"note" special instructions (e.g. black beans, no rice, etc.)
	NOTE: the "s need to be escaped if the shell sees them:
    +j  whole jalepenos
    +jf fresh jalapenos
    +js sliced jalapenos
    +n:<i> <i> copies of this food item. (default = 1)
    +o  olives
    +s  medium salsa
    +sc sour cream
    +sf fire salsa
    +sh hot salsa
    +sm mild salsa
    +sv salsa verde
    +t  tomato
    +v:ca carne azada
    +v:cc chile colorado
    +v:cv chile verde
    +v:f  fiesta
    +v:l  lengua  (beef tongue)
    +v:m  mole    (chicken)
    +v:p  pastor
    +v:pb pollo borracho
    +v:rb rice and beans (default)
    +v:v  vegetarian
    +z:l  large
    +z:r  regular (default)
    +z:c  chico (small)

    -[option] cancels option.  Not valid for ":" options or +i.  
       This is useful for modifying burrito macros specified in
        .costenarc file.


burrito -time +:30 b+g+cc+jf+jf+sf+sc-sc+i"Black Beans"+n:2/Ross \
   b+v:cc+g+cm+sc+i"no rice"/Kathie

logged in user will pick up an order in 30 minutes.
  Ross wants two rice and bean (default) burritos with
    fresh jalepenos (double)
    fire salsa
    no sour cream (cancelled)
    Black beans (comment)
  Kathie wants a Chile Colorado burrito with
    montery cheese
    sour cream
    no rice (comment)

You should keep your +i comments short, because there isn't much space on
the form for them, and the space is not used particularly well by my
PostScript program.  "Black beans, no rice" is about as long a
message as it can handle.



   There's all kinds of ways to break this thing.  The lines in your
\.costenarc file should be less than 1000 characters, or the stack will
get trashed.  The PostScript program does not make particularly good
use of the "Comments" section of the form (controlled by the "+i"
switch), and doesn't detect when it is writing things off the side of
the page.  I have no idea what will happen if the disk is full when
burrito tries to write the file, or if it can't open it
because the directory is protected, or whatever.  But if you are
reasonable in your expectations of the program, and don't try to break
it, I think you'll find that it's adequate.  For bug reports, see my
comments below about future enhancements.

   This is the kind of thing that everybody will have suggestions on
how to improve.  I will duly record every feature enhancement request,
but I can't promise that I'll do any more than that.  I have no
intention whatsoever, for example, of writing a Graphical User
Interface for this thing, even though so many people think that it's a
natural.  (However, see below.)  As I have said (many times) before
about this: "When I'm done with the program, you are more than welcome
to add any features that you wish."  Well, I'm (essentially) done.
Anyone who wants the source, it's in /user/thompson/public/burrito.c.
Gombata Kodesai.

    Steve Hawley has written two programs that make use of burrito
technology.  I don't know anything about them except that they exist,
but I thought I would mention them for what it's worth.  As far as I
know, they were both done as intellectual exercises, and are not
necessarily supported.
    - xburrito is a GUI overlay to the burrito program, which makes
	use of the motif library to animate the La Costena order form.
	This has been successfully run on DecStations, Sparcs, and
	perhaps other platforms.
    - macburrito is a gooey which runs on Macs.  It has the look and
	feel of a real burrito: The user interface involves throwing
	toppings onto a tortilla.

(From the "Rest" of RHF)

Previous | RHF Joke Archives | Next

Best of Jokes | Current Jokes | RHF Home | Search