Version 4.0.4-1 of "weechat" has been uploaded.
ChangeLog:
https://weechat.org/files/doc/weechat/ChangeLog-4.0.4.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).
HOMEPA
Hi Corinna,
Corinna Vinschen via Cygwin wrote:
On Aug 24 14:39, Mark Geisert via Cygwin wrote:
Denis Excoffier via Cygwin wrote:
Hello,
When i try to compile coreutils-9.3 under cygwin-3.4.8 i get the following
error messages (see below).
There seems to be a kind of loop in the hierarchy of #
> While select indicates that
> data can be written, it doesn't indicate how much data can be written.
> I. e., if select returns, and there's only buffer space for 10 bytes,
> and the send call tries to send 100 bytes, it *will* block, unless the
> socket is non-blocking and returns EAGAIN.
IIRC,
> it is not possible to diffentiate between Cygwin
> FIFOs and real FIFOs created from the remote side in `ls -l'
> output.
Why would that be necessary? If it's a FIFO, it can be used as a FIFO,
regardless where and how it was created..
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
Problem rep
On 2023-08-25, Jim Garrison via Cygwin wrote:
> On 8/25/2023 00:18, Backwoods BC via Cygwin wrote:
> [snip]
> >
> >I get borders around both active and inactive windows, but then I've
> >spent hours (probably days) messing with registry values in an attempt
> >to gain the kind of UI control that wa
Hi Corinna,
On Fri, 25 Aug 2023 12:50:56 +0200
Corinna Vinschen wrote:
> On Aug 25 17:48, Takashi Yano via Cygwin wrote:
> > This did not help. I looked into this deeper and noticed that:
> > 1) _win32_select() sometimes returns 0.
> > 2) If _win32_select() returns 0, WaitForMultipleObjects(..., I
On 8/25/2023 00:18, Backwoods BC via Cygwin wrote:
[snip]
I get borders around both active and inactive windows, but then I've
spent hours (probably days) messing with registry values in an attempt
to gain the kind of UI control that was built into XP. I don't know
which change I made that gave
On Fri, Aug 25, 2023 at 2:18 PM Corinna Vinschen via Cygwin
wrote:
>
> On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO,
> > instead it comes back as a symlink "myfifo.fifo -> ':\0:c4:1000'".
> >
> > AFAIK there are (at least) t
On Aug 25 14:23, Corinna Vinschen via Cygwin wrote:
> On Aug 25 12:08, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > > I don't have an answer to this problem yet.
> > >
> > > Can we use send(sock, "", 0) to reenable FD_WRITE, perhaps?
> >
> > Can't it just be assumed that the socket
On Aug 25 14:18, Corinna Vinschen via Cygwin wrote:
> On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> > 2. Check whether the filesystem for the fifos path is NFS
> > (cgywin.dll's |fs.fs_is_nfs()|), and then just refuse |mkfifo()| with
> > |ENOSYS| (not implemented)
>
> I like the idea.
EPERM,
On Aug 25 12:08, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > I don't have an answer to this problem yet.
> >
> > Can we use send(sock, "", 0) to reenable FD_WRITE, perhaps?
>
> Can't it just be assumed that the socket is _always_ writeable _unless_ the
> last send() failed?
> In o
On Aug 23 01:05, Roland Mainz via Cygwin wrote:
> Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO,
> instead it comes back as a symlink "myfifo.fifo -> ':\0:c4:1000'".
>
> AFAIK there are (at least) these two options to fix the problems:
> 1. Check whether the filesystem for the
> I don't have an answer to this problem yet.
>
> Can we use send(sock, "", 0) to reenable FD_WRITE, perhaps?
Can't it just be assumed that the socket is _always_ writeable _unless_ the
last send() failed?
In other words, try to always send() if it did not fail before. If it did,
only send() a
On Aug 25 17:48, Takashi Yano via Cygwin wrote:
> On Thu, 24 Aug 2023 10:59:33 +0200
> Corinna Vinschen wrote:
> > > I'm not sure why at all, however, the following patch seems to
> > > solve the issue.
> > >
> > > diff --git a/winsup/cygwin/select.cc b/winsup/cygwin/select.cc
> > > index 7b947384
On Aug 24 18:24, Martin Wege via Cygwin wrote:
> On Sat, Aug 19, 2023 at 10:15 AM ASSI via Cygwin wrote:
> >
> > Martin Wege via Cygwin writes:
> > > How can I find out whether the current Cygwin terminal has
> > > Administrator rights? I want to safeguard our admin scripts with a
> > > simple tes
On Aug 24 14:39, Mark Geisert via Cygwin wrote:
> Hi Denis,
>
> Thanks for the report. More below...
>
> Denis Excoffier via Cygwin wrote:
> > Hello,
> > When i try to compile coreutils-9.3 under cygwin-3.4.8 i get the following
> > error messages (see below).
> > There seems to be a kind of lo
On Thu, 24 Aug 2023 10:59:33 +0200
Corinna Vinschen wrote:
> > I'm not sure why at all, however, the following patch seems to
> > solve the issue.
> >
> > diff --git a/winsup/cygwin/select.cc b/winsup/cygwin/select.cc
> > index 7b9473849..de5794c9f 100644
> > --- a/winsup/cygwin/select.cc
> > +++
On 25/08/2023 08:18, Backwoods BC via Cygwin wrote:
> On Thu, Aug 24, 2023 at 10:54 PM Gary Johnson via Cygwin
> wrote:
>>
>> On 2023-08-25, Thomas Wolff via Cygwin wrote:
>>>
>>>
>>> Am 25.08.2023 um 02:41 schrieb Gary Johnson via Cygwin:
On 2023-08-24, Backwoods BC via Cygwin wrote:
>
On Thu, Aug 24, 2023 at 10:54 PM Gary Johnson via Cygwin
wrote:
>
> On 2023-08-25, Thomas Wolff via Cygwin wrote:
> >
> >
> > Am 25.08.2023 um 02:41 schrieb Gary Johnson via Cygwin:
> > >On 2023-08-24, Backwoods BC via Cygwin wrote:
> > >>On Thu, Aug 24, 2023 at 11:08 AM Jim Garrison via Cygwin
>
19 matches
Mail list logo
