emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Jarmo Hurri <jarmo.hurri@iki.fi>
Cc: emacs-orgmode@gnu.org
Subject: Re: Binding RET to org-return-and-maybe-indent
Date: Thu, 23 Jul 2020 17:00:57 +0200	[thread overview]
Message-ID: <878sfaxoly.fsf@gmail.com> (raw)
In-Reply-To: <871rl2y2wa.fsf@iki.fi> (Jarmo Hurri's message of "Thu, 23 Jul 2020 12:52:21 +0300")

Jarmo Hurri <jarmo.hurri@iki.fi> writes:

>> #+begin_src emacs-lisp
>> (add-hook 'org-mode-hook (lambda () (electric-indent-mode -1)))
>> #+end_src
> Unfortunately this has side effects: it changes at least the way
> parentheses and indentation interact when opening a Babel source code
> block. It might be a good idea to mention this in ORG-NEWS.

Could you give us a precise recipe?  (Starting from emacs -Q and an
empty Org buffer)

I've fiddled a bit with source blocks just now and I'm noticing some
weirdness that I suspect might be due to electric-indent-mode
re-indenting the previous line when hitting RET (or C-j when disabling
electric-indent-mode), but nothing specific to parentheses.

Since I'm a bit pressed for time ATM it would help if you could give a
step-by-step explanation of what goes wrong.

  reply	other threads:[~2020-07-23 15:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 12:12 Binding RET to org-return-and-maybe-indent Jarmo Hurri
2020-07-22 14:50 ` Kévin Le Gouguec
2020-07-23  5:55   ` Jarmo Hurri
2020-07-23  9:52   ` Jarmo Hurri
2020-07-23 15:00     ` Kévin Le Gouguec [this message]
2020-07-24  4:26       ` Jarmo Hurri
2020-07-24 16:59         ` Kévin Le Gouguec
2020-07-27 10:18           ` Jarmo Hurri
2020-07-27 13:12             ` [PATCH] Fix recommendation in ORG-NEWS (was: Binding RET to org-return-and-maybe-indent) Kévin Le Gouguec
2020-07-29  1:51               ` Kyle Meyer

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:

  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=878sfaxoly.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jarmo.hurri@iki.fi \


* 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


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