From: No Wayman <firstname.lastname@example.org> To: email@example.com Cc: firstname.lastname@example.org Subject: Re: Bug: org-babel-tangle: persmission denied when tangling [9.4.5 (9.4.5-gbc2659 @ /home/n/.emacs.d/straight/build/org/)] Date: Tue, 04 May 2021 15:33:10 -0400 Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Sébastien Miquel <email@example.com> writes: > Hi, > > No Wayman writes: >> I'm tangling my early-init/init.el with the :tangle-mode header >> arg set to >> (identity (#o444)). > This should be `(identity #o444)` I believe ? > Apologies, I transcribed that incorrectly. I do have `(identity #o444)`. > File permissions are now set before writing to the file, for > security > reasons. In this case, you remove write permission so emacs > fails to > write to the file. Perhaps we should try to support this use > case. > > However, even with the previous version, it seems that > subsequent > tangles should have failed (emacs should fail to delete the > previous > tangled file). Can you confirm this and explain how you dealt > with it ? Subsequent tangles did not fail for me. I just tested by building Org from a2cb9b853's parent: f84033b08. Multiple tangles work with no permission errors on subsequent tangles. Here's my init.org, if that's useful: https://raw.githubusercontent.com/progfolio/.emacs.d/master/init.org > As a workaround, you could use a file-local > `org-babel-post-tangle-hook` to set file permission. Although > subsequent tangles will still fail. Unfortunately, I don't have much use for the workaround if subsequent tangles will fail. I currently have an after-save-hook function which tangles the files if I've edited any of the src blocks. It's very convenient and I often will edit/tangle files set up like this multiple times.
next prev parent reply other threads:[~2021-05-04 19:46 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-04 18:26 No Wayman 2021-05-04 19:25 ` Sébastien Miquel 2021-05-04 19:33 ` No Wayman [this message] 2021-05-04 20:27 ` Sébastien Miquel 2021-05-04 20:32 ` Bastien 2021-05-04 21:19 ` Sébastien Miquel 2021-05-05 3:15 ` No Wayman 2021-05-05 6:49 ` Bug: [PATCH] " Sébastien Miquel 2021-05-05 7:03 ` Bastien 2021-05-05 13:53 ` No Wayman 2021-05-05 6:43 ` Bug: " Bastien
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://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 \ /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
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 list/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 list list/ https://orgmode.org/list \ firstname.lastname@example.org public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git