[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Introduce markup-list-command table (issue 289980043 by address@hidd
From: |
dak |
Subject: |
Re: Introduce markup-list-command table (issue 289980043 by address@hidden) |
Date: |
Sun, 31 Jan 2016 14:56:37 +0000 |
https://codereview.appspot.com/289980043/diff/40001/scm/define-markup-commands.scm
File scm/define-markup-commands.scm (right):
https://codereview.appspot.com/289980043/diff/40001/scm/define-markup-commands.scm#newcode4724
scm/define-markup-commands.scm:4724: The number of columns is specifies
by @var{columns}. Each column may be aligned
On 2016/01/31 14:34:22, thomasmorley651 wrote:
On 2016/01/31 13:43:30, dak wrote:
> Where is the point in specifying the number of columns when it is
(length
> column-align)? Or am I overlooking something?
Although you're correct:
while testing, I found it comfortable to write a longer list for
column-align
than the number of columns, because I could easily change between
different
numbers of columns.
Anything wrong with
-- Scheme Procedure: list-head lst k
-- C Function: scm_list_head (lst, k)
Copy the first K elements from LST into a new list, and return it.
? It would seem easy enough to drop this into your argument for
debugging purposes and then just jiggle k.
https://codereview.appspot.com/289980043/
- Introduce markup-list-command table (issue 289980043 by address@hidden), thomasmorley65, 2016/01/30
- Re: Introduce markup-list-command table (issue 289980043 by address@hidden), dak, 2016/01/30
- Re: Introduce markup-list-command table (issue 289980043 by address@hidden), thomasmorley65, 2016/01/31
- Re: Introduce markup-list-command table (issue 289980043 by address@hidden), dak, 2016/01/31
- Re: Introduce markup-list-command table (issue 289980043 by address@hidden), thomasmorley65, 2016/01/31
- Re: Introduce markup-list-command table (issue 289980043 by address@hidden),
dak <=
- Re: Introduce markup-list-command table (issue 289980043 by address@hidden), thomasmorley65, 2016/01/31