That's interesting. Well my sync settings already seems to be off, but
when I was having issues, it was working just like you described.
I'm not sure if I'm supposed to create a new Mintty issue or wait for
Thomas to reply.
On Fri, Jun 7, 2019 at 5:41 PM Doug Henderson wrote:
> On Fri, 7 Jun 2
On Fri, 7 Jun 2019 at 11:33, Academy OfFetishes wrote:
>
> I have the same problem with 3.0.0.
>
> Sorry for slowly dripping out information (I promise that's not my intent),
> but I will say, as soon as I created this user account on windows, I had
> copy and paste issues that were outside of cygw
I have the same problem with 3.0.0.
Sorry for slowly dripping out information (I promise that's not my intent),
but I will say, as soon as I created this user account on windows, I had
copy and paste issues that were outside of cygwin. I recall copying text
from firefox and not being able to past
Version 2.5-1 of "weechat" has been uploaded.
ChangeLog:
https://weechat.org/files/changelog/ChangeLog-2.5.html
DESCRIPTION
WeeChat is a fast, light and extensible chat client. It runs on many platforms
like Linux, Unix, BSD, GNU Hurd, Mac OS X and Windows (bash/ubuntu and
cygwin).
HOMEPAGE
htt
While testing some new pipe code, I'm occasionally seeing a timerfd deadlock:
The main thread is stuck in timerfd_tracker::dtor at timerfd.cc:354, waiting
for
the timerfd thread to close; and the timerfd thread is stuck at timerfd.cc:140,
waiting to acquire a mutex that's held by timerfd_tracke
On 07/06/2019 12:22, JonY wrote:
On 6/7/19 10:04 AM, Michael Haubenwallner wrote:
Hi,
so I'm encountering a strange problem related to object file order passed to
the linker, with any binutils and gcc version available to setup-x86_64.exe:
$ cat weak-func.c
extern void weakfunc() __attribute__
On 6/7/19 10:04 AM, Michael Haubenwallner wrote:
> Hi,
>
> so I'm encountering a strange problem related to object file order passed to
> the linker, with any binutils and gcc version available to setup-x86_64.exe:
>
> $ cat weak-func.c
> extern void weakfunc() __attribute__((weak));
> void weakf
Hi,
so I'm encountering a strange problem related to object file order passed to
the linker, with any binutils and gcc version available to setup-x86_64.exe:
$ cat weak-func.c
extern void weakfunc() __attribute__((weak));
void weakfunc() {}
$ cat weak-main.c
extern void weakfunc() __attribute__(
On Fri, 7 Jun 2019 09:41:45, Thomas Wolff wrote:
> Am 07.06.2019 um 01:04 schrieb Houder:
[snip]
> > I cannot say anything sensible about the 2 scripts you have executed. Sorry.
> >
> > But I am afraid, that you may have to start from scratch again (reinstalling
> > W10) in order to find out unde
Am 07.06.2019 um 01:04 schrieb Houder:
On Thu, 6 Jun 2019 15:26:25, Academy OfFetishes wrote:
inline
On Thu, Jun 6, 2019 at 12:56 PM Houder wrote:
On Thu, 6 Jun 2019 10:56:28, Academy OfFetishes wrote:
Well first of all, is this feature supposed to work by default or is it
something you
On Jun 6 15:13, Stanislav Kascak wrote:
> > > [...]
> > > I played around a bit and I can confirm it would be consistent with
> > > current behavior:
> > > memwrite <0 - filesize) - no error, written to file
> > > memwrite > > memwrite <4k, 64k) - SIGSEGV
> > > memwrite <64k, mmap alloc size) - S
11 matches
Mail list logo
