From: "Dave Korn" <dave.korn@artimi.com>
To: "'The Cygwin-Hippo Maltreating List'" <cygwin-talk@cygwin.com>
Subject: RE: paste & join
Date: Thu, 09 Jun 2005 17:57:00 -0000 [thread overview]
Message-ID: <SERRANOA7OIkUqLpHka00000391@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <Pine.GSO.4.61.0506091310360.23557@slinky.cs.nyu.edu>
----Original Message----
>From: Igor Pechtchanski
>Sent: 09 June 2005 18:12
> On Thu, 9 Jun 2005, Dave Korn wrote:
>
>> ----Original Message----
>>> From: zzapper
>>> Sent: 09 June 2005 11:18
>>
>>> Hi,
>>> I've used paste for years and it's super useful.
>>
>> Well, I've got to agree with you there. It's that whole Unix command
>> line philosophy of having loads and loads of tiny little tools, simple
>> components that perform simple tasks, and a flexible environment where
>> you can connect them up using pipes and backticks and whatever else,
>> with the idea of quickly building more complex tasks out of reusable
>> parts. You could almost have a shell-scripting RAD/gui and let people
>> drag'n'drop boxes labelled things like "grep" and "cat" and "sed" and
>> link them up using lines to represent pipes and fifos and stuff.....
>> | | | | |
>>> | W |
>>> Basically it "vertically pastes" two text files together
>>> !|E | Can't get my head around join tho, when|and where would you use
>>> this?
>> .|E| |
>> ! .E |
>> I would use it perhaps to ...... WAIT! WHAT'S THAT? OH NO! DUCK!
>> |E |
>> | E |
>> | E|
>> | E |
>> F ||E | e
>> o \ / ~ \ Z e
>>> \ @$/BOOMSPLAT#
>>> ### this is a Hi (. < SQUELCH!! > one ###
>> /%\ \_=/~\~/ \ {
>> p/ | ` &'* | / r
>> p
>>
>> No, wait a minute, it looks like I was wrong ... That was way too big
>> to be a duck!
>
> Looks like you conveniently snipped the "# this is a hippo-free zone #"
> comment from the above message...
Don't be silly, I didn't snip a thing - that falling hippo landed on it
and smashed it to bits and all the letters went flying everywhere!
> Hey, wait, it doesn't matter. You've freed that zone from a hippo just
> now, haven't you?
Look, I didn't drop _that_ one, ok? Nothing to do with me, I don't know
where it came from, maybe someone flushed it out of an airliner passing
overhead, I really don't know! Dust it all you like, you won't find my
prints on it![*]
cheers,
DaveK
[*] The fact that it's quite difficult (if not impossible)[**] to get a
clean fingerprint off of a tonne-and-a-half of wet soggy squashed hippo
entrails is neither here nor there!
[**] Probably. What, you think I might have had occasion to try this at
some time in the past[***] and actually be speaking from personal
experience?
[***] Well, ok, I might have at that. But it's still not important.[****]
[****] For suitable values of 'important'.
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2005-06-09 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 12:18 zzapper
2005-06-09 17:12 ` Dave Korn
2005-06-09 17:52 ` Igor Pechtchanski
2005-06-09 17:57 ` Dave Korn [this message]
2005-06-09 18:06 ` Igor Pechtchanski
2005-06-09 18:39 ` Dave Korn
2005-06-09 20:46 ` Igor Pechtchanski
2005-06-09 15:53 Buchbinder, Barry (NIH/NIAID)
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=SERRANOA7OIkUqLpHka00000391@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=cygwin-talk@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).