From: gerard.vermeulen@posteo.net
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Emacs orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BUG]: unexpected behavior related to org-indent-block
Date: Thu, 11 Jan 2024 14:14:14 +0000 [thread overview]
Message-ID: <7e14e605f4b2a9f802a75b91247245f2@posteo.net> (raw)
In-Reply-To: <87mstcjbas.fsf@localhost>
On 11.01.2024 13:37, Ihor Radchenko wrote:
> gerard.vermeulen@posteo.net writes:
>
>> Below, I show 2 commands to be run with point on a source block.
>> I expect that those commands modify an Org file identically, but
>> they do not. It fails when `org-indent-block' is called in a
>> loop after each `(insert (org-element-interpret-data copy))' and
>> it works when `org-indent-block' is called in a separate loop
>> after insertion of all `(org-element-interpret-data copy)'s:
>> ...
>> Example block:
>> ---
>> #+begin_src emacs-lisp
>> <point>
>> #+end_src
>> ---
>> make-2-indent-fails results in
>> ---
>> #+begin_src emacs-lisp
>> copy 1
>> #+end_src
>
> I cannot reproduce.
> I am seeing
>
> make-2-indent-fails results in
> ---
> #+begin_src emacs-lisp
> copy 1
> #+end_src
> #+begin_src emacs-lisp
> copy 2
> #+end_src
> <point>
>
> On the latest main.
This is strange:
I pulled the latest main and created a clean org-emacs directory
where I put a minimal init.el reading:
(when (eq system-type 'darwin)
(setopt ns-alternate-modifier nil
ns-command-modifier 'meta
ns-right-command-modifier 'super))
(push (expand-file-name "~/VCS/org-mode/lisp") load-path)
(require 'org)
After emacs --init-directory org-emacs, I get (code in the
result blocks got now indented):
Example block:
---
#+begin_src emacs-lisp
<point>
#+end_src
---
make-2-indent-fails results in
---
#+begin_src emacs-lisp
copy 1
#+end_src
---
make-2-indent-works results in
---
#+begin_src emacs-lisp
copy 1
#+end_src
#+begin_src emacs-lisp
copy 2
#+end_src
---
I have no idea what I can do now.
My Emacs is also recent main and built by me with minimal configure
options.
next prev parent reply other threads:[~2024-01-11 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 11:33 [BUG]: unexpected behavior related to org-indent-block gerard.vermeulen
2024-01-11 12:37 ` Ihor Radchenko
2024-01-11 14:14 ` gerard.vermeulen [this message]
2024-01-11 15:04 ` Ihor Radchenko
2024-01-11 15:48 ` gerard.vermeulen
2024-01-11 16:01 ` Ihor Radchenko
2024-01-11 16:41 ` gerard.vermeulen
2024-01-11 17:28 ` Ihor Radchenko
2024-01-11 18:06 ` gerard.vermeulen
2024-01-11 18:18 ` Ihor Radchenko
2024-01-12 19:19 ` Ihor Radchenko
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=7e14e605f4b2a9f802a75b91247245f2@posteo.net \
--to=gerard.vermeulen@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).