emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Carlos Pita <carlosjosepita2@gmail.com>,
	org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: Keyword completion list: uppercase or lowercase? (was: Shower thought: submit an IETF RFC to register Org as a MIME type)
Date: Sat, 23 Oct 2021 09:51:23 -0400	[thread overview]
Message-ID: <CAF-FPGPFS98GsOx0sphNiEahP5MxdfMbEKRoHtrYt9Kp5mTTCg@mail.gmail.com> (raw)
In-Reply-To: <871r4bg8op.fsf@localhost>

On Sat, Oct 23, 2021 at 9:41 AM Ihor Radchenko <yantar92@gmail.com> wrote:
> Carlos Pita <carlosjosepita2@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.


  reply	other threads:[~2021-10-23 13:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  1:21 Shower thought: submit an IETF RFC to register Org as a MIME type Carlos Pita
2021-10-23  6:45 ` Ihor Radchenko
2021-10-23  8:34   ` Carlos Pita
2021-10-23  8:36     ` Timothy
2021-10-23 13:41     ` Keyword completion list: uppercase or lowercase? (was: Shower thought: submit an IETF RFC to register Org as a MIME type) Ihor Radchenko
2021-10-23 13:51       ` Bruce D'Arcus [this message]
2021-10-23 14:21         ` Ihor Radchenko
2021-10-23 18:55       ` Keyword completion list: uppercase or lowercase? Carlos Pita

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAF-FPGPFS98GsOx0sphNiEahP5MxdfMbEKRoHtrYt9Kp5mTTCg@mail.gmail.com \
    --to=bdarcus@gmail.com \
    --cc=carlosjosepita2@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).