emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Guillaume MULLER <guillaume.muller@alolise.org>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Change of behavior of org-meta-return in 9.6/DoomEmacs?
Date: Tue, 17 May 2022 12:57:08 -0400	[thread overview]
Message-ID: <CAFyQvY3XHf6WWDtdwtKMGLWGApgQ89ziUcGSfHCJnn-c3gV8=A@mail.gmail.com> (raw)
In-Reply-To: <41f10572-03d0-8c7a-341a-26c0315753d0@alolise.org>

On Tue, May 17, 2022 at 12:24 PM Guillaume MULLER
<guillaume.muller@alolise.org> wrote:
> I noticed that hitting Meta-Return in org in Doom does not behave as in Vanilla Emacs. If I have (with <> being the cursor):
> * outline 1
> ** outline 2
>    + no<>te1
>    + note2
> In Vanilla Emacs, hitting M-Ret (i.e. calling org-meta-return) resulted in:
> * outline 1
> ** outline 2
>    + no
>    + <>te1
>    + note2

I am seeing your Vanilla Emacs behavior on Emacs 28.1 with Org built
from main branch (Org mode version 9.5.3 (release_9.5.3-504-gcdbb1c)).

> As I use "keycast" package, I can see that, in both cases:
> - M-Ret is org-meta-return
> - C-Ret is +org/insert-item-below

The keycast package's modeline display might not show if that
org-meta-return has been advised to modify the behavior.

If you do C-h f org-meta-return, do you see something like "This
function has .. advice: .." towards the end of that *Help* buffer?

> How can I check if it is a change in org 9.6 or in DoomEmacs?

Try reverting your DoomEmacs version to an older version to see if
that fixes it.
Then try reverting to the Org stable version from GNU ELPA (version
9.5.3) and see if that fixes the issue.

Also, may be opening an issue on the DoomEmacs repo might help.

Good luck!

  reply	other threads:[~2022-05-17 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 22:14 Change of behavior of org-meta-return in 9.6/DoomEmacs? Guillaume MULLER
2022-05-17 16:57 ` Kaushal Modi [this message]
2022-05-20 20:50   ` Guillaume MULLER
2022-05-18 18:31 ` Nick Dokos

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='CAFyQvY3XHf6WWDtdwtKMGLWGApgQ89ziUcGSfHCJnn-c3gV8=A@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=guillaume.muller@alolise.org \


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