Hanno Perrey writes:
> Good point. I attach a patch that does just that. After the '~'
> character, only "space" is assigned -- which feels like a hack, but
> means that the selection key field is empty and that the fields are
> still aligned nicely. Actually selection any of these items is not
Ihor Radchenko writes:
> Hanno writes:
>
- 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
Hanno writes:
>>> - 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
>> - 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
Hanno writes:
> However, I have noticed some oddities with the characters that are being
> associated as keys to the entries in the interface:
>
> - after "a..z" runs out, '{', '|' and '}' are being used which seems
> reasonable -- but after that, I get '\200' and similar before reaching
>
Hej,
I use the fast tags selection interface (=org-set-tags-command= with
=org-use-fast-tag-selection= set to =t=) to quickly add several tags to
a heading. I have both tags and keys defined in
=org-tag-persistent-alist= and use
=org-complete-tags-always-offer-all-agenda-tags= to complete the
