From: Will Yardley <william@hq.newdream.net>
To: zsh-users@sunsite.dk
Subject: Re: $mailpath and Maildir
Date: Mon, 4 Feb 2002 23:08:42 -0800 [thread overview]
Message-ID: <20020205070842.GA29866@hq.newdream.net> (raw)
In-Reply-To: <1012892557.8896.3.camel@jo.cool.net>
Joakim Ryden wrote:
> this "works for me[TM]":
>
> export MAILPATH="$HOME/Maildir?You have new mail in
> \$_.:$HOME/Maildir/.maildir2?You have new mail in
> \$_.:$HOME/Maildir/.maildir3?You have new mail in
> \$_.:$HOME/Maildir/.maildir4?You have new mail in
> \$_.:$HOME/Maildir/.maildir5?You have new mail in
> \$_.:$HOME/Maildir/.maildir6?You have new mail in \$_."
d'oh.... just needed to escape the "$". you may all give me 50 lashes
with a wet noodle now.
w
next prev parent reply other threads:[~2002-02-05 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 6:40 Will Yardley
2002-02-05 7:02 ` Joakim Ryden
2002-02-05 7:08 ` Will Yardley [this message]
2002-02-05 9:01 ` Joakim Ryden
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=20020205070842.GA29866@hq.newdream.net \
--to=william@hq.newdream.net \
--cc=zsh-users@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).