emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: dalanicolai <dalanicolai@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] demarcate block splits block even when outside of src-block
Date: Tue, 25 Oct 2022 09:42:08 +0000	[thread overview]
Message-ID: <87sfjcs0i7.fsf@localhost> (raw)
In-Reply-To: <CACJP=3nCekgX4RuYBWf=R_2t05-s4ikx-L9qP7W0cSicNG55BA@mail.gmail.com>

dalanicolai <dalanicolai@gmail.com> writes:

>  [9.5.4 (release_9.5.4 @ /usr/local/share/emacs/29.0.50/lisp/org/)]
>
> When trying to create a new src-block via `M-x
> org-babel-demarcate-block` immediately after a previous code block (only
> empty lines in between), then the command behaves like when splitting a
> src-block (inserting an #+end_src first, followed by a #+begin_src).
>
> However, as the point is outside of the source block, according to the
> docstring of the command, a new source block should be created.
>
> As a comment, normally when creating a new source block, Emacs prompts
> for the source block type. However, currently, when used as mentioned
> here, the command automatically sets the type (because it tries to
> split). I would say that is convenient behavior, so that effectively
> only the order of the inserted lines should get reversed.

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

-- 
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-10-25  9:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13  0:24 [BUG] demarcate block splits block even when outside of src-block dalanicolai
2022-10-25  9:42 ` Ihor Radchenko [this message]
2022-10-25 11:14   ` dalanicolai

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=87sfjcs0i7.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=dalanicolai@gmail.com \
    --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).