public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: stty icrnl
Date: Thu, 09 Jun 2016 22:08:00 -0000	[thread overview]
Message-ID: <87fusm6mog.fsf@Rainer.invalid> (raw)
In-Reply-To: <C770C2B2-4069-47EA-8BA5-466ED62A9700@etr-usa.com> (Warren	Young's message of "Thu, 9 Jun 2016 12:58:31 -0600")

Warren Young writes:
> Unfortunately, it is a GUI program, which seems to go against the OP’s actual wish, which is for a command line program.  

Right.  Plus it doesn't have the translation capabilities that I needed
in this particular case.

> If the OP can stand a curses terminal program (as opposed to a purely
> bytestream oriented program like cu or direct /dev/tty* access) then
> I’d suggest minicom.

I've used minicom on Linux for similar hardware.  It also doesn't have
the translation capabilities needed since usually the IOCTL layer does
it, which remains unimplemented in Cygwin for serial lines.  Meanwhile,
I might need to write a proper wrapper for fully utilizing that hardware
anyway since I want to automate a few things and then have to keep an
eye on how much characters I've queued up and wait for echo in some
places.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

--
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

  reply	other threads:[~2016-06-09 22:08 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 [this message]
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
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=87fusm6mog.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).