Hi list.
Is it possible to specify unequal increments or decrements in
scale/range/spinbuttons or adjustments?
By that I mean, for example, if the up-arrow of a spin button is
pressed, instead of increasing the value by a fixed increment, I change
it by arbitrary values - say the value changes
On 03/20/2015 01:43 PM, Ryan Lortie wrote:
karaj,
For those unfamiliar with the issue: when a process is created on UNIX
via naive fork() and exec(), the default is that the process will
inherit all of the file descriptors of the parent. This makes a lot of
sense for stdin, stdout and stderr,
On Fri, Mar 20, 2015 at 7:29 PM, Christian Hergert christ...@hergert.me
wrote:
This makes me happy. I don't think I've actually seen any of this stuff
handled right. Not to mention that close() itself is basically broken in
multi-threaded scenarios on Linux (Linus says to basically just not
So, you found that dup3 doesn't do what you want, and now you want to
throw out the baby with the bathwater and just say I don't care
anymore if we leak fds ?
On Fri, Mar 20, 2015 at 4:43 PM, Ryan Lortie de...@desrt.ca wrote:
karaj,
For those unfamiliar with the issue: when a process is
On Fri, Mar 20, 2015, at 20:29, Christian Hergert wrote:
What I would welcome, is a function that says glib, close all FDs you
know about or that you created. If all the libraries did that, at least
it would be possible for applications to maybe, sorta, do the right
thing. (That would push
On Fri, Mar 20, 2015, at 23:33, Matthias Clasen wrote:
So, you found that dup3 doesn't do what you want, and now you want to
throw out the baby with the bathwater and just say I don't care
anymore if we leak fds ?
dup3() was a bit of a straw that broke the camel's back case. I could
point at
Sorry, I'm not overly familiar with this sort of stuff.
Right now, we use raw fork/exec in mutter where we need to do some tricky
management and explicitly leak an FD into the correct place [0]. Does this
mean that from now on, glib might leak an FD and we need to be prepared to
handle that?
hi,
On Sat, Mar 21, 2015, at 01:19, Jasper St. Pierre wrote:
Right now, we use raw fork/exec in mutter where we need to do some tricky
management and explicitly leak an FD into the correct place [0]. Does
this
mean that from now on, glib might leak an FD and we need to be prepared
to
handle
On 15-03-20 10:07 AM, Roger Davis wrote:
Hi Jim Konstantin,
I can now add another data point on this topic. My boss bought me a
nice new iMac 27 Retina which arrived a couple days ago (yayy
boss!!), so I decided to do my first ever X11-free quartz-only gtk3
MacPorts install (agh
hi,
On Sat, Mar 21, 2015, at 01:27, Jürg Billeter wrote:
Doesn't the following standard POSIX functionality provide what you
want?
fcntl(fd, F_DUPFD_CLOEXEC, 0)
Yes. It does. Thank you very much.
It seems that this is a (slightly) recent addition. It's documented:
Hi Jim Konstantin,
I can now add another data point on this topic. My boss bought me a nice
new iMac 27 Retina which arrived a couple days ago (yayy boss!!), so I
decided to do my first ever X11-free quartz-only gtk3 MacPorts install
(agh gtk3-on-quartz!!). I am now seeing your menu
11 matches
Mail list logo
