RE: Cygwin on Win10 much slower than Win7

From: Stephen John Smoogen > Sent: Thursday, November 2, 2017 12:49 > To: cygwin@cygwin.com > Subject: Re: Cygwin on Win10 much slower than Win7 > > On 2 November 2017 at 12:44, Nellis, Kenneth <kenneth.nel...@conduent.com> > wrote: > > From: cyg Simple > >>

RE: Cygwin on Win10 much slower than Win7

From: cyg Simple > On 11/2/2017 9:36 AM, Erik Bray wrote: > > On Wed, Nov 1, 2017 at 3:50 PM, Nellis, Kenneth wrote: > >> Since migrating from a Windows 7 laptop to one with Windows 10, I've > >> noticed a significant speed decrease in opening a mintty/bash window &

Cygwin on Win10 much slower than Win7

Since migrating from a Windows 7 laptop to one with Windows 10, I've noticed a significant speed decrease in opening a mintty/bash window from about 0.5s to 3.5s. I've narrowed it down to two bottlenecks in .bash_profile: to "cygpath" and "source". Each invocation of cygpath on Win10 takes

RE: ISO boost library help

From: Marco Atzeri > On 24/10/2017 19:25, Nellis, Kenneth wrote: > > Trying unsuccessfully (so far) to use the Cygwin-provided boost > > libraries. The only boost-related package I saw was boost-build, which > I've installed. > > > > may be libbost-devel ? &g

ISO boost library help

Trying unsuccessfully (so far) to use the Cygwin-provided boost libraries. The only boost-related package I saw was boost-build, which I've installed. $ cygcheck -c boost-build Cygwin Package Information Package VersionStatus boost-build 1.63.0-1 OK $ Google

setup complaining about shared-mime-info package

Dear Cygwin Community, Since I recently reinstalled Cygwin from Win7 to a clean Win10 machine, I have not been able to get around setup complaining about the following postinstall script error: Package: z/Perpetual zp_shared-mime-info.sh exit code 1 The given package, "z/Perpetual",

RE: lftp / zlib problems

From: Andrew Schulman > > > From: Harri T. > > > > Hi all, > > > > > > > > After updating Cygwin 32-bit we have had problems with all the > > > > combinations of lftp 4.7.7.-1 / 4.8.0-1 and zlib 1.2.8-3 / 1.2.11-1. > > > > ... > > > > assertion "ptr(x.heap_index)==" faSKiled: file > > > >

RE: chere install problem

From: Gluszczak, Glenn > "Hive not writable" sounds like permission for a registry key. > Mind you, Cygwin unloads the registry on a filesystem. > /proc/registry/HKEY_CURRENT_USER/ Thanx for the response. Digging deeper into Google, it turns out that I needed to launch mintty "as

chere install problem

Moving to a new machine with Windows 10 from an old machine with Windows 7, I am installing Cygwin from scratch. I am having trouble with package chere: $ cygcheck -c chere Cygwin Package Information Package VersionStatus chere1.4-1 OK $ chere -if -t

RE: lftp / zlib problems

From: Harri T. > Hi all, > > After updating Cygwin 32-bit we have had problems with all the > combinations of lftp 4.7.7.-1 / 4.8.0-1 and zlib 1.2.8-3 / 1.2.11-1. > ... > assertion "ptr(x.heap_index)==" faSKiled: file > "/home/ASchulma/dev/cygwin/lftp/lftp-4.8.0-1.i686/src/lftp- >

cygcheck -f reorders output

I found it surprising that the packages aren't listed in the order requested: $ cygcheck -f `which bash find grep xargs cygwin1.dll` bash-4.4.12-3 cygwin-2.9.0-3 findutils-4.6.0-1 findutils-4.6.0-1 grep-3.0-2 $ Adds a bit of challenge to match the output with the parameters. --Ken Nellis --

RE: i686-w64-mingw32-gcc -fstack-protector-strong

> From: Lee > ... > Was there ever a man page for cygcheck? I remember looking at one, > but maybe I it was https://cygwin.com/cygwin-ug-net/cygcheck.html ?? > $ man cygcheck > No manual entry for cygcheck > > $ info cygcheck > info: No menu item 'cygcheck' in node '(dir)Top' Both man and

