* Bug: headlines escape blocks [9.3 (9.3-elpaplus @ /home/tom/.emacs.d/elpa/org-plus-contrib-20191203/)]
@ 2019-12-07 5:20 Tom Gillespie
2019-12-07 11:12 ` Nicolas Goaziou
0 siblings, 1 reply; 4+ messages in thread
From: Tom Gillespie @ 2019-12-07 5:20 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
* Description
Headlines are not ignored inside of blocks when the headline is not indented.
* Affected versions
9.1.9, 9.3
* Observed behavior
Lines starting with any headline pattern =*=, =**= etc. are treated as
headlines inside all block types. Example and source blocks highlight
as if the text is escaped, diverging from the behavior of org-mode.
Verse blocks highlight as a headline, in agreement with the behavior.
* Expected behavior
I would expect the behavior implied by the highlighting in the example
and source blocks. Blocks should take precedence over the headline
behavior.
* Reproduction
See example below (attached as a standalone file as well).
---------------
To reproduce =emacs -q --load org -- org-bug-1.org=
#+BEGIN_EXAMPLE
* This should not be treated as a header
but for some reason it is
#+END_EXAMPLE
#+BEGIN_SRC
* Neither should this be treated as a header
but for some reason it is
** And so is this
#+END_SRC
#+BEGIN_VERSE
* Ode to a left aligned headline
this one colors correctly
#+END_VERSE
#+BEGIN_SRC
* This one does not highlight correctly
hrm
#+END_SRC
---------------
Emacs : GNU Emacs 26.3 (build 1, x86_64-pc-linux-gnu, X toolkit)
of 2019-09-27
Package: Org mode version 9.3 (9.3-elpaplus @
/home/tom/.emacs.d/elpa/org-plus-contrib-20191203/)
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
/usr/share/emacs/26.3/lisp/org/)
[-- Attachment #2: org-bug-1.org --]
[-- Type: application/vnd.lotus-organizer, Size: 420 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bug: headlines escape blocks [9.3 (9.3-elpaplus @ /home/tom/.emacs.d/elpa/org-plus-contrib-20191203/)]
2019-12-07 5:20 Bug: headlines escape blocks [9.3 (9.3-elpaplus @ /home/tom/.emacs.d/elpa/org-plus-contrib-20191203/)] Tom Gillespie
@ 2019-12-07 11:12 ` Nicolas Goaziou
2019-12-07 20:31 ` Tom Gillespie
0 siblings, 1 reply; 4+ messages in thread
From: Nicolas Goaziou @ 2019-12-07 11:12 UTC (permalink / raw)
To: Tom Gillespie; +Cc: emacs-orgmode
Hello,
Tom Gillespie <tgbugs@gmail.com> writes:
> * Description
> Headlines are not ignored inside of blocks when the headline is not indented.
>
> * Affected versions
> 9.1.9, 9.3
>
> * Observed behavior
> Lines starting with any headline pattern =*=, =**= etc. are treated as
> headlines inside all block types. Example and source blocks highlight
> as if the text is escaped, diverging from the behavior of org-mode.
> Verse blocks highlight as a headline, in agreement with the behavior.
This is the expected behaviour. See (info "(org) Literal Examples")
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bug: headlines escape blocks [9.3 (9.3-elpaplus @ /home/tom/.emacs.d/elpa/org-plus-contrib-20191203/)]
2019-12-07 11:12 ` Nicolas Goaziou
@ 2019-12-07 20:31 ` Tom Gillespie
2019-12-08 8:05 ` Nicolas Goaziou
0 siblings, 1 reply; 4+ messages in thread
From: Tom Gillespie @ 2019-12-07 20:31 UTC (permalink / raw)
To: emacs-orgmode
Hi Nicolas,
Thanks for the reply and pointer to the docs. Given that the
headlines are working as expected, is there the possibility to
change how the syntax highlighting for source and example
blocks works so that it matches the behavior for the verse blocks?
Best,
Tom
On Sat, Dec 7, 2019 at 3:12 AM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>
> Hello,
>
> Tom Gillespie <tgbugs@gmail.com> writes:
>
> > * Description
> > Headlines are not ignored inside of blocks when the headline is not indented.
> >
> > * Affected versions
> > 9.1.9, 9.3
> >
> > * Observed behavior
> > Lines starting with any headline pattern =*=, =**= etc. are treated as
> > headlines inside all block types. Example and source blocks highlight
> > as if the text is escaped, diverging from the behavior of org-mode.
> > Verse blocks highlight as a headline, in agreement with the behavior.
>
> This is the expected behaviour. See (info "(org) Literal Examples")
>
> Regards,
>
> --
> Nicolas Goaziou
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bug: headlines escape blocks [9.3 (9.3-elpaplus @ /home/tom/.emacs.d/elpa/org-plus-contrib-20191203/)]
2019-12-07 20:31 ` Tom Gillespie
@ 2019-12-08 8:05 ` Nicolas Goaziou
0 siblings, 0 replies; 4+ messages in thread
From: Nicolas Goaziou @ 2019-12-08 8:05 UTC (permalink / raw)
To: Tom Gillespie; +Cc: emacs-orgmode
Hello,
Tom Gillespie <tgbugs@gmail.com> writes:
> Thanks for the reply and pointer to the docs. Given that the
> headlines are working as expected, is there the possibility to
> change how the syntax highlighting for source and example
> blocks works so that it matches the behavior for the verse blocks?
I do not understand. Source and example blocks are verbatim blocks,
whereas verse blocks are not. There is nothing to match, is there?
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-12-08 8:05 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-12-07 5:20 Bug: headlines escape blocks [9.3 (9.3-elpaplus @ /home/tom/.emacs.d/elpa/org-plus-contrib-20191203/)] Tom Gillespie
2019-12-07 11:12 ` Nicolas Goaziou
2019-12-07 20:31 ` Tom Gillespie
2019-12-08 8:05 ` Nicolas Goaziou
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).