From: Joel Walker <joel@trysomecode.com>
To: emacs-orgmode@gnu.org
Subject: org refile completion for won't use ido
Date: Tue, 25 Apr 2017 17:17:11 +0000 [thread overview]
Message-ID: <CAP0NVDjP_K6PjVpbTBoE8Eaw_cROPKde9EzyddBtZbxMfdZN6Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]
When using org-refile, I'm accustom to getting ido completion when
selecting a target due to the customizations in my init below. In org-mode
release 9.0.5, the minibuffer won't ido for an org-refile. Ido works
otherwise. There isn't an error, and refiling still works; ido completion
is just missing. I changed to org-mode release 8.3.6, things work as
expected.
; Use full outline paths for refile targets - we file directly with IDO
(setq org-refile-use-outline-path t)
; Targets complete directly with IDO
(setq org-outline-path-complete-in-steps nil)
; Allow refile to create parent tasks with confirmation
(setq org-refile-allow-creating-parent-nodes (quote confirm))
; Use IDO for both buffer and file completion and ido-everywhere to t
(setq org-completion-use-ido t)
(setq ido-everywhere t)
(setq ido-max-directory-size 100000)
(ido-mode (quote both))
; Use the current window when visiting files and buffers with ido
(setq ido-default-file-method 'selected-window)
(setq ido-default-buffer-method 'selected-window)
; Use the current window for indirect buffer display
(setq org-indirect-buffer-display 'current-window)
;;;; Refile settings
; Exclude DONE state tasks from refile targets
(defun bh/verify-refile-target ()
"Exclude todo keywords with a done state from refile targets"
(not (member (nth 2 (org-heading-components)) org-done-keywords)))
(setq org-refile-target-verify-function 'bh/verify-refile-target)
[-- Attachment #2: Type: text/html, Size: 1633 bytes --]
next reply other threads:[~2017-04-25 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 17:17 Joel Walker [this message]
2017-04-25 17:34 ` org refile completion for won't use ido Joel Walker
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=CAP0NVDjP_K6PjVpbTBoE8Eaw_cROPKde9EzyddBtZbxMfdZN6Q@mail.gmail.com \
--to=joel@trysomecode.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).