From: Ihor Radchenko <yantar92@posteo.net>
To: Paul Stansell <paulstansell@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] tmp [9.7-pre (release_9.6.10-881-g595a32 @ /home/ps/.emacs.d/org-mode-git/lisp/)]
Date: Sat, 11 Nov 2023 09:43:13 +0000 [thread overview]
Message-ID: <87cywgwrpq.fsf@localhost> (raw)
In-Reply-To: <CAMJKaZw4CueNAyT85giWNfSPLP5BTA7RLe3ny1WTdcog6Oo03Q@mail.gmail.com>
Paul Stansell <paulstansell@gmail.com> writes:
> When using Org Mode version 9.7-pre (release_9.6.10-881-g595a32) the
> following happens that doesn't happen when using Org Mode version 9.5.5
> (release_9.5.5 @ /usr/share/emacs/28.2/lisp/org/)]:
>
> When the cursor is at the end of a folded section, that is, immediately
> after the ellipses, and return is pressed the folded section is made
> visible (i.e., it is unfolded).
This is expected.
> This is particularly problematic when adding a new section after the last
> section in an org file. If the last section is folded it seems impossible
> to get the cursor beyond the final ellipses so when adding a new section
> below this one (using return or Alt-return) the previous section is
> always opened. For sections that aren't the last one can put the cursor at
> the start of the next section and press Alt-return to insert a new section
> above it without unfolding any sections.
You can customize `org-fold-catch-invisible-edits' to return to past behavior.
Alternatively, use C-<RET>, which makes sure that formatting is not
broken despite editing near folded region.
Not a bug.
Canceled.
--
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>
next prev parent reply other threads:[~2023-11-11 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 20:09 [BUG] tmp [9.7-pre (release_9.6.10-881-g595a32 @ /home/ps/.emacs.d/org-mode-git/lisp/)] Paul Stansell
2023-11-10 20:19 ` Samuel Wales
2023-11-11 9:43 ` Ihor Radchenko [this message]
2023-11-11 10:36 ` Paul Stansell
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=87cywgwrpq.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=paulstansell@gmail.com \
/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).