emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kevin Liu <kevin@nivekuil.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Fix org-capture-place-entry narrow bounds
Date: Sat, 13 Jun 2020 10:48:01 +0200	[thread overview]
Message-ID: <87o8pngxmm.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87sgficlog.fsf@nivekuil.com> (Kevin Liu's message of "Fri, 29 May 2020 17:26:39 -0700")


Kevin Liu <kevin@nivekuil.com> writes:

> From 8e7b28054492424170f14f11297b416ef7575540 Mon Sep 17 00:00:00 2001
> From: nivekuil <mail@nivekuil.com>
> Date: Fri, 29 May 2020 16:48:31 -0700
> Subject: [PATCH] capture: Fix org-capture-place-entry narrow bounds
> * lisp/org-capture.el
> (org-capture-place-entry):
> Prevent breaking the following headline inside the capture buffer.
> This should match the behavior from 9.3.
> (org-capture-finalize):
> Reverts cb2774d1a, which solves a similar problem but only in the
> finalize stage, so the subtree structure would still be broken in the
> middle of editing the capture.

Applied. Thank you.


Nicolas Goaziou

      reply	other threads:[~2020-06-13  8:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-30  0:25 [PATCH] Fix org-capture-place-entry narrow bounds Kevin Liu
2020-05-30  0:26 ` Kevin Liu
2020-06-13  8:48   ` Nicolas Goaziou [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:

  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=87o8pngxmm.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=kevin@nivekuil.com \


* 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


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