emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Jeff Kowalczyk <jtk@yahoo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: #+TAGS has some groups with many entries, suppress hotkey assignment
Date: Fri, 30 Aug 2013 17:59:17 +0200	[thread overview]
Message-ID: <B47ABEF3-5AA9-472C-8540-D79A01F2E743@gmail.com> (raw)
In-Reply-To: <loom.20130817T034523-96@post.gmane.org>


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

  reply	other threads:[~2013-08-30 16:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-17  2:04 #+TAGS has some groups with many entries, suppress hotkey assignment Jeff Kowalczyk
2013-08-30 15:59 ` Carsten Dominik [this message]
2013-09-17 15:56   ` Jeff Kowalczyk
2013-09-18  4:23     ` Carsten Dominik

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=B47ABEF3-5AA9-472C-8540-D79A01F2E743@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jtk@yahoo.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).