emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Noorul Islam <noorul@noorul.com>
Cc: Richard Riley <rileyrg@googlemail.com>, emacs-orgmode@gnu.org
Subject: Re: capture initial "level" and refile of capture buffer
Date: Mon, 25 Oct 2010 13:34:35 +0200	[thread overview]
Message-ID: <F0A1674C-8934-490B-8A28-E0A763893FFF@gmail.com> (raw)
In-Reply-To: <AANLkTikHLWVyUUoA6nUDS0Zd3nOzdt9CHyLjzG0gORpy@mail.gmail.com>

Hi Noorul,

could you please make a more detailed test case of this but, with an  
example files (capture target and refile target files) and step by  
step instructions.  I am not sure I understand what exactly you are  
doing.

Thanks.

- Carsten

On Oct 23, 2010, at 10:42 AM, Noorul Islam wrote:

> On Fri, Oct 22, 2010 at 5:13 PM, Richard Riley  
> <rileyrg@googlemail.com> wrote:
>>
>> What determines the level of a new capture element? e.g I just  
>> created
>> one and it started at "****".
>>
>> feature request : when I added some sub elements to a capture  
>> buffer e.g
>>
>> * my new capture
>>
>> ** sub point
>>
>> *** sub sub point 1
>> *** sub sub point 2
>>
>> and hit C-c C-w to refile, it only refiled the sub element (where  
>> cursor
>> was) and then lost the rest. I would like to suggest that refile from
>> the capture buffer should refile the entire buffer and not only the
>> "current nested org item". Or am I missing something in my setup?
>
> On my box I have this observation.
>
> If I have something like this in my capture buffer
>
> * TODO Test
>
> * my new capture
>
> ** sub point
>
> *** sub sub point 1
> *** sub sub point 2
>
>
> and if I press C-c C-w at the last line (*** sub sub point 2) and
> refile it to refile.org then what I get in refile.org is this
>
>
> * TODO Test
>
> * my new capture
>
> ** sub point
>
> *** sub sub point 1
> * sub sub point 2
>
>
> The last one's level got changed.
> I have latest pull from git repo.
>
> Org-mode version 7.01trans (release_7.01h.833.g21ad0)
> GNU Emacs 23.2.2 (i686-pc-linux-gnu)
> of 2010-06-08 on sajida
>
> Thanks and Regards
> Noorul
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

  parent reply	other threads:[~2010-10-25 11:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 11:43 capture initial "level" and refile of capture buffer Richard Riley
2010-10-23  8:42 ` Noorul Islam
2010-10-23 10:16   ` Noorul Islam
2010-10-23 10:34     ` Noorul Islam
2010-10-25  7:11     ` Carsten Dominik
2010-10-25  8:54       ` Noorul Islam
2010-10-25  9:11         ` Carsten Dominik
2010-12-12  8:39         ` Carsten Dominik
2010-10-25 11:34   ` Carsten Dominik [this message]
2010-10-26  8:37     ` Noorul Islam
2010-10-26  8:53 ` 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=F0A1674C-8934-490B-8A28-E0A763893FFF@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=noorul@noorul.com \
    --cc=rileyrg@googlemail.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).