public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: tee: 'standard output': Permission denied
Date: Wed, 30 Dec 2020 12:21:21 -0700	[thread overview]
Message-ID: <1f81eb96-7269-5bcb-8c81-60fcbc40a053@SystematicSw.ab.ca> (raw)
In-Reply-To: <1318302036.20201230052233@inbox.ru>

On 2020-12-29 19:22, Andry via Cygwin wrote:
>> Cannot repro...  Logfile is created correctly and commands and their
>> output are logged there.  The file encoding for the logfile is utf-8.
> The issue found in the Windows 7 x64.
> 
>> A couple of things though:    1.  changing \ to / does not guarantee a
>> valid Cygwin path.
> Not sure what you talking about. Always worked.
> 
>> 2.  the cd does nothing because bash -l starts the shell in the home
>> directory.
> I've tested it and it does.
> 
>> 3.  Once you've started bash, you don't have to supply the full path so 
>> "/bin/bash.exe" and "/bin/tee.exe" are fine (assuming your path and mounts
>> are set correctly)
> You have to, because not logged shell does not have PATH registration to the
> `/bin`.
> 
>> Are any files on a remote share?
> You cannot run cmd.exe on a remote share.
> 
>> Are any of the paths relative?Do any of the paths have spaces in them?
> Does it matter?
Seems to have been reported a few times with Windows Russian and fix suggested 
was "chcp 1252" (which might not be too useful for many Russians), as there may 
be encoding conversion bugs with UTF-8.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2020-12-30 19:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-27  2:04 Andry
2020-12-29 21:50 ` Andry
2020-12-30  1:29   ` Kevin Schnitzius
2020-12-30  2:22     ` Andry
2020-12-30 19:21       ` Brian Inglis [this message]
2020-12-31 16:33         ` Andry
2020-12-30  1:31   ` Doug Henderson
2020-12-30  1:45   ` Takashi Yano
2020-12-30  2:24     ` Andry
2020-12-30  4:02       ` Takashi Yano
2020-12-30  4:40         ` Takashi Yano
2020-12-30  4:54           ` Andry
2020-12-30  5:11           ` Andry
2020-12-30  4:49         ` Andry
2020-12-30  5:03           ` Takashi Yano
2020-12-30  5:18             ` Andry
2020-12-30  6:40             ` Takashi Yano
2020-12-30 10:13       ` Takashi Yano
2020-12-30 15:07         ` Andry

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=1f81eb96-7269-5bcb-8c81-60fcbc40a053@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).