Greetings Eric.
Eric Schulte writes:
> I understand that this particular use case is confusing, however there
> are competing use cases and the case described here is not the most
> common.
>
> Take for example the following.
>
> #+name: data
> | header |
> ||
> | one
Rick Frankel writes:
> On 2013-11-13 09:17, Eric Schulte wrote:
>> Perhaps we should change `org-babel-default-inline-header-args' to
>> include `(:hlines "yes")'. If there is no push back on that change I'd
>> be happy to make it.
>
> I agree. It would probably make the behavior less confusing.
On 2013-11-13 09:17, Eric Schulte wrote:
Perhaps we should change `org-babel-default-inline-header-args' to
include `(:hlines "yes")'. If there is no push back on that change I'd
be happy to make it.
I agree. It would probably make the behavior less confusing.
rick
Jarmo Hurri writes:
> Rick Frankel writes:
>
> Greetings again.
>
>> Again, the solution is to globally set the :hline property to =yes=
>> instead of the default =no=, and you will get the results you want.
>
> The issue I am trying to raise here is the consistency of the system,
> not the way
Rick Frankel writes:
Greetings again.
> Again, the solution is to globally set the :hline property to =yes=
> instead of the default =no=, and you will get the results you want.
The issue I am trying to raise here is the consistency of the system,
not the way to solve this particular problem. P
On 2013-11-12 11:09, Jarmo Hurri wrote:
Rick Frankel writes:
Greetings Rick.
Note that in versions of org-mode prior to commit 6857d139 of
2013-09-28 (below), this was overridden in the setting of
`org-babel-default-header-args:emacs-lisp, so this may be why you are
seeing and "inconsistency"
Rick Frankel writes:
Greetings Rick.
> Note that in versions of org-mode prior to commit 6857d139 of
> 2013-09-28 (below), this was overridden in the setting of
> `org-babel-default-header-args:emacs-lisp, so this may be why you are
> seeing and "inconsistency" between the call line and the ema
On 2013-11-12 01:16, Jarmo Hurri wrote:
Eric Schulte writes:
There are two paces to specify header arguments in a call line, the
arguments in the [] are applied to the input-table function, *not* to
the call line, so they change the inputs. The trailing header
arguments are applied to the call
Eric Schulte writes:
Greetings Eric.
> There are two paces to specify header arguments in a call line, the
> arguments in the [] are applied to the input-table function, *not* to
> the call line, so they change the inputs. The trailing header
> arguments are applied to the call line.
So there
>
> In fact, a ":hlines no" keeps hlines in raw output; see a summarizing
> example below.
>
> From the documentation I got the impression that if hlines are pruned,
> they are pruned from the _input_:
>
There are two paces to specify header arguments in a call line, the
arguments in the [] are ap
Eric Schulte writes:
> The ":hlines yes" header argument must be set on the call line itself.
Thanks, that works!
Since this works differently for org results and raw results, can you
explain whether I understand this correctly: a ":hlines yes" at the end
of the line is needed to keep hlines i
Thorsten Jolitz writes:
> Jarmo Hurri writes:
>
While taking my first long tour in the land of Babel, I bumped into a
minor hline issue. Can someone tell me why the hline has disappeared
from the second table?
>>>
>>> Because you use CALL without arguments and argument :hlines def
Jarmo Hurri writes:
>>> While taking my first long tour in the land of Babel, I bumped into a
>>> minor hline issue. Can someone tell me why the hline has disappeared
>>> from the second table?
>>
>> Because you use CALL without arguments and argument :hlines defaults
>> to 'no'?
>
> Ok, but why
>> While taking my first long tour in the land of Babel, I bumped into a
>> minor hline issue. Can someone tell me why the hline has disappeared
>> from the second table?
>
> Because you use CALL without arguments and argument :hlines defaults
> to 'no'?
Ok, but why is there then a hline in the r
Jarmo Hurri writes:
> Greetings.
>
> While taking my first long tour in the land of Babel, I bumped into a
> minor hline issue. Can someone tell me why the hline has disappeared
> from the second table?
Because you use CALL without arguments and argument :hlines defaults to
'no'?
> # --
Greetings.
While taking my first long tour in the land of Babel, I bumped into a
minor hline issue. Can someone tell me why the hline has disappeared
from the second table?
# --
* test
#+NAME: table-one
#+BEGIN_SRC emacs-lisp
16 matches
Mail list logo
