From: "Ozan S. Yigit" <oz@sis.yorku.ca>
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: huh?
Date: Wed, 10 Mar 1993 12:02:45 -0500 [thread overview]
Message-ID: <9303101702.AA07530@sis.yorku.ca> (raw)
In-Reply-To: Your message of "Wed, 10 Mar 93 08:53:29 PST." <9303101653.AA04978@utopia.mv.us.adobe.com>
> i believe the difference is that ``x'' without a pattern
> immediately following it uses an implicit /^.*\n/
Ah, now I found it in page 8 of the tutorial. Grumble, all
this time, I have been using it without this shorthand. It
goes to show that one must always read Bell Labs tutorials
with care. ;-)
oz
---
We only know... what we know, and | email: oz@sis.yorku.ca
that is very little. --Dan Rather | ph:416 736 2100 x33976
next prev parent reply other threads:[~1993-03-10 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-03-10 16:53 huh? Paul Haahr
1993-03-10 17:02 ` Ozan S. Yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-03-16 19:57 huh? Ozan S. Yigit
1993-03-10 19:44 huh? Scott Schwartz
1993-03-10 16:39 huh? Ozan Yigit
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=9303101702.AA07530@sis.yorku.ca \
--to=oz@sis.yorku.ca \
--cc=sam-fans@hawkwind.utcs.toronto.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).