RE: How to find out the current cygwin version?

From: David Billinghurst > On 8/09/2017 14:39, Ben Stover via cygwin wrote: > > > Assume I get to another (Windows) computer where Cygwin is already > installed. > > > > How can I find out which version of Cygwin is currently installed? > cygcheck --version # for cygwin dll > ...

RE: lftp 4.8.0-1

From: Nellis, Kenneth > From: From: Andrew Schulman > > lftp 4.8.0-1 is now available in Cygwin. This is a new upstream release, > > with minor enhancements and bug fixes. Please see > > http://lftp.tech/news.html for the list of changes. > > > > lftp is a so

RE: bash pipe fails in script with subshell/loop cmbination

> From: Eliot Moss > It also works for me. If it is not a version issue, then I > wonder about BLODA. Maybe anti-virus or similar tools are > wrapping process creation in such a way that things get > confused. Try cygcheck, etc. BTW, it also works for me. With so many Cygwin issues being

RE: lftp 4.8.0-1

> lftp 4.8.0-1 is now available in Cygwin. This is a new upstream release, > with minor enhancements and bug fixes. Please see > http://lftp.tech/news.html for the list of changes. > > lftp is a sophisticated file transfer program and ftp/http/bittorrent > client. It supports multiple network

RE: distinguishing cygwin from mingw binaries

From: Hans-Bernhard Bröker > That's a bit too rough. Something like > > cygcheck ./foo.exe | grep cygwin1.dll > orldd ./foo.exe | grep cygwin1.dll > > would be more precise. Appreciate the improved tests. Thanx! > > One of my wishes for Cygwin is for the "file" command to make the

distinguishing cygwin from mingw binaries

For my personal use, I use gcc to generate binaries, but occasionally I need to make a binary available to someone who doesn't use Cygwin. For that I use Cygwin's x86_64-w64-mingw32-gcc. After the fact, I would like to know whether the binary requires Cygwin support or not. One way is: strings

setup complains about cygwin-doc package update

Curious about an error that setup.exe reported today related to upgrading package cygwin-doc to 2.8.1-1, saying: Postinstall script errors These do not necessarily mean that affected packages will fail to function properly, but please check /var/log/setup.log.full and report any

RE: Compile/run problems on cygwin not solved by going to cygwin64

