9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Simon <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] equality sign in Rc
Date: Sat,  6 May 2017 14:20:30 +0100	[thread overview]
Message-ID: <3F739A40-44AE-4E2B-A7CF-7C97F9BC0762@quintile.net> (raw)
In-Reply-To: <C5216A86-3139-4B1E-8C6A-F46DCC7C019A@gmail.com>


i would have expected this to work:

cc '-DFOO=bar' file.c

-Steve

> On 6 May 2017, at 08:43, Sean Callanan <l337.h4x0r@gmail.com> wrote:
> 
> I can't speak for dexen, but I would love to be able to run
> 
> cc -DFOO=bar file.c
> 
> or similar commands with button 2 in Acme.  What I get instead is
> 
> rc: line 2: token '=': syntax error
> 
> Sean
> 
> iPadから送信
> 
> 2017/05/05 18:53、tty0@teknik.io のメッセージ:
> 
>> May 1, 2017 2:30 PM, "dexen deVries" <dexen.devries@gmail.com> wrote:
>> 
>>> does anybody have a version of Rc that allows unquoted equality sign?
>>> 
>>> having to quote the character get a bit annoying on POSIX systems (plan9port)
>> 
>> I don't, but can you explain in detail what you are doing that causes an issue?
>> 
>> 




  reply	other threads:[~2017-05-06 13:20 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01 19:27 dexen deVries
2017-05-06  1:53 ` tty0
2017-05-06  7:43   ` Sean Callanan
2017-05-06 13:20     ` Steve Simon [this message]
2017-05-06 19:09       ` Sean Callanan
2017-05-06 20:14     ` Nick Owens
2017-05-13 12:36 trebol
2017-05-13 13:42 ` Charles Forsyth
2017-05-13 14:21   ` trebol
2017-05-13 16:53     ` Charles Forsyth
2017-05-13 22:41       ` Bruce Ellis
2017-05-14  9:56 ` Charles Forsyth
2017-05-14 15:36   ` trebol
2017-05-14 22:31     ` erik quanstrom
2017-05-15  8:58       ` Charles Forsyth
2017-05-15 11:48         ` trebol
2017-05-15 11:54           ` Charles Forsyth
2017-05-15 11:55             ` Charles Forsyth
2017-05-15 11:56             ` Charles Forsyth
2017-05-15 15:37               ` Erik Quanstrom
2017-05-15 15:42                 ` Charles Forsyth
2017-05-15 15:54                   ` Erik Quanstrom
2017-05-15 15:59                     ` Charles Forsyth
2017-05-15 16:30                       ` Giacomo Tesio
2017-05-15 16:36                         ` Charles Forsyth
2017-05-15 18:25                           ` Giacomo Tesio
2017-05-15 16:43                         ` trebol
2017-05-15 18:33                           ` trebol
2017-05-15 21:06                             ` Charles Forsyth
2017-05-15 21:48                               ` trebol
2017-05-15 23:38                                 ` trebol
2017-05-15 23:59                                   ` trebol
2017-05-14 22:36     ` trebol
2017-05-14 22:38 ` erik quanstrom
2017-05-15 11:35   ` hiro
2017-05-15 11:45     ` trebol
2017-05-15 16:44 trebol
2017-05-15 21:02 ` Charles Forsyth
2017-05-16  9:24 ` Charles Forsyth
2017-05-16 15:59   ` Erik Quanstrom
2017-05-16 17:07     ` Giacomo Tesio
2017-05-15 19:32 sl
2017-05-15 20:15 ` Erik Quanstrom
2017-05-16 17:11 ` Kurt H Maier
2017-05-16 18:27   ` hiro
2017-05-16 18:40   ` Giacomo

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=3F739A40-44AE-4E2B-A7CF-7C97F9BC0762@quintile.net \
    --to=steve@quintile.net \
    --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).