On Tue, 31 Mar 2015, Emmanuele Bassi wrote:
Hi;
On 31 March 2015 at 21:58, Allin Cottrell wrote:
so I was wondering if for 3.18/2.46 if we should drop XP. I think it would
make our life easier and anyway why do we need to support something that
microsoft is also not supporting?
For 3.18 t
Hi;
On 31 March 2015 at 21:58, Allin Cottrell wrote:
>> so I was wondering if for 3.18/2.46 if we should drop XP. I think it would
>> make our life easier and anyway why do we need to support something that
>> microsoft is also not supporting?
>
>
> For 3.18 that sounds fine. But why 2.46? I mea
On Tue, 31 Mar 2015, Ignacio Casal Quinteiro wrote:
Hey folks,
so I was wondering if for 3.18/2.46 if we should drop XP. I think it would
make our life easier and anyway why do we need to support something that
microsoft is also not supporting?
For 3.18 that sounds fine. But why 2.46? I mean,
Hi;
I think that was the definite plan for this cycle, at the very least for GLib.
Ciao,
Emmanuele.
On 31 March 2015 at 21:41, Ignacio Casal Quinteiro wrote:
> Hey folks,
>
> so I was wondering if for 3.18/2.46 if we should drop XP. I think it would
> make our life easier and anyway why do we
Hey folks,
so I was wondering if for 3.18/2.46 if we should drop XP. I think it would
make our life easier and anyway why do we need to support something that
microsoft is also not supporting?
Cheers.
--
Ignacio Casal Quinteiro
___
gtk-devel-list mail
hi,
On Tue, Mar 31, 2015, at 03:48, Alexander Larsson wrote:
> In general, setting O_CLOEXEC is a nice thing to do, but doing so does
> not change the fundamental fact that you can't rely on it being set.
This is pretty much the entire point of this thread. I now consider
O_CLOEXEC as a 'nice to
On tis, 2015-03-31 at 09:48 +0200, Alexander Larsson wrote:
> On lör, 2015-03-21 at 20:57 -0400, Ryan Lortie wrote:
> > hi,
> >
> > On Sat, Mar 21, 2015, at 01:59, Jürg Billeter wrote:
> > > I would keep using O_CLOEXEC as it's as close as we can get to the
> > > behavior that should have been the
Hi, GTK team.
Mozilla is implementing vertical-writing spec [*1] to Gecko rendering
engine. But GTK has no API to add hint of vertical writing mode to
input method.
Other OS already has the following method / attribute for this case.
OSX / Cocoa
drawsVerticallyForCharacterAtIndex method
https:/
On lör, 2015-03-21 at 20:57 -0400, Ryan Lortie wrote:
> hi,
>
> On Sat, Mar 21, 2015, at 01:59, Jürg Billeter wrote:
> > I would keep using O_CLOEXEC as it's as close as we can get to the
> > behavior that should have been the default: don't implicitly inherit
> > file descriptors on exec.
> >
>
