9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] upas aliases
Date: Sun, 27 Sep 2009 21:25:24 -0700	[thread overview]
Message-ID: <dd6fe68a0909272125n6b907dd0g459c4a587f66b372@mail.gmail.com> (raw)
In-Reply-To: <47ff785949f474506048701186b50f22@ladd.quanstro.net>

You switched examples in your mail.
Given an aliases file like

a1: local!a2
a3: local!a1

and a rewrite file like

[^!@.]+			translate	"/bin/upas/aliasmail '&'"
local!(.*)		>>		/mail/box/\1/mbox

I expect an attempt to mail a1 to deliver to /mail/box/a2/mbox
or else fail if that file does not exist.  Similarly,
I expect an attempt to mail a3 to deliver to /mail/box/a1/mbox
or else fail if that file does not exist.
"Attempt to mail" means any attempt at mail.

Local is *not* analogous to builtin in rc.
Rc's builtin has special meaning to rc.
Local has no special meaning at all to upas;
the rules apply to local!a1 the same as they
do to any other string; there's just a rule that
handles local!(.*).

Because you switched names halfway through
you didn't say what was working and what was not.
In terms of the above two lines, what is it that
is behaving a different way than you expect?

Are you sure that your own $mail/aliases
file is not also in play when your run plain "mail"
as opposed to "upas/send -x"?

Russ


  reply	other threads:[~2009-09-28  4:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28  4:00 erik quanstrom
2009-09-28  4:25 ` Russ Cox [this message]
     [not found] <<dd6fe68a0909272125n6b907dd0g459c4a587f66b372@mail.gmail.com>
2009-09-28  5:07 ` erik quanstrom
2009-09-28  5:28   ` Russ Cox
     [not found] <<dd6fe68a0909272228y7e141beavf1a3fc4fb02f7fbd@mail.gmail.com>
2009-09-28  5:42 ` erik quanstrom
2009-09-28  5:54   ` Russ Cox

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=dd6fe68a0909272125n6b907dd0g459c4a587f66b372@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=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).