From: "Sébastien Miquel" <email@example.com> To: Michael Gauland <firstname.lastname@example.org>, email@example.com Subject: Re: source blocks mangled when edited Date: Mon, 31 May 2021 09:42:08 +0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Michael Gauland writes: > I didn't instrument the functions, but found that there are two places > that test '(if (version< emacs-version "26.1"...'. If I change that to > use "version<=", the problem goes away (I'm still running 26.1). I don't > know whether this is the right fix (the underlying problem may be a > quirk in my system, and this is just masking it). I'm hesitant to > submit a patch unless someone else can replicate the problem. The commit `d02ad1f207e1579aff8f36f740a065d71472c182` introduced the use of `replace-buffer-contents` when available. This function was introduced in emacs 26.1, hence the version tests. There must be an issue with the `replace-buffer-contents` calls. Can you call `trace-function` on `replace-buffer-contents` and trigger the behaviour again to see what it returns ? You said it also happens with `emacs -q`, right ? I'll try to see if I can reproduce with emacs 26.1 tomorrow. -- Sébastien Miquel
next prev parent reply other threads:[~2021-05-31 9:42 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-31 3:39 Michael Gauland 2021-05-31 4:21 ` Samuel Wales 2021-05-31 8:01 ` Michael Gauland 2021-05-31 8:15 ` Sébastien Miquel 2021-05-31 8:54 ` Michael Gauland 2021-05-31 9:42 ` Sébastien Miquel [this message] 2021-05-31 10:02 ` Michael Gauland 2021-06-01 8:20 ` [PATCH] " Sébastien Miquel 2021-06-27 13:54 ` Nicolas Goaziou
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: source blocks mangled when edited' \ /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 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).