From: Carsten Dominik <carsten.dominik@gmail.com>
To: David Maus <dmaus@ictsoc.de>
Cc: Jules Bean <jules@jellybean.co.uk>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Org-capture breaks if captured-to file is open in a narrowed buffer
Date: Fri, 24 Sep 2010 09:01:33 +0200 [thread overview]
Message-ID: <FCCB0ABD-B997-4E8C-AD7E-AF0CFEB5EDE1@gmail.com> (raw)
In-Reply-To: <877hicxotf.wl%dmaus@ictsoc.de>
On Sep 23, 2010, at 9:06 PM, David Maus wrote:
> David Maus wrote:
>> Jules Bean wrote:
>>> If I run org-capture with the template:
>
>>> ("t" "Todo" entry (file+headline
>>> "/Users/jules/work/TODO.org" "Tasks") "* TODO %?
>>> (Captured at %u)
>>> %i
>>> %a
>>> ")
>
>>> whilst I have narrowed (using, e.g., org-narrow-to-subtree) the
>>> buffer
>>> that contains TODO.org, a new "* Tasks" headline is inserted at the
>>> end of my narrowing and the new entry is added there, which messes
>>> up
>>> the hierarchy of the file.
>
>> I can confirm this with
>
>> Org-mode version 7.01trans (release_7.01h.497.g59fa)
>
>> GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
>> of 2010-08-14 on raven, modified by Debian
>
> Attached should fix this problem.
Looks good to me.
- Carsten
>
> Best,
> -- David
> --
> OpenPGP... 0x99ADB83B5A4478E6
> Jabber.... dmjena@jabber.org
> Email..... dmaus@ictsoc.de
> <0001-Widen-to-remove-possible-restrictions-in-target-
> buff.patch>_______________________________________________
> 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
next prev parent reply other threads:[~2010-09-24 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 11:38 [BUG] Org-capture breaks if captured-to file is open in a narrowed buffer Jules Bean
2010-09-12 16:50 ` David Maus
2010-09-23 19:06 ` David Maus
2010-09-24 7:01 ` Carsten Dominik [this message]
2010-09-24 12:29 ` David Maus
2010-09-24 15:17 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FCCB0ABD-B997-4E8C-AD7E-AF0CFEB5EDE1@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
--cc=jules@jellybean.co.uk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.