From: Andreas Schwab <schwab@suse.de>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 28875@debbugs.gnu.org
Subject: bug#28875: 25.3.50; set-default-file-modes ignores execution bits
Date: Fri, 20 Oct 2017 09:53:19 +0200 [thread overview]
Message-ID: <8760bajlw0.fsf@linux-m68k.org> (raw)
In-Reply-To: <878tg6ecpx.fsf@gmail.com> (Tino Calancha's message of "Fri, 20 Oct 2017 12:10:18 +0900")
On Okt 20 2017, Tino Calancha <tino.calancha@gmail.com> wrote:
> diff --git a/src/fileio.c b/src/fileio.c
> index b7df38c857..d707bfc1c6 100644
> --- a/src/fileio.c
> +++ b/src/fileio.c
> @@ -3125,7 +3125,11 @@ symbolic notation, like the `chmod' command from GNU Coreutils. */)
> DEFUN ("set-default-file-modes", Fset_default_file_modes, Sset_default_file_modes, 1, 1, 0,
> doc: /* Set the file permission bits for newly created files.
> The argument MODE should be an integer; only the low 9 bits are used.
> -This setting is inherited by subprocesses. */)
> +This setting is inherited by subprocesses.
> +
> +Note that some functions (e.g., `write-region') ignore the execution
> +bits in MODE. In that case you need first to create the file,
> +and then set the permisions with `set-file-modes'. */)
The umask cannot broaden the permissions, only restrict them. The zero
bits specify the bits that are always cleared from the mode, the one
bits leave them unmodified.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2017-10-20 7:53 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
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 [this message]
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=8760bajlw0.fsf@linux-m68k.org \
--to=schwab@suse.de \
--cc=28875@debbugs.gnu.org \
--cc=tino.calancha@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.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).