From: Wouter van Doorn > Hello all, > ... > Attachments: > - cygcheck.out for details of the installation > - installed.db with moreother details of the installation > - PML-files with details of runs as gathered by ProcMon (the 'thread > exit' after closing the file on cygwin1.lib MUST be the

RE: Updated: setup (2.880)

From: Csaba Raduly > I also couldn't reproduce your scenario. > ... > > Since it's reproducible for you, you could (if you're curious) run > wget with the -d (--debug) switch or break out the heavy artillery: > install Wireshark and look at the HTTP headers sent and received by > wget. Thanx,

RE: Window Maker issues, launching from cygwin

From: David DLC > $ startx > ... > /usr/bin/X :0 -auth /home/David Dela Cruz/.serverauth.9196 > ... > /etc/X11/xinit/xinitrc-common: line 20: [: too many arguments > Excessive file argument "Cruz/.Xresources" > 1 error in preprocessor. > /etc/X11/xinit/xinitrc: line 20: [: too many arguments >

RE: Updated: setup (2.880)

From: Andrey Repin > Doesn't matter what syntax I use, I'm unable to reproduce your effects. > ... > Get rid of intercepting proxies and your problem will go away as well. > It's not a matter of syntax. I'm unaware of any proxies involved. I haven't set any up. Don't even know how. Any proxies

RE: Updated: setup (2.880)

The folks who couldn't reproduce it were using different command syntax than I. Mine: wget -O setup-x86_64.exe http://cygwin.com/setup-x86_64.exe Theirs: wget https://cygwin.com/setup-x86_64.exe Why did I use that syntax? Because it was given in the OP,

RE: Updated: setup (2.880)

From: cygwin-announce-owner > > A new version of Setup, release 2.880, has been uploaded to > >https://cygwin.com/setup-x86.exe (32 bit version) >https://cygwin.com/setup-x86_64.exe (64 bit version) > ... > Please send bug reports, as usual, to the public mailing list cygwin AT >

UTF-8 compatibility between Windows and Cygwin

I have (BOM-less) UTF-8 text files that I can read fine in Cygwin, but not Windows. When I create text files in Windows containing non-ASCII characters, I cannot read them in Cygwin. I understand why, but wondering the best way to be able to share text files across the two environments. I'm

RE: setup-x86.exe default view

From: Sky Diver > Actually, the preferred user experience would be to: > 1. Start in Category view > 2. Select whatever packages to install/remove/etc. > 3. Click "Next" > 4. Have the Pending view show up in order to review whatever is going > to be installed. > 5. Have the option to Approve /

readshortcut fails on file name

I have a Windows shortcut with Unicode character U+2013 (EN DASH) in its name. readshortcut fails to read it, but if I rename it removing the EN DASH, readshortcut reads it correctly. $ readshortcut c-d.lnk readshortcut: Load failed on C:\cygwin\home\knellis\work\c-d.lnk $ mv c-d.lnk b.lnk $

RE: cygpath compatiblity break (v2.1 -> v2.7)

From: Chevallier Yves > ... > So two questions in this thread: > 1. How can I participate to the thread and use this mailing list properly? > ... > From: Brian Inglis > ... > Looks like the 207653 comes from the Return-Path header when > you view the raw message content. The answer

RE: [ANNOUNCEMENT] Updated: sqlite3-3.16.2-1 for Cygwin/Cygwin64

From: Jan Nijtmans [mailto:jan.nijtm...@gmail.com] > ... > B.T.W: You can leave "sqlite3" at 3.16.2 and still upgrade all other > related packages (such as libsqlite3_0) to 3.18. Then you will > have all new features, and still run the old shell (which is just a thin > wrapper around libsqlite3_0

RE: Missing announcements for screen?

From: Andrew Schulman > ... > I confess to forgetting or just skipping announcements sometimes. It's hard > for > me to tell that anyone cares about them, although I see that you do. I will > try > to do better, though I guess if you don't see one from me you can assume > nothing > important

RE: cygpath compatiblity break (v2.1 -> v2.7)

From: cyg Simple > I was going to state the same yesterday but I gave it a try first. The > resulting mail doesn't explain the use of cygwin-get.MSGID that I saw. > It mostly refers to the FAQ on cygwin.com. Well, there is the following. Not saying it is easy to find.

RE: cygpath compatiblity break (v2.1 -> v2.7)

From: Yves Chevallier > ... > How can I use this mailing list to answer a mail that I only find from > this [link](https://www.cygwin.com/ml/cygwin/2017-04/msg00156.html)? > ... Send a plain-text e-mail to cygwin-get.207...@cygwin.com. No need to add a subject or body. It will send you the

RE: can't break out of perl script during execute()

From: Nellis, Kenneth (Conduent) > I have a perl script that reads a (large) log file, searches for records > matching a certain pattern, and execute()s a binary passing in to it data > from the matched log record This message was sent prematurely. Please disregard. Apologies. --K

can't break out of perl script during execute()

I have a perl script that reads a (large) log file, searches for records matching a certain pattern, and execute()s a binary passing in to it data from the matched log record. Works great, except that I can't CTRL-C to break out when the perl script is executing the binary, which is where it

RE: pdf2djvu 0.9.5-1

From: Marco Atzeri > On 04/04/2017 22:42, Nellis, Kenneth (Conduent) wrote: > > From: cygwin-announce-owner cygwin com [...] On Behalf Of > Yaakov Selkowitz > >> > >> The following packages have been uploaded to the Cygwin distribution: > >> > >&g

RE: pdf2djvu 0.9.5-1

From: cygwin-announce-owner cygwin com [...] On Behalf Of Yaakov Selkowitz > > The following packages have been uploaded to the Cygwin distribution: > > * pdf2djvu-0.9.5-1 > > pdf2djvu creates DjVu files from PDF files. It's able to extract graphics, > text, hyperlinks, bookmarks, and

RE: inetutils-server, OpenSP and units install glitches and fixes

From: Ian Lambert via cygwin > ... > On a related note, using not ancient Red Hat 5.6 where the mirror is > stored, tar won't expand the Cygwin packages? > > $ tar -xvf units-2.13-1.tar.xz > > tar: This does not look like a tar archive > tar: Skipping to next header > tar: Archive contains

RE: Very Slow Setup Parsing / was Re: Segmentation Faults

From: Ian Lambert > ... > I missed the discussions of this "new" option, > and documentation is the last thing to be updated. > :) > https://cygwin.com/faq.html#faq.setup.cli It's also incorrect in saying that the listing is written to setup.log. It seems to write to stdout instead. --Ken

RE: [ANNOUNCEMENT] Updated: dash-0.5.9.1-1

From: Eric Blake > ... > Until then, I'm worried that there are > enough scripts in the wild that use bashisms and will therefore break if > /bin/sh is not bash, even though that number has reduced somewhat since > Debian made their switch. > ... I was thinking of testing my scripts by changing

RE: cygpath (reprised)

From: cyg Simple > On 2/21/2017 1:22 PM, Nellis, Kenneth (Conduent) wrote: > > I suppose one could argue that, by using -w, that cygpath might assume that > > it > > is converting *from* a POSIX path, and therefore the colon would not > > indicate > > a drive

cygcheck outputs CRLF

Looked, but didn't see this addressed in the archives... Just realized that cygcheck output contains DOS line endings forcing me to pipe it through d2u in certain applications. Wondering if this is intended or desired behavior. It is installed in /usr/bin, so I would expect to behave Unix-like.

RE: suggest adding posting dates to follows-up and references

> From: Eric Blake > Still, you'll need to forward this request to webmaster AT sourceware > DOT org, as the cygwin list readers are not the same people as those in > charge of maintaining the web pages. (see > https://sourceware.org/lists.html for the full set of archives that will > be impacted

RE: suggest adding posting dates to follows-up and references

From: Eric Blake [mailto:ebl...@redhat.com] > Well, according to the bottom of > https://cygwin.com/ml/cygwin/2017-02/index.html, the Cygwin mailing list > archives are run by MHonArc software, so it would be a feature request > to MHonArc (https://www.mhonarc.org/) followed by getting the

RE: suggest adding posting dates to follows-up and references

From: Eric Blake > On 02/22/2017 08:27 AM, Nellis, Kenneth (Conduent) wrote: > > FWIW, here's a change that I would find beneficial: > > > > At the bottom of a post, which is either a reply and/or has a follow-up, > > we see something like the following example: >

suggest adding posting dates to follows-up and references

FWIW, here's a change that I would find beneficial: At the bottom of a post, which is either a reply and/or has a follow-up, we see something like the following example: • Follow-Ups: ◦ Re: Hangs on connect to UNIX socket being listened on in the same process (was: Cygwin hanging in

RE: cygpath (reprised)

From: Andrey Repin > > But, consider the following: > > > $ cygpath -w a:b | od -An -tx1c > > 41 3a 62 0a > >A : b \n > > $ > > > Instead of the special character colon (:), shouldn't cygpath be showing > > something in the Unicode Private Use area? > > No, it shouldn't. > You've

cygpath (reprised)

I followed and understood the discussion to all the recent cygpath postings, so I understand and expect the following: $ cygpath -w 'a*b' | od -An -tx1c 61 ef 80 aa 62 0a a 357 200 252 b \n $ But, consider the following: $ cygpath -w a:b | od -An -tx1c 41 3a 62 0a A :

RE: cygpath

From: Corinna Vinschen > On Feb 13 17:29, Nellis, Kenneth (Conduent) wrote: > > From: Andrey Repin > > > See > > > http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars > > > > This reference says: > > ... > > I

RE: cygpath

From: Andrey Repin > See > http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars This reference says: > All of the above characters, except for the backslash, are converted to > special UNICODE characters in the range 0xf000 to 0xf0ff (the "Private > use area") when

RE: [ANNOUNCEMENT] Updated [test]: sed-4.4-1

From: Steven Penny > Perhaps I am missing something, but cant all that be said about Sed too? I > just cant see a situation where we are justified changing one and not the > other. They should either both strip carriage returns or neither. How about grep? $ printf 'hello\r\nworld\r\n' | grep

Please report this problem to the public mailing list...

We have received several postings of people responding to the Cygwin-generated message: WARNING: ... Please report this problem to the public mailing list cygwin@cygwin.com. I wonder how many places such messages are present in the Cygwin code. Just throwing out an idea here to help people help

RE: cygcheck (64&32) output contains DOS line terminators

From: Brian Inglis > On 2017-01-17 13:21, Marco Atzeri wrote: > > On 17/01/2017 21:00, Brian Inglis wrote: > >> All cygcheck output seems to have DOS line terminators in both > >> Cygwin 64 & 32. > >> Is this by design or just because it's a native Windows app? > > second one > > So by accident

RE: separating cygcheck -f package name from version

From: Brian Inglis > > $ fgrep "$(cygcheck -f /usr/bin/find | sed 's/\r$//').tar." \ > /etc/setup/installed.db | cut -d' ' -f1 > findutils > > OR > > $ fgrep "$(cygcheck -f /usr/bin/find | d2u).tar." \ > /etc/setup/installed.db | cut -d' ' -f1 > findutils >

separating cygcheck -f package name from version

I want to be able to extract a package's name from its version information output by cygcheck -f. For many packages it is easy: just strip off after the first hyphen; for example: $ cygcheck -f /usr/bin/find findutils-4.6.0-1 $ cygcheck -f /usr/bin/find | cut -d- -f1 findutils $ But, then there

RE: sincerely beg your help!!! for getting version 2.6.0-1

From: Marco Atzeri [mailto:marco.atz...@gmail.com] > On 17/01/2017 13:42, sun zheng wrote: > > hi team, > > > > sorry for troubling. but > > > > currently i am facing a big problem: > > i was requesting to install cygwin 2.6.0-1 in my company's pc since > > this is the latest version. due to

RE: rename() cannot replace the file which is opened with writable access

From: Masamichi Hosoda > If I understand correctly, > POSIX behavior should be able to replace the writable opened file by > rename(). > But, It does not work on my Cygwin environment. > > Is it no problem if Cygwin's behavior is different from POSIX behavior? > If so, we need different

Customizing bash user guide out-of-date

Chapter 2 of the Cygwin User's Guide [1] has a section called "Customizing bash" [2]. This section starts off: To set up bash so that cut and paste work properly, click on the "Properties" button of the window, then on the "Misc" tab. Two problems: (1) This statement doesn't

RE: open IE from command line

From: Andrey Repin > %ProgramData% and %PUBLIC% is a likely culprit. Thanx, but those didn't actually matter. The one causing the problem was ProgramW6432. Once I restored it, I could open web pages using cygstart. --Ken Nellis -- Problem reports: http://cygwin.com/problems.html FAQ:

RE: open IE from command line

From: cyg Simple (https://cygwin.com/ml/cygwin/2016-12/msg00240.html) > > FYI you can also use vi to translate those line endings > > $ vi foo > :set ff=unix > :wq > > or going the other direction, > > $ vi foo > :set ff=dos > :wq Actually, the file downloaded just fine without CRLF line

RE: open IE from command line

> From: Doug Henderson > On 21 December 2016 at 18:04, Doug Henderson wrote: > > On 21 December 2016 at 10:01, Nellis, Kenneth wrote: > > > Attached is a bash script, renamed as openurl.sh.txt, which will open > > a url with either the default browser or Internet E

RE: open IE from command line

From: Nellis, Kenneth > I suspect the issue is that some required DLLs are not in > my PATH. Indeed, my Cygwin PATH is a pruned version of my > Windows PATH. Actually, that's not the case and is irrelevant as Lee demon- strates in https://cygwin.com/ml/cygwin/2016-12/msg00220.html.

RE: open IE from command line

Thanx to all who responded to my query... > On 12/20/16, Nellis, Kenneth wrote: > > How to open a web page (remote or local) or launch IE from the > > mintty/bash command line? I've tried all the suggestions and the same thing happens: IE flashes on the screen and immediately dis

open IE from command line

How to open a web page (remote or local) or launch IE from the mintty/bash command line? I've tried the following: $ cygstart "http://www.google.com; $ cygstart index.html # local page $ "/cygdrive/c/Program Files/Internet Explorer/iexplore.exe" $ cygstart "/cygdrive/c/Program Files/Internet

RE: Editors set x-bit (sometimes)

From: Achim Gratz > I said "-exec +", although I concur it was too easy to miss. Indeed, I overlooked the "+" and was unfamiliar with that option to find. Glad I asked. Learned something today. Thanx for the clarification. ☺ --Ken Nellis -- Problem reports:

RE: Editors set x-bit (sometimes)

> From: Achim Gratz > .. the latter is slightly less efficient and you have to > do -print0/-0, but I tend to get it right more easily then the -exec > stuff. Really? I always thought the opposite. With -exec, doesn't find invoke the command for each single found object? While xargs allows a

chere and environment variable preparation

Normally, I open a Cygwin terminal window by clicking on a Windows icon which is an alias to a .BAT file which prepares environment variables for my Cygwin session and then invokes mintty thusly: start /b C:\cygwin64\bin\mintty -i/Cygwin-Terminal.ico -s80,57 - Nothing unusual there, but I have

RE: [ANNOUNCEMENT] Updated: setup.exe (Release 2.876)

From: Massimo Balestra > > I made a batch script that, when needed, downloads the new setup.exe > with wget, changes the permissions and then executes it. > > This is my bat script. > > -- > > cd C:\cygwin64Install > move setup-x86_64.exe

RE: [ANNOUNCEMENT] Updated: setup.exe (Release 2.876)

From: Andrey Repin > Greetings, Nellis, Kenneth! > > >> A new version of Setup, release 2.876, has been uploaded to > >> > >>https://cygwin.com/setup-x86.exe (32 bit version) > >>https://cygwin.com/setup-x86_64.exe (64 bit version) > >

RE: [ANNOUNCEMENT] Updated: setup.exe (Release 2.876)

From: Yaakov Selkowitz > > A new version of Setup, release 2.876, has been uploaded to > >https://cygwin.com/setup-x86.exe (32 bit version) >https://cygwin.com/setup-x86_64.exe (64 bit version) > > ... Not a biggie, but thought I'd mention that when I installed the new 64-bit

RE: unzip, find broken by auto handling of .exe file extension

From: Stephen Anderson > > See also: > > http://stackoverflow.com/questions/32467871/unzip-gives-checkdir-error- > directory-exists-but-is-not-a-directory#32468314 > > The fact that 7z handles this and unzip does not indicates that the > problem > is fixable.. FWIW, it seems that the same

setup.exe to have Install button

Just in case anyone's collecting change requests against Setup.exe, here's a simple one that I'd like to see: All screens until the final screen display a "Next>" button. Typically, after launching, I just click this button until I get to the list of packages to review, but this screen also has a

RE: bash: igncr shell option breaks my PS1 prompt

From: Andrey Repin > > Greetings, Eric Blake! > > > But it seems like \n handling in PS1 is independent of any change in > > handing in the 'read' builtin. As evidence, I ran the following test > > using the older bash-4.3.42-4 build: > > > $ bash-4.3.42-4 > > $ set -o igncr > > $

RE: Script broken after updating bash to 4.3.46-7?

From: Gene Pavlovsky > Andrey, > That's what I personally think, none of the scripts I use have CRs, > and this is why I'd prefer not using the `igncr` option. > However the recent change to how `read` works makes it necessary to > modify existing scripts which interoperate with Windows console >

RE: cygpath -w and .exe magic

From: cyg Simple > On 8/26/2016 10:35 AM, Nellis, Kenneth wrote: > > From: Herbert Stocker > >> On 26.08.2016 15:19, Lee Dilkie wrote: > >>> and break everyone who has existing code to take care of this? > >> > >> If it is done, it should be done as

RE: cygpath -w and .exe magic

From: Herbert Stocker > On 26.08.2016 15:19, Lee Dilkie wrote: > > and break everyone who has existing code to take care of this? > > If it is done, it should be done as an additional option, i'd say. Of course a new option, duh! ☺ But my feeble brain is failing to imagine a case where this

cygpath -w and .exe magic

Dear Cygwin Community, $ ls -l total 60 -rwxr-x--- 1 knellis Domain Users 60927 Aug 26 08:57 hello.exe $ ./hello Hello, world! $ cygpath -w hello hello $ The purpose of cygpath -w, it seems to me, is to provide to Windows a valid path given a Posix path. Given executable file foo.exe, which

RE: Please explain how to add to a thread in this mailing list

Alternatively, From: Andrey Repin > People use digest when they don't plan to participate in discussions, or if > they are using web mail with no ability or inclination to setup main filters > so that list messages end in a separate directory and not disturbing their > private mails. I

RE: Ubuntu on Windows against Cygwin X server

From: Marco Atzeri > http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-xserver-nolisten-tcp-default The target of this link says "See Q: 1.6", which states "See the DISPLAY NAMES section of man X for more information." $ man X No manual entry for X $ uname -svr CYGWIN_NT-6.1 2.5.2(0.297/5/3)

RE: PATHEXT is fundamental to Windows and Should be recognised by CYGWIN

From: Erik Soderquist > ... DOS did a lot of things > against already established conventions, such as using a backslash > instead of a forward slash as the directory separator, just "to be > different". Not just to be different, but to distinguish from slashes used as command qualifiers (a la

RE: cygpath -w 'a"b'

It seems that the length of the string passed to cygpath -w affects whether double quotes are translated or not: $ cygpath -w '"12345"' | od -cAn " 1 2 3 4 5 " \n $ cygpath -w '"123456"' | od -cAn " 1 2 3 4 5 6 357 200 242 \n $ cygpath --version cygpath (cygwin)

RE: chere not seeing my preferred $HOME

Thanx to the responders to this issue. My problem, it turns out, is due to my having set up Windows environment variable "HOME", which conflicted with my Cygwin HOME. Apparently my Windows HOME overrode my Cygwin HOME; deleting the Windows HOME allowed chere to see my Cygwin HOME, and all is

RE: chere not seeing my preferred $HOME

From: Rainer Blome > > Hi Kenneth, Hello. http://www.cygwin.com/acronyms/#PCYMTNQREAIYR (Actually, I don't know how to do that, so I do it manually.) > not sure what you are aiming for here. I simply want chere to run my .profile before it presents me with the bash prompt. > The purpose of

chere not seeing my preferred $HOME

Couldn't find anything online for this: Wondering if someone can tell me how to configure chere so that it runs my .bash_profile in my regular Cygwin home: Cygwin64> echo $HOME; cygpath -w $HOME /home/knellis C:\cygwin\home\knellis Cygwin64> chere> echo $HOME; cygpath -w $HOME

RE: Cygwin 2.5.2-1

> From: cygwin-announce-owner> > ... > NOTE 2: > > Cygwin 2.5.2 is the last release supporting Windows XP and Windows > Server 2003. > ... Okay, but to be clear, is it the *final* release supporting these? --Ken Nellis

malware

Dear Cygwin, A little supposition here, but it appears that the recent posting from Viverra Inc. contained a malicious attachment, as detected by my company's e-mail malware detection as it intercepted the recent digest. I need now to appeal to them to allow me to continue receiving e-mail

RE: Proposed patch for web site: update most links to HTTPS

-Original Message- From: Adam Dinwoodie > ... > But I agree with Brian: the Cygwin website > should use https everywhere unless there's some good, specific reason > why it's a bad idea... 1. Did Brian say that? I couldn't find it in the thread. 2. I would be interested to hear the

cygwin support for building for Win CE

Please let me know whether Cygwin offers any package support for building native Windows CE binaries, specifically 5.0. I tried i686-w64-mingw32-gcc, and it builds just fine for regular Windows, but such binaries do not run under CE. (I'm familiar with building for *nix; not so much Windows.)

RE: tclsh - try command

From: cyg Simple > Dear list, > > I'm thinking of using TCL for a development program I'm spearheading. > The documentation for TCL http://www.tcl.tk/man/tcl/TclCmd/try.htm show > that this is available and I need to use it. But with Cygwin's version > I get the following. Why isn't it

RE: cksum giving inconsistent results on network drive

From: Erik Soderquist > On Mon, Mar 21, 2016 at 4:21 PM, Nellis, Kenneth wrote: > > I'm seeing inconsistent results with cksum, with repeated > > executions on the same file giving different results. > > Now, I suspect I won't get much sympathy because I am > > access

cksum giving inconsistent results on network drive

I'm seeing inconsistent results with cksum, with repeated executions on the same file giving different results. Now, I suspect I won't get much sympathy because I am accessing the remote file through a "stone_age_old"* (QNX4) Samba server through my Q: drive, but if there's a solution to this, I'd

RE: faster opening Cygwin from Explorer window

> On Mar 18, 2016, at 11:48 AM, Jim Garrison wrote: > > > > Cygwin already has this, in package "chere". Not sure if it's available > > for 64-bit yet. > Hey, thanx Jim et al. Just what the doctor ordered! BTW, wanting to see some documentation on this package before I install,

cygcheck doesn't find package for procps

In another message, procps was mentioned*, and I tried to see what package it was in using cygcheck, but cygcheck didn't return anything. Wondering what is wrong... $ type procps procps is hashed (/usr/bin/procps) $ procps --version procps version 3.2.8 $ cygcheck --help Usage: cygcheck

faster opening Cygwin from Explorer window

I frequently ping-pong back and forth between working in the Windows and Cygwin environments, needing to keep both Explorer windows and Cygwin PWD focused on the same folder/directory. (I use mintty in Cygwin.) To open an Explorer window to my Cygwin PWD, I can simply type "cygstart .". The

RE: Calling cygpath from find exec?

From: Matt D. > > Is there a reason why these produce different results? > > find . -exec cygpath -wa {} \; > find . -exec echo $(cygpath -wa {}) \; > > I have to do this which is much slower: > find . -exec bash -c 'echo $(cygpath -wa {})' \; > > Or this: > find . | while read a; do echo

RE: Symlink targets dereferenced when winsymlinks:native

From: David Macek > On 18. 11. 2015 20:48, Corinna Vinschen wrote: > > On Nov 18 19:13, David Macek wrote: > >> On 18. 11. 2015 18:55, Corinna Vinschen wrote: > >>> On Nov 17 23:28, David Macek wrote: > I went through the UG looking for differences between regular Cygwin > symlinks and

RE: does anyone care about package minor version bump announcements?

From: Corinna Vinschen > On Nov 19 10:18, cyg Simple wrote: > > On 11/19/2015 10:13 AM, Andrew Schulman wrote: > > > Does anyone care about that? Lately I don't. In fact I've skipped > > > sending > > > the last few, and no one seems to have noticed. > > > > > > Can we leave it to the

RE: initial cygwin installation

From: Warren Young > > On Oct 25, 2015, at 3:11 PM, t s wrote: > > > > Q: How do I install everything? > > A: You do not want to do this! > > I explain this in more detail here: > > http://stackoverflow.com/a/21233990 For the hell of it I decided to check out this

RE: /bin/pwd -P doesn't expand all symlinks

> From: Mark O'Keefe > > Hi, > > While using /bin/pwd -P to expand directories to get the absolute, non- > symlinked version of the directory I discovered that this doesn't work on > Cygwin as I believe it is meant to work. > > > $ cd /tmp > $ /bin/pwd -P > /tmp > $ ln -s /home . > $ cd home >

RE: [ANNOUNCEMENT] Updated: bash-4.3.42-3

From: Mikhail Usenko > There is also the similar problem found accidentally just now with sed in > pipelines: > $ echo -ne "\r\n" | sed '' | od -A n -tx1 # should be: 0d 0a > 0a > $ echo -ne "\r\r\n" | sed '' | od -A n -tx1 # should be: 0d 0d 0a > 0d 0a FWIW, back in 2012 there was a

  1   2   3   >