On Sat, Oct 23, 2021 at 9:41 AM Ihor Radchenko <yanta...@gmail.com> wrote: > > Carlos Pita <carlosjosepi...@gmail.com> writes: > > >>> 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? > > I just tried with clean Emacs: > > #+beg<complete -> #+begin_<complete> -> list of completions, all in lower case > #+BEG<complete -> #+BEGIN_<complete> -> list of completions, all in upper case
Perhaps at some point the upper case should just be removed? This raises a related question I've wondered about: Why doesn't the completion insert the full begin/end, and put point inside? It's a bit of an awkward UX to add the end line ATM. Bruce