emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "Alejandro Pérez Carballo" <apc@umass.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Setting export scope to subtree not working as expected [9.6 (9.6-gb3da42 @ /Users/apc/.emacs.d/straight/build/org/)]
Date: Sat, 10 Dec 2022 09:45:55 +0000	[thread overview]
Message-ID: <87359nsib0.fsf@localhost> (raw)
In-Reply-To: <m2sfhpffui.fsf@umass.edu>

Alejandro Pérez Carballo <apc@umass.edu> writes:

> If point is on a heading followed by a subheading without any text in between, the export process is using the tree starting with the subheading instead of the tree starting from point position. If instead you have some text after the first heading and before the subheading, the tree that is exported is the tree starting from point position, as expected. I’m assuming this is a bug, but maybe I’m missing something.
>
> For example, take a buffer containing just this:
>
>    * The title
>    ** A subtitle
>    Some text
>
> If I export this to an HTML buffer, with point at the beginning of the first line and  after setting the scope to ‘subtree’, I get an HTML buffer whose title is “A subtitle”.
>
> If I follow the same steps on a buffer containing just this: 
>
>    * The title
>    Some text
>    ** A subtitle
>
> I get an HTML buffer whose title is “The title”.

Thanks for reporting!
Fixed on bugfix.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=0616b3c37

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2022-12-10  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09  2:52 [BUG] Setting export scope to subtree not working as expected [9.6 (9.6-gb3da42 @ /Users/apc/.emacs.d/straight/build/org/)] Alejandro Pérez Carballo
2022-12-10  9:45 ` Ihor Radchenko [this message]
2022-12-10 11:10   ` Kaushal Modi
2022-12-10 18:58     ` Alejandro Perez Carballo

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=87359nsib0.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=apc@umass.edu \
    --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
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).