Ihor Radchenko <[email protected]> writes:
>> It seems to me that the names ':strip-colnames' and ':detach-colnames'
>> are also potentially misleading, because they only explicitly state that
>> column names will be removed, not that they will be re-attached. If
>> we're looking for a header name that makes more intuitive sense of the
>> 'yes' and 'no' values, I'd maybe propose ':has-colnames'.
>
> :has-colnames sounds good.
I am looking at this further, and there is also :hlines, which
implementing the same idea about manipulating input.
But renaming :hlines to :has-hlines makes little sense.
Maybe :hlines -> :strip-hlines; :colnames -> :has-colnames; :rownames ->
:has-rownames. But looking at this triplet of arguments, that again
feels not right.
Naming is hard.
In-between each table row or below the table headings, sometimes
results have horizontal lines, which are also known as "hlines".
The ‘hlines’ argument with the default ‘no’ value strips such lines
from the input table. For most code, this is desirable, or else
those ‘hline’ symbols raise unbound variable errors. A ‘yes’
accepts such lines, as demonstrated in the following example.
#+NAME: many-cols
| a | b | c |
|---+---+---|
| d | e | f |
|---+---+---|
| g | h | i |
#+NAME: no-hline
#+BEGIN_SRC python :var tab=many-cols :hlines no
return tab
#+END_SRC
#+RESULTS: no-hline
| a | b | c |
| d | e | f |
| g | h | i |
#+NAME: hlines
#+BEGIN_SRC python :var tab=many-cols :hlines yes
return tab
#+END_SRC
#+RESULTS: hlines
| a | b | c |
|---+---+---|
| d | e | f |
|---+---+---|
| g | h | i |
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
