From: David Hogan dhog@plan9.cs.su.oz.au
Subject: no need for cd
Date: Thu, 9 Mar 1995 02:30:59 -0500 [thread overview]
Message-ID: <19950309073059.5hwt__Ftn-LgErgj8TsLbuenMpqkZ_QPW7X3kwQeo8Q@z> (raw)
>a comment on your message: there is no word 'prepend'; use 'prefix'.
But it's in the Jargon File! :-) :-) :-)
:prepend: /pree`pend'/ [by analogy with `append'] vt. To
prefix. As with `append' (but not `prefix' or `suffix' as a
verb), the direct object is always the thing being added and not
the original word (or character string, or whatever). "If you
prepend a semicolon to the line, the translation routine will pass
it through unaltered."
next reply other threads:[~1995-03-09 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-03-09 7:30 David [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-03-11 1:06 serge
1995-03-09 8:18 David
1995-03-09 4:49 rob
1995-03-09 0:09 Scott
1995-03-08 21:27 serge
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=19950309073059.5hwt__Ftn-LgErgj8TsLbuenMpqkZ_QPW7X3kwQeo8Q@z \
--to=9fans@9fans.net \
/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).