#+TAGS has some groups with many entries, suppress hotkey assignment

#+TAGS has some groups with many entries, suppress hotkey assignment

[Jeff Kowalczyk]

I am using a tagging strategy that required some mutually exclusive tag 
groups
to have large numbers of entries. In the example below facilty and customer 
can
be 30-50 entries to start, and grow slowly from there.

#+TAGS: { category: admin(a) development(d)
#+TAGS: { facility: fac1 fac2 fac3 fac4}
#+TAGS: { customer: cust1 cust2 cust3 }
#+TAGS: { billing: billable(b) nonbillable(o) }

This works well in testing, but the hotkey selection UI automatically assigns 
a
character to all entries. After running out of alphanumerics, it moves on to
punctuation and then to unicode characters.

Is there a way to selectively suppress automatic hotkey assignment? If
supressing all automatic hotkey assignment is the only/better option, I would 
be
content to have no hotkeys unless explicitly set with the tag(x) syntax.

Thanks for any suggestions,

Jeff

Re: #+TAGS has some groups with many entries, suppress hotkey assignment

[Carsten Dominik]

On 17.8.2013, at 04:04, Jeff Kowalczyk <jtk@yahoo.com> wrote:

> I am using a tagging strategy that required some mutually exclusive tag 
> groups
> to have large numbers of entries. In the example below facilty and customer 
> can
> be 30-50 entries to start, and grow slowly from there.
> 
> #+TAGS: { category: admin(a) development(d)
> #+TAGS: { facility: fac1 fac2 fac3 fac4}
> #+TAGS: { customer: cust1 cust2 cust3 }
> #+TAGS: { billing: billable(b) nonbillable(o) }
> 
> This works well in testing, but the hotkey selection UI automatically assigns 
> a
> character to all entries. After running out of alphanumerics, it moves on to
> punctuation and then to unicode characters.
> 
> Is there a way to selectively suppress automatic hotkey assignment? If
> supressing all automatic hotkey assignment is the only/better option, I would 
> be
> content to have no hotkeys unless explicitly set with the tag(x) syntax.
> 
> Thanks for any suggestions,

Please take a look at the variable org-use-fast-tag-selection and see if there is a setting that you find useful.

Cheers

- Carsten

> 
> Jeff
> 
> 
> 

Re: #+TAGS has some groups with many entries, suppress hotkey assignment

[Jeff Kowalczyk]

Carsten Dominik writes:
> Please take a look at the variable org-use-fast-tag-selection
> and see if there is a setting that you find useful.

Thanks Carsten, 'auto is the behaviour I am seeking.

Is org-use-fast-tag-selection 'auto working as intended? It seems to
be acting like value t as described in the function doc string.

My Emacs 24 with org-mode git master has the default value:

: org-use-fast-tag-selection
: auto

I can reproduce a minimal test file:


#+TAGS: { admin(a) reporting(r) util(u) foo }
#+TAGS: { projecta projectb projectc(c) }
#+TAGS: { billable(b) nonbillable(e) unknown(k) }

* headline


Where C-c C-c on headline gives the selector:


Inherited:
Current:

{ [a] admin         [r] reporting     [u] util          [f] foo    }
{ [p] projecta      [d] projectb      [c] projectc      }
{ [b] billable      [e] nonbillable   [k] unknown       }


I would have anticipated only explicit single key selectors, e.g.:


Inherited:
Current:

{ [a] admin         [r] reporting     [u] util          foo    }
{     projecta      projectb          [c] projectc      }
{ [b] billable      [e] nonbillable   [k] unknown       }


Thanks,
Jeff

Re: #+TAGS has some groups with many entries, suppress hotkey assignment

[Carsten Dominik]

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]


On 17.9.2013, at 17:56, Jeff Kowalczyk <jeff.kowalczyk@gmail.com> wrote:

> Carsten Dominik writes:
>> Please take a look at the variable org-use-fast-tag-selection
>> and see if there is a setting that you find useful.
> 
> Thanks Carsten, 'auto is the behaviour I am seeking.
> 
> Is org-use-fast-tag-selection 'auto working as intended? It seems to
> be acting like value t as described in the function doc string.

Well, yes.  If you specify only a single selection character, Org thinks that you want selection characters and assigns random ones to the others as well.

I do now understand what you mean.

No, this is currently not possible.  I might take a look at this after the 8.2 release.

- Carsten

> 
> My Emacs 24 with org-mode git master has the default value:
> 
> : org-use-fast-tag-selection
> : auto
> 
> I can reproduce a minimal test file:
> 
> 
> #+TAGS: { admin(a) reporting(r) util(u) foo }
> #+TAGS: { projecta projectb projectc(c) }
> #+TAGS: { billable(b) nonbillable(e) unknown(k) }
> 
> * headline
> 
> 
> Where C-c C-c on headline gives the selector:
> 
> 
> Inherited:
> Current:
> 
> { [a] admin         [r] reporting     [u] util          [f] foo    }
> { [p] projecta      [d] projectb      [c] projectc      }
> { [b] billable      [e] nonbillable   [k] unknown       }
> 
> 
> I would have anticipated only explicit single key selectors, e.g.:
> 
> 
> Inherited:
> Current:
> 
> { [a] admin         [r] reporting     [u] util          foo    }
> {     projecta      projectb          [c] projectc      }
> { [b] billable      [e] nonbillable   [k] unknown       }
> 
> 
> Thanks,
> Jeff
> 
> 
> 


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 455 bytes --]