[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:40:45 +0000 |
https://codereview.appspot.com/169290045/diff/20001/scm/define-markup-commands.scm
File scm/define-markup-commands.scm (right):
https://codereview.appspot.com/169290045/diff/20001/scm/define-markup-commands.scm#newcode1183
scm/define-markup-commands.scm:1183: (interpret-markup-list layout props
l))))
I'd not do all of l here. Try just (list (car l)) instead. That way,
you don't evaluate all the rest of l unnecessarily.
Either that, or evaluate anything anyway. Much simpler, but probably
not in the spirit of "or".
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, 2014/11/12
- 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), 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