Capture while Buffer is narrowed to subtree

Capture while Buffer is narrowed to subtree

[Memnon Anon]

Hi,

I've been working on a large subtree of my main orgfile while it was
narrowed [C-x n s]. While doing so, I wanted to capture some information
which usually ends up under "* Inbox" at the bottom of that file. This
time, the information ended up in the narrowed buffer with a new "*
Inbox" added. I only noticed after a while that my captured TODOs were
not where I expected them to be.

I know why this is happening (I guess :) but I was wondering if this was
intended behaviour. If so, maybe a footnote should be added to the
manual that hints at possible side effects of `C-x n s'?

Memnon

capture template
#+begin_src emacs-lisp
  (setq 
   org-capture-templates 
   '(("t" "Todo" entry (file+headline "~/life/organizer.org" "Inbox") "* TODO %?\n  %U\n  %i\n  %a")
      ("o" "Someday" entry (file+headline "~/life/organizer.org" "Inbox") "* SOMEDAY %?\n  %U\n  %i\n  %a")
      ("a" "Appointment" entry (file+headline "~/life/organizer.org" "Inbox") "* APPT %?\n  %^T\n  %U\n  %i\n  %a")
      ("b" "Bookmark" entry (file+headline "~/life/bookmarks.org" "Inbox") "* %a %?\n  %u")
      ...))
#+end_src

Org-mode version 7.4

GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) of 2010-12-11 on raven, modified by Debian

Re: Capture while Buffer is narrowed to subtree

[Christopher Allan Webber]

Hello Memnon!

I've definitely been experiencing this problem as well.  It's a frequent
annoyance.  It keeps breaking the flow of my orgmode files, since I
narrow to subree all the time, and capture all the time. :(

I don't think this is an intended feature, though I wonder if it's
fixable?  I hope so... I haven't had the chance to investigate the code
(and my fsf papers still haven't arrived so I couldn't fix it even if I
knew how).

Memnon Anon <gegendosenfleisch@googlemail.com> writes:

> Hi,
>
> I've been working on a large subtree of my main orgfile while it was
> narrowed [C-x n s]. While doing so, I wanted to capture some information
> which usually ends up under "* Inbox" at the bottom of that file. This
> time, the information ended up in the narrowed buffer with a new "*
> Inbox" added. I only noticed after a while that my captured TODOs were
> not where I expected them to be.
>
> I know why this is happening (I guess :) but I was wondering if this was
> intended behaviour. If so, maybe a footnote should be added to the
> manual that hints at possible side effects of `C-x n s'?
>
> Memnon
>
> capture template
> #+begin_src emacs-lisp
>   (setq 
>    org-capture-templates 
>    '(("t" "Todo" entry (file+headline "~/life/organizer.org" "Inbox") "* TODO %?\n  %U\n  %i\n  %a")
>       ("o" "Someday" entry (file+headline "~/life/organizer.org" "Inbox") "* SOMEDAY %?\n  %U\n  %i\n  %a")
>       ("a" "Appointment" entry (file+headline "~/life/organizer.org" "Inbox") "* APPT %?\n  %^T\n  %U\n  %i\n  %a")
>       ("b" "Bookmark" entry (file+headline "~/life/bookmarks.org" "Inbox") "* %a %?\n  %u")
>       ...))
> #+end_src
>
> Org-mode version 7.4
>
> GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) of 2010-12-11 on raven, modified by Debian
>
>
> _______________________________________________
> 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
>

-- 
𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻

Re: Capture while Buffer is narrowed to subtree

[Bastien]

Hi Memnon,

Memnon Anon <gegendosenfleisch@googlemail.com> writes:

> I've been working on a large subtree of my main orgfile while it was
> narrowed [C-x n s]. While doing so, I wanted to capture some information
> which usually ends up under "* Inbox" at the bottom of that file. This
> time, the information ended up in the narrowed buffer with a new "*
> Inbox" added. I only noticed after a while that my captured TODOs were
> not where I expected them to be.
>
> I know why this is happening (I guess :) but I was wondering if this was
> intended behaviour. 

It was clearly a bug, and a nasty one.  Thanks for bringing this up. 
I've just pushed a fix for this.

-- 
 Bastien