emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Garklein <garklein97@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] pressing enter with org-src-tab-acts-natively over-intends block
Date: Thu, 3 Oct 2024 16:40:51 -0400	[thread overview]
Message-ID: <CALp=Ckko1Ck7-3K+bfKXLVSqDJvmHWYEZutkj5J2v3t=QuVhcw@mail.gmail.com> (raw)
In-Reply-To: <87v7y9ccbl.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]

Hi,

`org-edit-src-preserve-indentation' says "the minimum (across-lines)
number of leading whitespace characters are removed from all lines,
and the code block is uniformly indented according to the value of
‘org-edit-src-content-indentation'", but it doesn't seem to be
removing the whitespace, only adding it.

Is there a way to configure this?

Thank you,
Garklein

On Thu, Oct 3, 2024 at 1:41 PM Ihor Radchenko <yantar92@posteo.net> wrote:
>
>
> > With `org-src-tab-acts-natively' set to `t', pressing enter in a
> > source code block adds a newline, then indents every line in the block
> > by two spaces.
> >
> > I would expect that it adds a newline and positions my cursor where it
> > should be with the indentation, without indenting every single other
> > line in the block.
>
> See `org-edit-src-content-indentation' and
> `org-src-preserve-indentation'.
>
> Not a bug.
> Canceled.
>
> --
> 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>

[-- Attachment #2: 2024-10-03 16-38-36.mp4 --]
[-- Type: video/mp4, Size: 480962 bytes --]

next prev parent reply	other threads:[~2024-10-03 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 15:02 [BUG] pressing enter with org-src-tab-acts-natively over-intends block Garklein
2024-10-03 17:42 ` Ihor Radchenko
2024-10-03 20:40   ` Garklein [this message]
2024-10-12 18:31     ` 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='CALp=Ckko1Ck7-3K+bfKXLVSqDJvmHWYEZutkj5J2v3t=QuVhcw@mail.gmail.com' \
    --to=garklein97@gmail.com \
    --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

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).