From: Le Wang <l26wang@gmail.com>
To: Orgmode Mailing List <emacs-orgmode@gnu.org>
Subject: patch to org-refile for more accurate completing-read
Date: Fri, 27 Jan 2012 22:44:50 +0800 [thread overview]
Message-ID: <CAM=K+ioO=L3FEg+Qtf8-UgKFPEAYhSr5TVX_p-Y8Vd+5u3eoog@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 166 bytes --]
Here: https://gist.github.com/1689071
When we are using using refile as navigation, require must-match regardless
of org-refile-allow-creating-parent-nodes.
--
Le
[-- Attachment #2: Type: text/html, Size: 244 bytes --]
next reply other threads:[~2012-01-27 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 14:44 Le Wang [this message]
2012-01-27 23:42 ` patch to org-refile for more accurate completing-read Bernt Hansen
2012-01-28 8:51 ` Le Wang
2012-02-08 19:21 ` David Maus
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='CAM=K+ioO=L3FEg+Qtf8-UgKFPEAYhSr5TVX_p-Y8Vd+5u3eoog@mail.gmail.com' \
--to=l26wang@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).