From: Kevin Liu <kevin@nivekuil.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Fix org-narrow-to-subtree smaller than subtree
Date: Sat, 30 May 2020 18:54:16 -0700 [thread overview]
Message-ID: <87h7vw27jr.fsf@nivekuil.com> (raw)
In-Reply-To: <87zh9pmmqx.fsf@nicolasgoaziou.fr>
> There is a good reason for this. If you insert text at (point-max), you
> break the following headline.
>
> OTOH `org-mark-element' should pay attention to buffer boundaries.
Good point. `org-mark-element` uses (org-element-property); I wonder if
it makes sense to have the actual :end property of a subtree be the same
as its narrowed boundary?
next prev parent reply other threads:[~2020-05-31 1:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 13:29 [PATCH] Fix org-narrow-to-subtree smaller than subtree Kevin Liu
2020-05-30 13:35 ` Kevin Liu
2020-05-30 16:05 ` Nicolas Goaziou
2020-05-31 1:54 ` Kevin Liu [this message]
2020-05-31 12:23 ` Nicolas Goaziou
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=87h7vw27jr.fsf@nivekuil.com \
--to=kevin@nivekuil.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).