From: torys.anderson@gmail.com (Tory S. Anderson)
To: orgmode list <emacs-orgmode@gnu.org>
Subject: Re: navigating org-clock-in recent work list
Date: Sat, 14 Feb 2015 07:00:17 -0500 [thread overview]
Message-ID: <87vbj43dpq.fsf@gmail.com> (raw)
In-Reply-To: 87a90h6alu.fsf@gmail.com
So being new to elisp, I'm hoping there's a simple hack to disable the org-clock-select-task menu and go to a default (e.g. `C-x b' or `C-x f') style "type your option" interface that will would be populated with and return the same thing as the select-task-menu?
I've been looking at the elisp behind the buffer switching functions and I'm afraid it's beyond me; perhaps the "default" of invoking a prompt and passing autocompletion values isn't as simple as I'd hoped?
torys.anderson@gmail.com (Tory S. Anderson) writes:
> As per a recent discussion on the mailing list, I'm using the following to enable persistence and extended length of the clock history:
>
> ;; Org clock-in
> (org-clock-persistence-insinuate)
> (setq org-clock-persist t)
> ;;; * Orgmode Modules
> (add-to-list 'org-modules 'habits)
> ;; Number of clock tasks to remember in history.
> (setq org-clock-history-length 35) ; 1 to 9 + A to Z
>
> It works great, with one annoying problem: now that I have a list that goes to M, it can be hard to figure out which shortcut goes to which item. I can think of two possible solutions:
>
> 1. Alternately highlight lines, or underline (spreadsheet/table style)
> 2. Preferably, since I use Helm, if there were simply an autocomplete prompt (like switch-buffer; no shortcut keys) this would actually be easiest.
>
> Can I disable the special pop-up screen (i.e. `org-clock-select-task') and just use an shortcut-less autocomplete prompt (which, with helm will be facilitated)?
prev parent reply other threads:[~2015-02-14 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 16:26 navigating org-clock-in recent work list Tory S. Anderson
2015-02-14 12:00 ` Tory S. Anderson [this message]
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=87vbj43dpq.fsf@gmail.com \
--to=torys.anderson@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).