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: Mon, 08 Jul 2024 17:29:58 +0000	[thread overview]
Message-ID: <CUcZrwnsXw0XEbAs9PM-vpfzpnkJAZMVsZ740Xe2b5OlVzNvpL3d7fT-AUKE-EBJcNSavjUsEd_zI-kOkkbtkc0wHmtlaAzS2kmpmd-6mQI=@protonmail.com> (raw)
In-Reply-To: <87r0c3zy1d.fsf@localhost>

On Monday, July 8th, 2024 at 11:45 AM, Ihor Radchenko <yantar92@posteo.net> wrote:

> Michael Mauger michael.mauger@protonmail.com writes:
> 
> > This bug has been difficult to reproduce but several people have
> > encountered it, or symptoms of it. Most recently, there has been this
> > thread on Reddit:
> > https://www.reddit.com/r/emacs/comments/1drxsz6/tangled_0_code_blocks_from_filename_problem/
> > 

Just encountered it again. :( The recipe is still not obvious but I'm trying to find one... 
(This time got the "\..." version)

> > After some poking around I started getting failure when I tried to
> > reopen an Org file or ran `normal-mode' on it. Shutting down emacs 
> > and restarting cleared the issue. When the issue arose when reopening 
> > the file within a session, the backtrace was pointing to` plistp' failing in
> > `org-persist-read'. When I looked at the persist index there were
> > entries like:
> > 
> > (:container
> > ((elisp org-element--headline-cache) (elisp org-element--cache)
> > (version "2.3"))
> > :persist-file "49/605653-361a-49a4-a000-47db8d522096" :associated
> > (:hash "aa1176747642fdac45aaf96095a88367" :file
> > "/home/michael/Projects/my-config/emacs/my-org.org" :inode
> > 2554490)
> > :expiry 30 :last-access 1719791738.4428508 :last-access-hr
> > "2024-06-30T19:55:38-0400" ...)
> > 
> > (Note: the "..." in the last entry; sometimes it showed up as "\...".)
> 
> 
> This is curious. May it be that you have non-default value of
> `pp-default-function'?
> 

I don't touch `pp-default-function' and I've confirmed that it is 
set to `pp-fill' in my instance.

> --
> Ihor Radchenko // yantar92,
> Org mode contributor,

Thanks for your attention.


  reply	other threads:[~2024-07-08 17:31 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 [this message]
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

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='CUcZrwnsXw0XEbAs9PM-vpfzpnkJAZMVsZ740Xe2b5OlVzNvpL3d7fT-AUKE-EBJcNSavjUsEd_zI-kOkkbtkc0wHmtlaAzS2kmpmd-6mQI=@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).