Hi Igor, > The conversation was about keywords and similar constructs (i.e. > ^#+keyword). You are looking at property drawer and properties inside. > There is no preference here, though internally properties in property > drawer are all converted to upper case.
Ok, thank you very much for the clarification. >> But then c-a-p is very lenient since it lists lower and upper case block >> variants even when I typed a lower case prefix, and upper case usually >> will go first in the list, hence promoting a seemingly bad practice. > > Could you clarify what is "c-a-p"? Yes, I just meant completion-at-point. At least some org functions, which I believe are implemented using pcomplete and then exposed through the completion-at-point interface, provide completions in both lower and uppercase variants and except when completion-ignore-case is nil (not the default) uppercase candidates will be sorted first in the list. It's often quite inconvenient to scroll down a completion menu to pick the lowercase completion for a short prefix, which either promotes using the uppercase variant at hand or offsets the benefits of autocompletion. Moreover, popular external collections of snippets have already adopted the lowercase convention of org-mode, hence introducing inconsistency in the document when one mixes both sources of completion (lowercase snippets and org-mode uppercase completions). So perhaps uppercase completions should be provided only when the user explicitly typed an uppercase prefix. What do you think? Best regards, Carlos
