New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

{ke ko'a ce ko'e ke'e ce ko'i} doesnt parse. #118

Open
lagleki opened this Issue Jun 26, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@lagleki
Collaborator

lagleki commented Jun 26, 2015

No description provided.

@lagleki lagleki added the bug label Jun 26, 2015

@xorxes

This comment has been minimized.

xorxes commented Jun 26, 2015

That's inherited from the LALR(1) limitations of YACC. The same applies to
"ke broda gi'e brode ke'e gi'a brodi". It shouldn't be hard to fix with PEG.

On Fri, Jun 26, 2015 at 6:02 AM, Gleki Arxokuna notifications@github.com
wrote:


Reply to this email directly or view it on GitHub
#118.

guskant added a commit to guskant/gerna_cipra that referenced this issue Jun 27, 2015

guskant added a commit to guskant/gerna_cipra that referenced this issue Jun 27, 2015

guskant added a commit to guskant/gerna_cipra that referenced this issue Jun 27, 2015

guskant added a commit to guskant/gerna_cipra that referenced this issue Jun 27, 2015

guskant added a commit to guskant/gerna_cipra that referenced this issue Jun 27, 2015

guskant added a commit to guskant/gerna_cipra that referenced this issue Jun 27, 2015

@Spheniscine

This comment has been minimized.

Spheniscine commented Jul 20, 2015

This issue has increased in importance as {ke po'o lo broda [ke'e] cu brode} is increasingly popular as a way to front {po'o}/{ji'a} and avoiding having to close a sumti just to add them.

@lagleki

This comment has been minimized.

Collaborator

lagleki commented Jul 20, 2015

looks like commits by guskant referenced above fix both issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment