On Tue, 5 Jun 2018 20:18:59, Frank Farance wrote:
No, I'm not suggesting that one must be subscribed, I'm pointing out that if
one wants to have a back and forth discussion (in a practical sense), some
kinda registration/subscription system is necessary.
No, its not? did not you read my post?
On 2018-06-05 20:04, Steven Penny wrote:
[...]
If OP is suggesting people can only reply if they are subscribed, then I am not
a fan of that.
No, I'm not suggesting that one must be subscribed, I'm pointing out that if
one wants to have a back and forth discussion (in a practical sense),
On Tue, 5 Jun 2018 13:38:14, Erik Soderquist wrote:
I have seen many people (and have done this myself before I
subscribed) participate in the discussion of their specific topic on
the list without subscribing by watching the public archive of the
list for updates to their topics and crafting
On 05/29/2018 05:32 PM, Alberto Escrig Vidal wrote:
>
> Thanks so much Jon!
>
>
> I have noticed a couple of issues with g++-7.
>
>
> 1)
>
>
> #include
> #include
> #include
>
> int main()
> {
> std::string Str;
> std::stringstream ss("hello");
> std::getline(ss,Str);
> std::cout <<
On 12/10/2017 18:23, Jon Turney wrote:
The following package has been updated in the Cygwin distribution:
* gdb-7.12.1-2
The GNU debugger allows you to debug programs written in C, C++, and
other languages, by executing them in a controlled fashion and printing
their data.
Changes since
On 6/5/2018 10:32 PM, Ivan Shynkarenka wrote:
Hello
I use x64 bit Cygwin and it failed in my home, work and Appveyor. I add
cygcheck.out with my environment.
I'm sorry about misspell prefix space in my prev example. Please try the
following one:
#include
#include
int main(int argc,
Hello
I use x64 bit Cygwin and it failed in my home, work and Appveyor. I add
cygcheck.out with my environment.
I'm sorry about misspell prefix space in my prev example. Please try the
following one:
#include
#include
int main(int argc, char** argv)
{
std::string line;
On 6/5/2018 6:19 PM, Paul Sheer wrote:
20 years ago Linux cult members were using the same
"blame-the-user"-type arguments.
Nothing has changed.
Please refrain from rants.
You paid us nothing and we support you on our free time
I don't need to do ANY analysis or tests to see that the
On 6/5/2018 9:12 PM, Hans-Bernhard Bröker wrote:
Am 05.06.2018 um 17:56 schrieb Ivan Shynkarenka:
Hello,
I found an issue with Cygwin GCC 7.3.0 when building with -std=gnu++17
flag.
Using Cygwin 32-bit or 64-bit? I have to ask because I could not
reproduce your problem here, on the 64-bit
Am 05.06.2018 um 17:56 schrieb Ivan Shynkarenka:
Hello,
I found an issue with Cygwin GCC 7.3.0 when building with -std=gnu++17
flag.
Using Cygwin 32-bit or 64-bit? I have to ask because I could not
reproduce your problem here, on the 64-bit version.
Build: g++ -std=gnu++17 test.cpp
The following packages have been updated in the Cygwin distribution:
*** xorg-server-1.20.0-2
*** xorg-server-common-1.20.0-2
*** xorg-server-debuginfo-1.20.0-2
*** xorg-server-devel-1.20.0-2
*** xorg-server-dmx-1.20.0-2
*** xorg-server-extra-1.20.0-2
*** xorg-server-xorg-1.20.0-2
***
Some more imput: Problem (1) is related to getline. I prepared this minimal
example after disecting a program that parses a text file which aborted under
cygwin (despite it worked well compiled with g++-7 under ubuntu).
Thanks for the patch for problem (2) Ken!
On Mon, Jun 4, 2018 at 4:13 PM, Frank Farance wrote:
> Third, I believe a registration mechanism (just your E-mail address) is
> necessary for discussion: How would you be getting follow-up messages if
> you're not on the list? And E-mail clients may prefer Reply-To-List rather
> than Reply-All,
Hi David,
Thanks for the suggestion. Unfortunately, toggling the input method does
not make a difference in an xterm window. (It does, by the way, have the
effect you mention in a Cygwin64 terminal window.)
--- Matt
On Mon, Jun 4, 2018 at 7:21 PM, David Billinghurst
wrote:
> On 2018-06-05
20 years ago Linux cult members were using the same
"blame-the-user"-type arguments.
Nothing has changed.
I don't use Emacs. I only gave it as an easily-testable example.
Try: apt-get install xemacs ; export DISPLAY=windows.mylan:0.0 ;
xemacs
Professionally, I have been a C++ developer
Hi,
I am curious to know if you would be interested in acquiring Salesforce
Users List.
Information fields: Names, Title, Email, Phone, Company Name, Company URL,
Company physical address, SIC Code, Industry, Company Size (Revenue and
Employee).
We also have related product users like:
Paul Sheer wrote:
Maybe you aren't familiar with 'X'. X is just a graphical
transport. It doesn't have menus unless some other program puts them up.
Try 'X' on linux -- running it from startX from a console and see
how easy it is to use.
NetSarang commercial X server has
Hello,
I found an issue with Cygwin GCC 7.3.0 when building with -std=gnu++17
flag.
The following test.cpp shows the issue:
#include
#include
int main(int argc, char** argv)
{
std::string line;
std::ifstream stream(" test.cpp");
while (getline(stream, line))
std::cout <<
Greetings, Marco Atzeri!
> It seems that Xterm, and I assume the all X server,
> is using a different Keyboard layout than Mintty.
> One with dead-keys.
Thanks for the hint, this is not limited to X server only, but plagues other
remote control systems under win10 as well (RManSys, TeamViewer)
> Maybe you aren't familiar with 'X'. X is just a graphical
> transport. It doesn't have menus unless some other program puts them up.
> Try 'X' on linux -- running it from startX from a console and see
> how easy it is to use.
>
NetSarang commercial X server has configuration menus to
On 06/05/2018 03:05 PM, Michael Haubenwallner wrote:
> Hi,
>
> I'm using attached patch for a while now, and orphan cygpid.N shared memory
> instances are gone for otherwise completely unknown windows process ids.
>
> However, I do see defunct processes now which's PPID does not exist (any
>
Hi,
I'm using attached patch for a while now, and orphan cygpid.N shared memory
instances are gone for otherwise completely unknown windows process ids.
However, I do see defunct processes now which's PPID does not exist (any more),
causing the same trouble because their windows process handle
On 6/4/2018 5:54 PM, Duncan Roe wrote:
> On Mon, Jun 04, 2018 at 04:26:57PM -0400, Jeffrey Altman wrote:
>>
>> My mail servers regularly categorize cygwin at cygwin.com mail as spam.
>>
>> And then there is all of the mail that simply gets rejected because of
>> DMARC policies applied by the
Hi Corinna,
On 29 May, 18:44, Corinna Vinschen wrote:
Hi Sergejs,
On May 25 17:43, Sergejs Lukanihins wrote:
> Hello,
>
> Looks like ch.stacklimit wasn't being page-aligned correctly in
> fork.cc; you need to subtract 1 from page_size to do it correctly (see
> the attached patch).
>
> As a
On Jun 4 15:36, Ken Brown wrote:
> ---
> winsup/cygwin/include/cygwin/version.h | 3 ++-
> winsup/cygwin/release/2.10.1 | 1 +
> winsup/doc/posix.xml | 1 +
> 3 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/winsup/cygwin/include/cygwin/version.h
>
On Jun 4 15:36, Ken Brown wrote:
> Commit ebd645e on 2001-10-03 made environ.cc:_addenv() add unneeded
> space at the end of the environment block to "work around problems
> with some buggy applications." This clutters the code and is
> presumably no longer needed.
> ---
>
On Jun 4 16:35, Ken Brown wrote:
> On 6/4/2018 3:36 PM, Ken Brown wrote:
> > Following glibc, interpret this as meaning the environment is empty.
>
> Sorry, please hold off on reviewing this patch. I just noticed that I
> missed at least one place (build_env()) where environ==NULL could cause a
Hi Ken,
On Jun 4 15:36, Ken Brown wrote:
> This is a followup to https://cygwin.com/ml/cygwin/2018-05/msg00334.html.
>
> In this patch series I attempt to implement the glibc extension
> clearenv(). I also implement glibc's notion of environ==NULL being
> shorthand for an empty environment.
>
On Jun 4 15:36, Ken Brown wrote:
> ---
> winsup/cygwin/environ.cc | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/winsup/cygwin/environ.cc b/winsup/cygwin/environ.cc
> index 43225341c..b452d21a5 100644
> --- a/winsup/cygwin/environ.cc
> +++
Am 05.06.2018 um 06:03 schrieb Marco Atzeri:
On Mon, Jun 4, 2018 at 5:47 PM, Matt Nicholas wrote:
...
I start Cygwin/X as follows:
(1) open a Cygwin64 Terminal window
(2) cd /usr/bin
(3) ./xinit -- -multiwindow &
That works as expected, and creates an initial xterm window. I can then
30 matches
Mail list logo
