From: Kaiyu Zheng <kaiyu_zheng@alumni.brown.edu>
To: emacs-orgmode@gnu.org
Subject: Inconvenient end-of-file behavior in org-mode 9.6 (emacs 29.1)
Date: Wed, 16 Aug 2023 09:19:10 -0400 [thread overview]
Message-ID: <CAG=i0189HjWb1jS1TMOwFy7byYKyuSAYcAdgPa5KL_1KBY=rYQ@mail.gmail.com> (raw)
Dear Org-mode maintainers,
Org-mode has been fantastic. However, in the most recent release as
part of emacs 29.1, I am experiencing an inconvenience that made me
switch back to 28.3. (I learned from this page
https://irreal.org/blog/?p=10982 that emacs 29.1 released org-mode
9.6).
The issue is: let's say I have a simple org-mode file, and let's say
the cursor starts at the top of the file (marked by '|'):
|* Sec1
** SubSec1
** SubSec2
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?
Now, you could argue that I should type in the keybinding for
inserting the subsection instead of doing this manually. But I simply
don't remember (and never tried remembering) the keybinding for adding
a new section -- I don't think I'm wrong by not remembering that
keybinding. I was able to do what I wanted before in a simple and
natural way.
I hope my concern is valid.
Best,
Kaiyu
next reply other threads:[~2023-08-18 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 13:19 Kaiyu Zheng [this message]
2023-08-18 15:54 ` Inconvenient end-of-file behavior in org-mode 9.6 (emacs 29.1) Ihor Radchenko
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='CAG=i0189HjWb1jS1TMOwFy7byYKyuSAYcAdgPa5KL_1KBY=rYQ@mail.gmail.com' \
--to=kaiyu_zheng@alumni.brown.edu \
--cc=emacs-orgmode@gnu.org \
/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).