[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [BUG] defaults make it hard to edit Elisp blocks in org buffers
From: |
Ihor Radchenko |
Subject: |
Re: [BUG] defaults make it hard to edit Elisp blocks in org buffers |
Date: |
Thu, 18 Jan 2024 18:19:23 +0000 |
gerard.vermeulen@posteo.net writes:
>> I cannot think of any common use where the two approches differ, and
>> it is indeed simpler. The possibility that the block does not have the
>> common indentation still stands.
>
> As far as I understand, the effect also occurs when the block has a
> common indentation. Below are the steps:
> ...
> And with POINT after "?" and typing ENTER (wait more than 1 second
> for automatic indenting of 2 spaces), I can type parentheses with
> some sort of common indentation like below:
> #+begin_src emacs-lisp
> ;; common indentation?
> (())
> (())
> (())
> #+end_src
> When I place POINT in the middle of the lowest parentheses and
> type ENTER, then everything moves 2 spaces to the right like below:
This is expected, because we already have a special case for creating an
empty line - it does not contribute to common indentation we calculate.
But the special case for empty line does not cover your original
reproducer.
--
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>