From: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] defaults make it hard to edit Elisp blocks in org buffers
Date: Thu, 18 Jan 2024 16:45:25 +0000 [thread overview]
Message-ID: <d263b4af-3d9b-459b-aa27-a2e1d09a7f77@posteo.eu> (raw)
In-Reply-To: <878r4makff.fsf@localhost>
Ihor Radchenko writes:
>> If I recall correctly, in order to fix this, in =org-indent-line=,
>> before calling =TAB= in the native buffer, one should check the
>> current line indentation and if it is less than =block-content-ind=,
>> start by adding this much indentation to the current line.
>>
>> This could be a bit fragile, and in particular it assumes that the
>> rest of the block has this =block-content-ind=, which might not be the
>> case. One could possibly at least check that the first line of the
>> block does have this much indentation. If it doesn't, just do
>> whatever.
> What about a simpler approach - indent the line at point to block's
> expected indentation (if it is not yet there) and then rely upon the
> code block's major mode to do the right thing?
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.
--
Sébastien Miquel
next prev parent reply other threads:[~2024-01-18 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 18:34 [BUG] defaults make it hard to edit Elisp blocks in org buffers gerard.vermeulen
2024-01-17 20:04 ` Sébastien Miquel
2024-01-18 12:35 ` Ihor Radchenko
2024-01-18 16:45 ` Sébastien Miquel [this message]
2024-01-18 18:11 ` gerard.vermeulen
2024-01-18 18: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=d263b4af-3d9b-459b-aa27-a2e1d09a7f77@posteo.eu \
--to=sebastien.miquel@posteo.eu \
--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).