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 was
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 a
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 cha
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.
https://untroubled.org/ezm
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 messag
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
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
is
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
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 metadat
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 obsole
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 Nellis
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 s
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
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.
> 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
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 sourcewa
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:
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 psel
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
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 : b
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 propose t
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 c
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 he
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
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 r
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
>
>
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
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 securi
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 applicatio
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
30 matches
Mail list logo
