Ihor Radchenko writes:
>> I suggest to keep current defaults. Because I have lot of Org files, if
>> changed, I have to do lot of
>> work to adopt files and might get wrong. It's very important.
>
> Org mode does not distinguish the _meaning_ of all keywords regardless
> of their case. Includin
> I suggest to keep current defaults. Because I have lot of Org files, if
> changed, I have to do lot of
> work to adopt files and might get wrong. It's very important.
Org mode does not distinguish the _meaning_ of all keywords regardless
of their case. Including src blocks and results. If it is
Timothy writes:
> Hi Christopher,
>
>>> Is there a good reason for this?
>>>
>>> At a glance, I’d personally be tempted to make the use case insensitive, and
>>> only use `org-babel-results-keyword’ when inserting, or remove it all
>>> together.
>>
>> Me too, I hope it can be case-insensitive,
Hi Christopher,
>> Is there a good reason for this?
>>
>> At a glance, I’d personally be tempted to make the use case insensitive, and
>> only use `org-babel-results-keyword’ when inserting, or remove it all
>> together.
>
> Me too, I hope it can be case-insensitive, if org-mode internal has alre
Hi Ihor,
>> Hmm. Upon inspection I see that some uses of `org-babel-results-keyword’ are
>> indeed case-sensitive. This comes as a surprise to me, as I thought that
>> /all/
>> keywords were parsed in a case-insensitive manner.
>>
>> Is there a good reason for this?
>
> Could you elaborate on thi
Timothy writes:
> Hi Christopher,
>
>> I suggest to keep current defaults. Because I have lot of Org files, if
>> changed, I have to do lot of
>> work to adopt files and might get wrong. It’s very important.
>
> Hmm. Upon inspection I see that some uses of `org-babel-results-keyword' are
> inde
Timothy writes:
> Hmm. Upon inspection I see that some uses of `org-babel-results-keyword' are
> indeed case-sensitive. This comes as a surprise to me, as I thought that /all/
> keywords were parsed in a case-insensitive manner.
>
> Is there a good reason for this?
Could you elaborate on this? I
Hi Christopher,
> I suggest to keep current defaults. Because I have lot of Org files, if
> changed, I have to do lot of
> work to adopt files and might get wrong. It’s very important.
Hmm. Upon inspection I see that some uses of `org-babel-results-keyword' are
indeed case-sensitive. This comes
I suggest to keep current defaults. Because I have lot of Org files, if
changed, I have to do lot of
work to adopt files and might get wrong. It's very important.
--
[ stardiviner ]
I try to make every word tell the meaning that I want to express.
Blog: https://stardiviner.github
Rudolf Adamkovič writes:
> The results so far:
>
> - For inconsistent defaults:
> Colin
>
> - For consistent defaults:
> Rudy (me), Tim, Timothy, Kaushal
>
> - Unknown:
> Gyro
>
> Four times more people would like to see consistent defaults so far.
> Does that count as overwhelming support?
> Rudolf Adamkovič writes:
> Ihor Radchenko writes:
>> So, unless there is overwhelming support for changing uppercase
>> defaults into lowercase and a thorough patch, I am inclined
>> towards preserving the existing behaviour.
> The results so far:
> - For inconsis
On 11 January 2022, Rudolf Adamkovič wrote:
Four times more people would like to see consistent defaults so far.
Does that count as overwhelming support? :)
I'm for consistent defaults too, and #+RESULTS looks wrong to me, but I suspect
I'm one of many who isn't able to provide patches, doesn
Ihor Radchenko writes:
> So, unless there is overwhelming support for changing uppercase
> defaults into lowercase and a thorough patch, I am inclined towards
> preserving the existing behaviour.
The results so far:
- For inconsistent defaults:
Colin
- For consistent defaults:
Rudy (me), T
Hi Ihor,
> For some more context, other functions are not really consistent about
> uppercase/lowercase:
> - `org-insert-structure-template' lowercase
> - `org-insert-drawer' uppercase
> - `org-insert-property-drawer' uppercase
> - `org-babel-exp-code-template' defaults to uppercase
> - `org-cloc
> Ihor Radchenko writes:
> Colin Baxter 😺 writes:
>> What is the point of changing a default? Users can change to
>> whatever they like, but a default is a default - i.e. remains
>> fixed. Why a particular default arose belongs to peculiarities of
>> history. Do people re
Colin Baxter 😺 writes:
> What is the point of changing a default? Users can change to whatever
> they like, but a default is a default - i.e. remains fixed. Why a
> particular default arose belongs to peculiarities of history. Do people
> really want to revisit this year after year? The value of
> Timothy writes:
> Hi Gyro,
>> Consider Emerson’s quote:
>>
>> “A foolish consistency is the hobgoblin of little minds, adored
>> by little statesmen and philosophers and divines. With
>> consistency a great soul has simply nothing to do.”
> I think applying a
On Mon, Jan 10, 2022 at 8:35 AM Timothy wrote:
>
> FWIW, I think it would be good to be internally consistent. #+RESULTS is
> currently one of the few keywords inserted in upper case. Unless there’s a
> good
> reason to distinguish it from other keywords (perhaps an argument could be
> made
> th
Hi Gyro,
> Consider Emerson’s quote:
>
> “A foolish consistency is the hobgoblin of little minds, adored by little
> statesmen and philosophers and divines. With consistency a great soul has
> simply
> nothing to do.”
I think applying a quote about how societal expectations and norms can limit t
On 2022-01-09 06:21 PM, Rudolf Adamkovič wrote:
Thank you for providing me with such a clear explanation! To make my
point clear, I do not care about whether Org uses upper case or lower
case keywords, but I do care about consistency. Specifically, I think
Emacs should not make new users fiddle
Tim Cross writes:
> The point is, the begin v BEGIN issue is to some extent bordering on
> becoming a religious argument and one which is unlikely to gain
> consensus. While personally I agree with your point and for
> consistency, I think the default should be lower case, it really
> doesn't mat
Rudolf Adamkovič writes:
> If I remember well, Org decided to suggest with lowercase keywords (and
> use uppercase keywords in the manual, for some reason). Then, we should
> change "org-babel-results-keyword" from "RESULTS" to "results".
>
> (1) Example #1
>
> #+begin_src R :results verbatim
Colin Baxter 😺 writes:
> Change it for yourself.
I did.
> Please don't change the default.
Why?
--
"'Contrariwise,' continued Tweedledee, 'if it was so, it might be; and
if it were so, it would be; but as it isn't, it ain't. That's logic.'"
-- Lewis Carroll, Through the Looking Glass
Rudolf
> Rudolf Adamkovič writes:
> If I remember well, Org decided to suggest with lowercase keywords
> (and use uppercase keywords in the manual, for some reason).
> Then, we should change "org-babel-results-keyword" from "RESULTS"
> to "results".
Change it for yourself. Please do
24 matches
Mail list logo
