From: Tino Calancha <tino.calancha@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: 28875@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#28875: 25.3.50; set-default-file-modes ignores execution bits
Date: Tue, 17 Oct 2017 23:25:07 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1710172322300.17744@calancha-pc> (raw)
In-Reply-To: <mvminfd50s4.fsf@suse.de>
On Tue, 17 Oct 2017, Andreas Schwab wrote:
> On Okt 17 2017, Tino Calancha <tino.calancha@gmail.com> wrote:
>
>> emacs -Q:
>> (let ((foo (make-temp-file "foo")) mode)
>> (with-file-modes #o755 (write-region "" nil foo nil 0))
>> ;; (set-file-modes foo #o755)
>> (setq mode (nth 8 (file-attributes foo)))
>> (delete-file foo) mode)
>> => "-rw-------"
>>
>> To set foo file permissions to "-rwxr-xr-x" I need uncomment
>> (set-file-modes foo #o755) above.
>> Why? Is for security reasons?
>
> make-temp-file already creates the file (with restrictive modes), so
> with-file-modes has no effect (write-region does not change the mode of
> existing files). But write-region also never sets the x bits in the
> first place, it uses #o666 as the base mode.
>
Thank you for th enice explanation. I understand now.
I think I was fooled by the docstring of `set-default-file-modes':
"Set the file permission bits for newly created files..."
I thought that setting will be used by the functions in my snippet.
next prev parent reply other threads:[~2017-10-17 14:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 13:11 bug#28875: 25.3.50; set-default-file-modes ignores execution bits Tino Calancha
2017-10-17 14:03 ` Andreas Schwab
2017-10-17 14:25 ` Tino Calancha [this message]
2017-10-20 3:10 ` Tino Calancha
2017-10-20 7:15 ` Eli Zaretskii
[not found] ` <ef2bbaf3-7c6b-56a8-32ac-c5366d7431e7@gmail.com>
2017-10-20 8:42 ` Eli Zaretskii
[not found] ` <0a5e94fd-6c38-b022-5219-449f5e90c261@gmail.com>
[not found] ` <83bmks7l1p.fsf@gnu.org>
2017-10-27 14:02 ` Tino Calancha
2017-10-27 17:22 ` Eli Zaretskii
2018-07-10 6:45 ` Tino Calancha
2017-10-20 7:53 ` Andreas Schwab
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1710172322300.17744@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=28875@debbugs.gnu.org \
--cc=schwab@suse.de \
/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.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).