public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Documentation for cygwin-console-helper.exe
Date: Mon, 13 Aug 2018 14:46:00 -0000	[thread overview]
Message-ID: <20180813144529.GN3747@calimero.vinschen.de> (raw)
In-Reply-To: <165ec576-622d-a33a-9e38-722afc834af3@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

On Aug 13 08:57, cyg Simple wrote:
> On 8/13/2018 3:53 AM, Corinna Vinschen wrote:
> > On Aug 12 19:53, cyg Simple wrote:
> >> The documentation for cygwin-console-helper.exe is missing, not even a
> >> --help function.
> > 
> > cygwin-console-helper.exe is not for the user to use, so why add
> > user docs?  The documentation is in the source for the interested
> > dev:
> > 
> > https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/fhandler_console.cc;hb=HEAD#l2521
> > 
> 
> How the hell am I supposed to find that by looking at
> cygwin-console-helper.cc?

You aren't.  The cygwin-console-helper solution is under-the-hood stuff,
a solution for a problem which was supposed to be not user visible.
Because, in this case user visible means it doesn't work as desired.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-08-13 14:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-12 23:53 cyg Simple
2018-08-13  6:08 ` Thomas Wolff
2018-08-13  7:53 ` Corinna Vinschen
2018-08-13 11:12   ` Andy Moreton
2018-08-13 11:26     ` Corinna Vinschen
2018-08-13 12:57   ` cyg Simple
2018-08-13 14:46     ` Corinna Vinschen [this message]
2018-08-14 21:08       ` cyg Simple

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=20180813144529.GN3747@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).