public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Side-by-side configuration is incorrect reported as permission denied
Date: Wed, 15 Aug 2012 04:23:00 -0000	[thread overview]
Message-ID: <20120815040938.GA31916@ednor.casa.cgf.cx> (raw)
In-Reply-To: <102316155.20120815004209@mtu-net.ru>

On Wed, Aug 15, 2012 at 12:42:09AM +0400, Andrey Repin wrote:
>Greetings, Christopher Faylor!

Sigh.

>>But you aren't really even suggesting that.  You are apparently just
>>suggesting that every windows error should be displayed by the Cygwin
>>DLL.  Wow.
>
>Um.  On another hand, this made me think from my deep pit: as a regular
>user, not a developer, in some cases, I would prefer DLL to track and
>report native error codes/messages.  Not as a general way of operation,
>obviously, more like an intermediate debugging layer on demand.  So,
>there's a suggestion for someone interested in this feature and capable
>of making this happen.

If you're "debugging" you can get the error by stepping into the DLL.

If you are actually capable of making it happen then prove it by
discussing implementation in cygwin-developers and eventually providing
a patch in cygwin-patches.  Otherwise, take Earnie's observation to
heart: http://cygwin.com/ml/cygwin/2012-08/msg00257.html

(I'm going to be quoting this a lot)

You aren't making any points by posting YA vague suggestion.

cgf

--
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:[~2012-08-15  4:10 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-11  0:45 Andrew DeFaria
2012-08-11 10:35 ` Larry Hall (Cygwin)
2012-08-11 17:32   ` Earnie Boyd
2012-08-11 19:23   ` Andrew DeFaria
2012-08-11 19:54     ` Christopher Faylor
2012-08-12  4:24       ` Cliff Hones
2012-08-12  9:07       ` Andrew DeFaria
2012-08-12 12:35   ` Pawel Jasinski
2012-08-12 17:56     ` Christopher Faylor
2012-08-12 19:59       ` Pawel Jasinski
2012-08-12 20:54         ` Earnie Boyd
2012-08-12 21:30           ` Christopher Faylor
2012-08-13  1:05             ` Pawel Jasinski
2012-08-13  8:28               ` Herbert Stocker
2012-08-13 10:05                 ` Corinna Vinschen
2012-08-13 12:51                   ` Herbert Stocker
2012-08-13 13:11                 ` Earnie Boyd
2012-08-13 13:21                   ` Corinna Vinschen
2012-08-13 13:28                     ` Earnie Boyd
2012-08-13 14:32                       ` Corinna Vinschen
2012-08-13 13:51                   ` Cliff Hones
2012-08-13 15:15                 ` Christopher Faylor
2012-08-13  3:49           ` Andrew DeFaria
2012-08-13  8:48             ` Corinna Vinschen
2012-08-13 14:43               ` Andrew DeFaria
2012-08-13 14:59                 ` Corinna Vinschen
2012-08-13 15:01                   ` Andrew DeFaria
2012-08-13 15:22                     ` Corinna Vinschen
2012-08-13 15:40                       ` Andrew DeFaria
2012-08-13 15:33                 ` Christopher Faylor
2012-08-13 16:02                   ` Andrew DeFaria
2012-08-13 16:19                     ` Corinna Vinschen
2012-08-13 17:57                       ` Andrew DeFaria
2012-08-14 21:11                   ` Andrey Repin
2012-08-15  4:23                     ` Christopher Faylor [this message]
2012-08-13 18:56 Pawel Jasinski
2012-08-13 19:12 ` Christopher Faylor
2012-08-13 21:49   ` Daniel Colascione
2012-08-14  0:42     ` Pawel Jasinski
2012-08-14  3:12       ` Christopher Faylor
2012-08-14  8:38       ` Eric Blake
2012-08-14  9:16         ` Pawel Jasinski
2012-08-14 15:10           ` Christopher Faylor
2012-08-14 21:37             ` Pawel Jasinski
2012-08-15  5:37               ` Christopher Faylor

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=20120815040938.GA31916@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@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).