From: Michael Gauland <mikelygee@gmail.com>
To: emacs-orgmode@gnu.org
Subject: source blocks mangled when edited
Date: Mon, 31 May 2021 15:39:54 +1200 [thread overview]
Message-ID: <e5e4e0cc-14a8-a9f8-6911-5244d77bab29@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
I've stared having trouble editing source blocks. When I use C-c ' to
edit block, the editing behaves as expected, but when I C-c ' to return
to the main org file, the code is altered in strange ways. I've had
trouble coming up with a really small example, but the attached file
seems to consistently demonstrate the problem, even when running emacs
without my settings.
The file has two identical source blocks. The first generally behaves
fine, though some lines get extra indentation.
The second suffers more serious distortions. For example, the first line
changes from "digraph G {" to "aph G {".
I've seen this with other types of code as well (at least SQL and json),
so it's not specific to dot.
I'm running emacs 26.1 on Debian 10.9, with org build from git.
I'm not even sure how to start tracking this down. Any help would be
greatly appreciated!
Kind regards,
Mike Gauland
[-- Attachment #2: bug.org --]
[-- Type: text/plain, Size: 1326 bytes --]
#+BEGIN_SRC dot :file diagram1.png :cmdline -Kdot -Tpng
digraph G {
rankdir = "LR"
pre [label="Preprocessor"]
subgraph cluster_inputs {
label="Inputs"
rankdir = "TB"
input1 [label="input"]
input2 [label="input"]
input3 [label="∙\n∙\n∙",shape=none]
input4 [label="input"]
} -> pre
pre -> final
subgraph users {
rankdir="TB"
"End Users"
"Resellers"
"Corporate Users"
}
final -> "End Users"
final -> "Resellers"
final -> "Corporate Users"
}
#+END_SRC
#+BEGIN_SRC dot :file diagram2.png :cmdline -Kdot -Tpng
digraph G {
rankdir = "LR"
pre [label="Preprocessor"]
subgraph cluster_inputs {
label="Inputs"
rankdir = "TB"
input1 [label="input"]
input2 [label="input"]
input3 [label="∙\n∙\n∙",shape=none]
input4 [label="input"]
} -> pre
pre -> final
subgraph users {
rankdir="TB"
"End Users"
"Resellers"
"Corporate Users"
}
final -> "End Users"
final -> "Resellers"
final -> "Corporate Users"
}
#+END_SRC
next reply other threads:[~2021-05-31 3:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 3:39 Michael Gauland [this message]
2021-05-31 4:21 ` source blocks mangled when edited 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
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 \
--in-reply-to=e5e4e0cc-14a8-a9f8-6911-5244d77bab29@gmail.com \
--to=mikelygee@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).