Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion parsing bug?

Received: by 10.204.15.209 with SMTP id l17mr950957bka.6.1348419238109;
        Sun, 23 Sep 2012 09:53:58 -0700 (PDT)
X-BeenThere: pyke@googlegroups.com
Received: by 10.204.157.26 with SMTP id z26ls5235962bkw.1.gmail; Sun, 23 Sep
 2012 09:53:57 -0700 (PDT)
Received: by 10.204.146.68 with SMTP id g4mr935275bkv.4.1348419237403;
        Sun, 23 Sep 2012 09:53:57 -0700 (PDT)
Received: by 10.204.146.68 with SMTP id g4mr935274bkv.4.1348419237382;
        Sun, 23 Sep 2012 09:53:57 -0700 (PDT)
Return-Path: <dangy...@gmail.com>
Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53])
        by gmr-mx.google.com with ESMTPS id 27si457224bks.3.2012.09.23.09.53.57
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sun, 23 Sep 2012 09:53:57 -0700 (PDT)
Received-SPF: pass (google.com: domain of dangy...@gmail.com designates 209.85.214.53 as permitted sender) client-ip=209.85.214.53;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of dangy...@gmail.com designates 209.85.214.53 as permitted sender) smtp.mail=dangy...@gmail.com; dkim=pass header...@gmail.com
Received: by bkcjg15 with SMTP id jg15so997248bkc.40
        for <pyke@googlegroups.com>; Sun, 23 Sep 2012 09:53:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=8WmxVZONhzScDg/rVcBc4xuVEwS8EFmAb3KyH/219Yg=;
        b=WbfwUeGR7zDdEhWaYvPIgOKoaem2AJyhDR/bHAGqOwTD0mnXmy5Dmz/qaq9kg4zB/i
         xjBWpbUJhXAqb4YjTSGqo76JzQLAHQuNxqQtH+7Nbds5UDat/EwktZ5EOf+t2LGXgZCh
         WUZcunGcqqlhefYZlJpyewE+eu6xh2Z9S6VZDH75h6xmM08osOiKv+z0In6bkjPBD3rP
         nOZIAGbrSGmU/9eJwjlQtdlyeKSgk5doGTFW4h4Jeb++oUP7WiNCB9t6fE1Rz4/grI9o
         WrLvc01KWEwNbGUV6o22aygKhNdCMtLaR5IkS+fB+UJ9Jv/Z5JTcqSIsmNnoCtWI1Hk2
         hfYQ==
MIME-Version: 1.0
Received: by 10.204.150.200 with SMTP id z8mr2866070bkv.139.1348419237238;
 Sun, 23 Sep 2012 09:53:57 -0700 (PDT)
Received: by 10.205.40.129 with HTTP; Sun, 23 Sep 2012 09:53:57 -0700 (PDT)
In-Reply-To: <fe003c5c-28d0-4392-baec-78f62bd0c4bc@googlegroups.com>
References: <fe003c5c-28d0-4392-baec-78f62bd0c4bc@googlegroups.com>
Date: Sun, 23 Sep 2012 12:53:57 -0400
Message-ID: <CAEs=1Rg7iFRA_i0tc_o_0CZCDdRpZEqnPPGqVeknWDBTqX7...@mail.gmail.com>
Subject: Re: parsing bug?
From: Bruce Frederiksen <dangy...@gmail.com>
To: pyke@googlegroups.com
Content-Type: multipart/alternative; boundary=00151761c808a4d97a04ca615164

--00151761c808a4d97a04ca615164
Content-Type: text/plain; charset=ISO-8859-1

It would be useful if I could see an example of a BC rule that isn't
working.  The indent level (number of spaces) must be the same on all lines
(i.e., can't be 3 spaces on one line and 4 spaces on the next line).  This
would apply to both FC and BC rules.

On Sun, Sep 23, 2012 at 12:40 PM, Matteo Dell'Amico <
matteodellam...@gmail.com> wrote:

> A note: I've been playing with Pyke and I have found out that you can
> actually indent with spaces everywhere, except in BC rules, where you get a
> syntax error. In those rules, you should only indent with tabs. I don't
> know whether this is the right place to report such issues, but I hope it
> can be helpful.
>
> matteo
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyKE" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/pyke/-/ERh3O9_GzlcJ.
> To post to this group, send email to pyke@googlegroups.com.
> To unsubscribe from this group, send email to
> pyke+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/pyke?hl=en.
>

--00151761c808a4d97a04ca615164
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It would be useful if I could see an example of a BC rule that isn&#39;t wo=
rking. =A0The indent level (number of spaces) must be the same on all lines=
 (i.e., can&#39;t be 3 spaces on one line and 4 spaces on the next line). =
=A0This would apply to both FC and BC rules.<br>
<br><div class=3D"gmail_quote">On Sun, Sep 23, 2012 at 12:40 PM, Matteo Del=
l&#39;Amico <span dir=3D"ltr">&lt;<a href=3D"mailto:matteodellam...@gmail.c=
om" target=3D"_blank">matteodellam...@gmail.com</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">
A note: I&#39;ve been playing with Pyke and I have found out that you can a=
ctually indent with spaces everywhere, except in BC rules, where you get a =
syntax error. In those rules, you should only indent with tabs. I don&#39;t=
 know whether this is the right place to report such issues, but I hope it =
can be helpful.<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>matteo<br>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;PyKE&quot; group.<br>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msg/pyke/-/ERh3O9_GzlcJ" target=3D"_blank">https://groups.google.com/d=
/msg/pyke/-/ERh3O9_GzlcJ</a>.<br>=20
To post to this group, send email to <a href=3D"mailto:p...@googlegroups.co=
m" target=3D"_blank">pyke@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:pyke%2Bunsu=
bscribe@googlegroups.com" target=3D"_blank">pyke+unsubscr...@googlegroups.c=
om</a>.<br>

For more options, visit this group at <a href=3D"http://groups.google.com/g=
roup/pyke?hl=3Den" target=3D"_blank">http://groups.google.com/group/pyke?hl=
=3Den</a>.<br>


</font></span></blockquote></div><br>

--00151761c808a4d97a04ca615164--