Re: How to change default umask in Stretch?
Henrique de Moraes Holschuh: > Note that the ideal implementation would
be to inherit the umask [...] Jonathan de Boyne Pollard: > Actually, the
ideal implementation from the GNOME point of view would be for > these
programs to pass the umask from the client process to the server, just >
like they pass open file handles, the working directory, environment >
variables (including DISPLAY), and the arguments vector. > >
* https://github.com/GNOME/gnome-terminal/blob/52f32f962a5ed34f8c31042f2f8276dc1710cc99/src/terminal.c#L317
>
* https://github.com/GNOME/glib/blob/b51a0e7c63313ecfc0c6bbb9f2a8d99f193e51ea/gio/gapplication.c#L923
Henrique de Moraes Holschuh: > You'd have to always indirectly start an
intermediate "gnome launcher" > thing (instead of the real program) that
sets up the environment, then > exec the real program for that to work.
No, that would not be necessary at all. Think about how GNOME Terminal
and GNOME Editor work. As I said: These are already passing a whole
bunch of process state from the client to the server, in order to
preserve things like the apparent semantics of GNOME Terminal windows
"inheriting" the working directories of the invoking clients, when in
reality there is no inheritance from those client processes going on at
all. This would be just one more such item of process state.
Reply to: