emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Miele <sebastian.miele@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Respect buffer-local value of `org-edit-src-content-indentation'
Date: Sun, 03 Nov 2019 22:25:45 +0000	[thread overview]
Message-ID: <87tv7ksil2.fsf@gmail.com> (raw)
In-Reply-To: <87y2wwr6ub.fsf@nicolasgoaziou.fr>

Hi Nicolas,

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Sebastian Miele <sebastian.miele@gmail.com> writes:
>
>> Subject: [PATCH] Respect buffer-local value of
>>  `org-edit-src-content-indentation'
>>
>> * lisp/org-src.el (org-src--contents-for-write-back): Use the
>> potentially buffer-local value of `org-edit-src-content-indentation'
>> from the source buffer instead of that from the editing buffer.
>
> Thank you.
>
> Would you mind explaining your use case?

The Org default of org-edit-src-content-indentation is 2. I like that
value and leave it that way. Worg's root .dir-locals sets it to 0
buffer-locally in at least many Worg's Org files. Hence, when I edit an
src block in a Worg file, the value of org-edit-src-content-indentation
in the edit buffer is 2. But the correct value in that case is 0.

Best wishes
Sebastian

  reply	other threads:[~2019-11-03 22:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 23:30 [PATCH] Respect buffer-local value of `org-edit-src-content-indentation' Sebastian Miele
2019-10-16  0:50 ` Adam Porter
2019-10-17  0:34   ` Sebastian Miele
2019-11-03 21:24     ` Nicolas Goaziou
2019-11-03 22:25       ` Sebastian Miele [this message]
2019-11-19 10:39         ` Nicolas Goaziou
2019-11-20  6:12           ` Sebastian Miele
2019-11-20 21:30             ` Nicolas Goaziou
2020-02-12 17:51 ` Bastien
2020-02-12 18:35   ` Sebastian Miele
2020-02-12 19:10     ` Bastien
2020-02-12 19:28       ` Sebastian Miele
2020-02-13 19:31         ` Sebastian Miele
2020-02-14 10:02           ` Bastien

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=87tv7ksil2.fsf@gmail.com \
    --to=sebastian.miele@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).