emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Ihor Radchenko <yantar92@posteo.net>
To: Paul Schlesinger <phschlesinger@gmail.com>
Cc: Orgmode <emacs-orgmode@gnu.org>
Subject: Re: orgmode 9.6
Date: Fri, 16 Dec 2022 06:06:24 +0000	[thread overview]
Message-ID: <87r0wzsx0f.fsf@localhost> (raw)
In-Reply-To: <CAG8VtR3uBP24EcBc+juivL1vjZGk=aOjSNn5owQz3x+++8EOHQ@mail.gmail.com>

Paul Schlesinger <phschlesinger@gmail.com> writes:

> ...  At the end of the day I quit emacs, saving all my
> work for the day in a very large folder tree that includes all my working
> files and this is rsync'ed onto a usb disk that is a backup and is
> sync'ed to a disk on my home computer and I have redundant backups. About
> one month ago upgraded to orgmode  9.6 using elpa  and about a week ago I
> started getting an encoding warning when i would tell emacs I wanted to
> quit. The warning indicated the offending characters but they were in an
> unformatted buffer on the screen and I became fatigued trying to correct
> them.  If I save the file as raw-text I preserve all the org formatting and
> structure.  I upgraded ny home computer to 9.6 and this started happening
> on it also.

Thanks for reporting!

Did you notice which file this happened to?
If you did, does opening only that file, editing it, and closing trigger
the issue?

We need more information to understand what is happening.

-- 
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:[~2022-12-16  6:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 23:02 orgmode 9.6 Paul Schlesinger
2022-12-16  6:06 ` Ihor Radchenko [this message]
2022-12-16  6:47 ` Jean Louis
2022-12-16 21:28   ` Paul Schlesinger
2022-12-17 23:59     ` Jean Louis

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=87r0wzsx0f.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=phschlesinger@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

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