emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Mauger <michael.mauger@protonmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: 31.0.50; Org Persist file formatting
Date: Sat, 31 Aug 2024 14:58:00 +0000	[thread overview]
Message-ID: <8ILFtc_1-n1gBnSbTgZbG42wVVcKPZsz-9Wmjx3EzEPhz06N68_2boKsuw8wwfH-dWmk-Nl-ZMQ108S5C0weVL0BJ7uRyTB5Y-UNuTTkAeY=@protonmail.com> (raw)
In-Reply-To: <87seuklpjx.fsf@localhost>


-------- Original Message --------
On 8/31/24 10:43 AM, Ihor Radchenko <yantar92@posteo.net> wrote:

>  Michael Mauger <michael.mauger@protonmail.com> writes:
>  
>  > Bad news :(  I do not have a reproducible set of steps, but I'll start looking for one. I am not using the fix you sent and am using the latest master of Emacs 30.0.50 and Org 9.7.10

>  Maybe something is setting `print-level' per-buffer?
>  

(Don't have access rn; Holiday weekend here…) 

I will check but I don't set `print-level' anywhere in my code and it's `let' bound in the org-persist code. I'll do some digging on where things go bad when I get home. My gut feeling is that the damage is done elsewhere and doesn't manifest itself until it's persisted.

>  --
>  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:[~2024-08-31 14:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01  1:18 31.0.50; Org Persist file formatting Michael Mauger
2024-07-08 15:46 ` Ihor Radchenko
2024-07-08 17:29   ` Michael Mauger
2024-07-08 17:40     ` Ihor Radchenko
2024-07-25  3:28       ` Michael Mauger
2024-08-25  7:32         ` Ihor Radchenko
2024-08-30  3:08           ` Michael Mauger
2024-08-31 14:44             ` Ihor Radchenko
2024-08-31 14:58               ` Michael Mauger [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='8ILFtc_1-n1gBnSbTgZbG42wVVcKPZsz-9Wmjx3EzEPhz06N68_2boKsuw8wwfH-dWmk-Nl-ZMQ108S5C0weVL0BJ7uRyTB5Y-UNuTTkAeY=@protonmail.com' \
    --to=michael.mauger@protonmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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).