From: No Wayman <iarchivedmywholelife@gmail.com>
To: sebastien.miquel@posteo.eu
Cc: Bastien <bzg@gnu.org>, Tom Gillespie <tgbugs@gmail.com>,
emacs-orgmode@gnu.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 23:15:10 -0400 [thread overview]
Message-ID: <87y2ctlviu.fsf@gmail.com> (raw)
In-Reply-To: <28c262ba-7816-a38f-8d1d-c4d6d880d2e2@posteo.eu>
Sébastien Miquel <sebastien.miquel@posteo.eu> writes:
> Hi Bastien,
>
> Bastien writes:
>> I tried to apply this (transitory?) patch against maint and it
>> did not
>> apply. It applies okay on master. For bug fixes, please make
>> patches
>> againt the maint branch.
> This fixes a bug introduced by a commit in master. I've attached
> the same
> patch here, properly formated. I think it should be applied to
> master.
>
> It reverts a part of a2cb9b853: permissions are no longer set
> before writing
> to the tangled file.
>
> I've CC'd Tom, which made the original suggestion. I guess we
> could set the
> write and execute permissions before writing, and set the read
> permissions
> afterwards.
Another related bug to the changes:
I have the :tangle header-arg set to evaluate some elisp to return
the file name:
org-babel no longer interprets this elisp. It is being used
literally as the file name:
e.g.
Wrote /home/n/.emacs.d/(concat (file-name-sans-extension
(buffer-file-name)) ".el")
next prev parent reply other threads:[~2021-05-05 3:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 18:26 Bug: org-babel-tangle: persmission denied when tangling [9.4.5 (9.4.5-gbc2659 @ /home/n/.emacs.d/straight/build/org/)] No Wayman
2021-05-04 19:25 ` Sébastien Miquel
2021-05-04 19:33 ` No Wayman
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 [this message]
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2ctlviu.fsf@gmail.com \
--to=iarchivedmywholelife@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=sebastien.miquel@posteo.eu \
--cc=tgbugs@gmail.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
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).