[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 4191: add an "\or" markup command (issue 169290045 by address@
From: |
dak |
Subject: |
Re: Issue 4191: add an "\or" markup command (issue 169290045 by address@hidden) |
Date: |
Wed, 12 Nov 2014 06:34:46 +0000 |
On 2014/11/12 02:21:41, Dan Eble wrote:
On 2014/11/11 09:29:05, dak wrote:
> Not every markup list is a Scheme list of markups.
Thanks for pointing that out. I assume you mean to imply that I
should (a) make
the command work with other kinds of markup list, rather than (b)
change the
predicate to identify just the things the command currently works
with. I will
work on (a) unless I hear otherwise.
(b) wouldn't work anyway. Unlike music function arguments are now,
markup command arguments types are identified by the function address of
their predicate. Make a new predicate, and no markup lists will get
accepted.
https://codereview.appspot.com/169290045/
- Re: Issue 4191: add an "\or" markup command (issue 169290045 by address@hidden), dak, 2014/11/11
- Re: Issue 4191: add an "\or" markup command (issue 169290045 by address@hidden), nine . fierce . ballads, 2014/11/11
- Re: Issue 4191: add an "\or" markup command (issue 169290045 by address@hidden),
dak <=
- Re: Issue 4191: add an "\or" markup command (issue 169290045 by address@hidden), dak, 2014/11/12
- Re: Issue 4191: add an "\or" markup command (issue 169290045 by address@hidden), dak, 2014/11/12
- Re: Issue 4191: add an "\or" markup command (issue 169290045 by address@hidden), nine . fierce . ballads, 2014/11/12
- Re: Issue 4191: add an "\or" markup command (issue 169290045 by address@hidden), dak, 2014/11/12
- Re: Issue 4191: add an "\or" markup command (issue 169290045 by address@hidden), dak, 2014/11/13