emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Kaiyu Zheng <kaiyu_zheng@alumni.brown.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Inconvenient end-of-file behavior in org-mode 9.6 (emacs 29.1)
Date: Fri, 18 Aug 2023 15:54:22 +0000	[thread overview]
Message-ID: <87wmxs8hxt.fsf@localhost> (raw)
In-Reply-To: <CAG=i0189HjWb1jS1TMOwFy7byYKyuSAYcAdgPa5KL_1KBY=rYQ@mail.gmail.com>

Kaiyu Zheng <kaiyu_zheng@alumni.brown.edu> writes:

> In 28.3 and before, when I do `M->`, and hit 'Enter', I get to the end
> of file on a new line outside of SubSec2, like so:
>
> * Sec1
> ** SubSec1
> ** SubSec2
> |
>
> And now I could type `** SubSec3` to add a new section like below:
>
> * Sec1
> ** SubSec1
> ** SubSec2
> ** SubSec3|
>
> But in 29.1, when I do the same sequence, the cursor is "trapped" in
> SubSec2, and I had to expand SubSec2 first in order to see what I'm
> typing. I don't like this behavior -- I wonder why it is this way in
> the new version. How is this better? Could we revert back?

You can try some other key that is not enter. For example, <SPC>.
'Enter' should work on main, the development branch.

I will see what can be done on stable Org version.

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


  reply	other threads:[~2023-08-18 15:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 13:19 Inconvenient end-of-file behavior in org-mode 9.6 (emacs 29.1) Kaiyu Zheng
2023-08-18 15:54 ` Ihor Radchenko [this message]
2023-08-19  7:28   ` Ihor Radchenko
2023-08-19  3:26 ` Max Nikulin
2023-08-19  7:55   ` Ihor Radchenko
2023-08-20  2:41     ` Max Nikulin
2023-08-20  6:32       ` Ihor Radchenko
2023-08-20 16:17         ` Max Nikulin

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=87wmxs8hxt.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaiyu_zheng@alumni.brown.edu \
    /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).