From: Ihor Radchenko <yantar92@posteo.net>
To: Jerome <jeromesiljan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Bug Report [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]
Date: Tue, 12 Mar 2024 18:59:00 +0000 [thread overview]
Message-ID: <87cyrzjmyz.fsf@localhost> (raw)
In-Reply-To: <7199B7A5-FA81-4E50-8EF4-9C74F38DDF2F@gmail.com>
[ Adding Org mailing list back to CC. Please use "reply all" to keep the
conversation public ]
Jerome <jeromesiljan@gmail.com> writes:
> This specific case (deleting a line and getting a bug) has only happened once. Might also be worth noting that I only ever get bugs in this one org file that I open, never in any others so it might be fairly niche.
This kind of bugs is indeed fairly niche. The reason why we display the
warning and ask to report is to catch various edge cases users may
encounter. (We have hard time making the relevant code 100% reliable -
it is asynchronous and often depends on details of Org buffer structure
+ editing sequence)
In any case, if you are lucky, updating Org mode to the latest stable
version (Org 9.6.21) or to the latest main (development version Org
9.7-pre) might eliminate the bug.
May you upgrade and report back if you keep seeing problems?
--
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>
prev parent reply other threads:[~2024-03-12 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 4:55 [BUG] Bug Report [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)] Jerome Siljan
2024-03-12 13:47 ` Ihor Radchenko
[not found] ` <7199B7A5-FA81-4E50-8EF4-9C74F38DDF2F@gmail.com>
2024-03-12 18:59 ` Ihor Radchenko [this message]
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=87cyrzjmyz.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jeromesiljan@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).