emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Hanno <hanno@hoowl.se>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Odd characters in the fast tags selection interface
Date: Fri, 05 Aug 2022 12:54:59 +0200	[thread overview]
Message-ID: <7AB4F327-24D0-4BA5-BD20-B329D4CBBF0A@hoowl.se> (raw)
In-Reply-To: <878ro3phee.fsf@localhost>


>> - after "a..z" runs out, '{', '|' and '}' are being used which seems
>>   reasonable -- but after that, I get '\200' and similar before reaching
>>   '©'...
>
>This is indeed true, but what can we do? There are only that many
>characters in the keyboard. We may instead start using two-key
>combinations for tags beyond #26, similar to org-capture. Patches are
>welcome!

Thanks for the fast reply and fully agreed! I would indeed argue that automatically generated keys are not useful beyond a certain number (N=26?) as they could change with new tags and thus are hard to memorize. And taking in >N random choices every time is hardly "fast select" anymore.

In fact, the docstring for =org-fast-tag-selection= says that only a-z would be automatically assigned. That sounds reasonable to me (otherwise one can define more keys via =org-tag-persistent-alist=). Maybe this is a bug after all? If more than 26 choices are desired, maybe A-Z (i.e. capital letters) could extend the list before more unusual characters?

What do you think?

I am not at my computer right now but could try to come up with a patch later.


>> - when defining my own keys, they are not displayed in the top; instead
>>   their characters are missing in the 'a'..'z' range leaving more room
>>   for odd and very difficult-to-type characters
>I think that it would make sense to have `org-tag-persistent-alist`
>staff being shown on top. Unless there are objections I can merge this
>trivial change.

Thanks, that already improves the usability a lot!

Thanks and cheers,
Hanno



  reply	other threads:[~2022-08-05 10:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 21:41 Odd characters in the fast tags selection interface Hanno
2022-08-05  2:12 ` Ihor Radchenko
2022-08-05 10:54   ` Hanno [this message]
2022-08-06  8:13     ` Ihor Radchenko
2022-08-07 17:55       ` [PATCH] org.el: Improve automatic fast tag selection keys (was: Odd characters in the fast tags selection interface) Hanno Perrey
2022-08-07 23:42         ` Christopher M. Miles
2022-08-08 13:24         ` Ihor Radchenko
     [not found]         ` <62f04f7c.d40a0220.9da67.0a2cSMTPIN_ADDED_BROKEN@mx.google.com>
2022-08-08 13:36           ` [PATCH] org-fast-tag-selection: Make group tags separator not break alignment Ihor Radchenko
2022-08-22 12:02             ` Ihor Radchenko
2022-08-07 23:47       ` Odd characters in the fast tags selection interface Christopher M. Miles

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=7AB4F327-24D0-4BA5-BD20-B329D4CBBF0A@hoowl.se \
    --to=hanno@hoowl.se \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).