public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: stty icrnl
Date: Thu, 09 Jun 2016 18:34:00 -0000	[thread overview]
Message-ID: <72EAE5BB-D905-4394-BEB4-5303ED8879A4@etr-usa.com> (raw)
In-Reply-To: <loom.20160608T020226-915@post.gmane.org>

On Jun 7, 2016, at 6:05 PM, Brian Inglis <Brian.Inglis@SystematicSw.ab.ca> wrote:
> 
> 
> cu is the normal Unixy way of using a remote USB->serial line, but I can't
> find it in Cygwin packages

Taylor UUCP builds out of the box on Cygwin:

  $ wget ftp://ftp.gnu.org/pub/gnu/uucp/uucp-1.07.tar.gz
  $ tar xf uucp-1.07.tar.gz
  $ cd uucp-1.07
  $ configure && make -j11
  $ ./cu --version
  cu (Taylor UUCP) 1.07
  Copyright (C) 1991, 92, 93, 94, 1995, 2002 Ian Lance Taylor
  This program is free software; you may redistribute it under the terms of
  the GNU General Public LIcense.  This program has ABSOLUTELY NO WARRANTY.

> searching for \<cu\>, and cu spews too many hits. 

When searching on the Cygwin package search page, adding .exe to executables narrows the results considerably.

As it happens, there is a Cygwin package shipping *cu.exe, but it is not the cu(1) you are looking for.  Move along.

Adding a leading slash fixes that:

  Found 0 matches for /cu.exe

If you were searching elsewhere (e.g. Google) then, yes, “cu” is a bad search term.  But if you knew that cu comes from the UUCP package, “cu uucp” leads you right to Taylor UUCP.

See, I *knew* there was a reason I was spending my days on amber VT220s hacking Unix back when I could have been out making Vitamin D!
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2016-06-09 18:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 12:05 Achim Gratz
2016-06-06 15:09 ` Achim Gratz
2016-06-07  9:31   ` Achim Gratz
2016-06-08  0:06 ` Brian Inglis
2016-06-08  5:40   ` Achim Gratz
2016-06-09  3:16     ` Andrey Repin
2016-06-09 18:58       ` Warren Young
2016-06-09 22:08         ` Achim Gratz
2016-06-09 22:31           ` Warren Young
2016-06-10  8:29             ` Achim Gratz
2016-06-10 15:38               ` Achim Gratz
2016-06-13 12:18                 ` Achim Gratz
2016-06-10  8:42           ` Corinna Vinschen
2016-06-10  8:57             ` Helmut Karlowski
2016-06-10 10:00               ` Helmut Karlowski
2016-06-10 14:39               ` Corinna Vinschen
2016-06-10 19:45             ` Achim Gratz
2016-06-09 18:34   ` Warren Young [this message]
2016-06-09 22:49     ` John Hein

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=72EAE5BB-D905-4394-BEB4-5303ED8879A4@etr-usa.com \
    --to=wyml@etr-usa.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).