emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Adam Spiers <orgmode@adamspiers.org>
To: emacs-orgmode@gnu.org
Subject: Re: org-capture doesn't narrow correctly if :prepend is t
Date: Mon, 16 Sep 2013 12:33:12 +0100	[thread overview]
Message-ID: <CAOkDyE_V_Qm8a_5tnssfE=52-KGu7DOv6M13X+at5ofJ+eQ=Sw@mail.gmail.com> (raw)
In-Reply-To: <CAOkDyE-PNYnK2EVGTz+f45kudUYRc37sMNc_s4dFujyn3hj6YQ@mail.gmail.com>

On 2 September 2013 18:51, Adam Spiers <orgmode@adamspiers.org> wrote:
> I have an org-capture template as follows:
>
>  ("n" "personal NEXT" entry
>   (file "~/org/TODO.org")
>   "* NEXT %?" :prepend t)
>
> but after I hit `C-c C-c', the file's buffer stays narrowed, with the
> new entry invisible.  Anyone who didn't notice the presence of
> 'Narrow' in the modeline would be convinced that the capture
> completely failed.  It can be revealed via `C-u C-x n w', but of
> course it's annoying having to do this every time.
>
> The problem vanishes as soon as I de-select the :prepend flag.  It's
> been an issue for a while, so I guess I'm the only one using this
> flag?

Judging by the lack of response, it seems noone else uses :prepend :-/
It's enough of an itch that I am happy to scratch / fix it myself, but
it would be great if someone could give me a few quick pointers on how
org-capture uses narrowing - otherwise it could take me quite a lot of
time and pain to understand it by myself ...

Thanks!
Adam

next prev parent reply	other threads:[~2013-09-16 11:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 17:51 org-capture doesn't narrow correctly if :prepend is t Adam Spiers
2013-09-16 11:33 ` Adam Spiers [this message]
2013-09-16 11:59   ` Carsten Dominik
2013-09-16 12:12     ` Adam Spiers
2013-09-16 21:56       ` Samuel Wales
2014-03-01 11:57     ` Thomas Proschinger
2014-03-13  9:45       ` Bastien
2014-03-15 11:19         ` Adam Spiers
2014-03-16 14:01         ` Thomas Proschinger

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='CAOkDyE_V_Qm8a_5tnssfE=52-KGu7DOv6M13X+at5ofJ+eQ=Sw@mail.gmail.com' \
    --to=orgmode@adamspiers.org \
    --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

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).