From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Andry <andry@inbox.ru>
Subject: Re: tee: 'standard output': Permission denied
Date: Wed, 30 Dec 2020 14:03:58 +0900 [thread overview]
Message-ID: <20201230140358.836dbced31c365033ac1f130@nifty.ne.jp> (raw)
In-Reply-To: <571565681.20201230074907@inbox.ru>
On Wed, 30 Dec 2020 07:49:07 +0300
Andry wrote:
> Hello Cygwin,
>
> >I am not sure why you don't wat to use script,
> >how about this then?
> >
> >@echo off
> >set CYGWIN_ROOT=...
> >set PWD=...
> >set PROJECT_LOG_FILE=...
> >
> >"%CYGWIN_ROOT%\bin\script" -q -a "%PROJECT_LOG_FILE%" -c "chcp.com 65001 > /dev/null 2>&1; cd \"%PWD%\"; CHERE_INVOKING=1 /bin/bash --login"
>
> 1. chcp.com has no effect here
Weird. In my environment, chcp surely changes the code page.
Are you using cygwin 3.2.0 snapshot by any chance? If so, add
set CYGWIN=disable_pcon
before starting script.
> 2. log is written after the `script` exit
Add -f option to script command.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2020-12-30 5:04 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
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 [this message]
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=20201230140358.836dbced31c365033ac1f130@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=andry@inbox.ru \
--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).