From: Carsten Dominik <dominik@science.uva.nl>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Fix grammer and incorrect key documentation for org-refile
Date: Thu, 7 Feb 2008 08:11:12 +0100 [thread overview]
Message-ID: <CAE18A2D-124D-42F8-B604-EEB25F434B7D@science.uva.nl> (raw)
In-Reply-To: <87ir11a4ch.fsf@gollum.intra.norang.ca>
You are right, this is fixed now. Thanks.
- Carsten
On Feb 7, 2008, at 3:27 AM, Bernt Hansen wrote:
> Documentation fixes to clarify the use of org-refile.
> ---
>
> I came across the following documentation today which I believe is
> incorrect. Here's a patch in case it's useful. Thanks again for a
> great tool!
>
> org.el | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/org.el b/org.el
> index 8fffb80..c73218b 100644
> --- a/org.el
> +++ b/org.el
> @@ -14016,9 +14016,9 @@ At the target location, the entry is filed
> as a subitem of the target heading.
> Depending on `org-reverse-note-order', the new subitem will either
> be the
> first of the last subitem.
>
> -With prefix are GOTO, the command will only visit the target
> location,
> +With prefix argument GOTO, the command will only visit the target
> location,
> not actually move anything.
> -With a double prefix `C-c C-c', go to the location where the last
> refiling
> +With a double prefix `C-u C-u', go to the location where the last
> refiling
> operation has put the subtree.
>
> With a double prefix argument, the command can be used to jump to any
> --
> 1.5.4.23.gef5b9
>
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2008-02-07 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 2:27 [PATCH] Fix grammer and incorrect key documentation for org-refile Bernt Hansen
2008-02-07 7:11 ` Carsten Dominik [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=CAE18A2D-124D-42F8-B604-EEB25F434B7D@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=bernt@norang.ca \
--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).