From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Strange SSH behaviour after updating to Cygwin 2.0.1
Date: Fri, 15 May 2015 10:29:00 -0000 [thread overview]
Message-ID: <20150515184100.2c2590c9b1b49b3d8617f334@nifty.ne.jp> (raw)
In-Reply-To: <87siazei6h.fsf@Rainer.invalid>
On Thu, 14 May 2015 09:23:34 +0200
Achim Gratz wrote:
> That I already knew, and it's indeed fixed by making tcsh your default
> shell over on Cygwin. I can't do that in the case I mentioned since I
> still haven't been able to convince our AD administrators to fill the
> respective fields.
Try: ssh -t user@hostname -- tcsh -l
With option -t, it should work as you expected.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
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
next prev parent reply other threads:[~2015-05-15 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 8:12 Achim Gratz
2015-05-08 6:48 ` Stephen John Smoogen
2015-05-14 7:44 ` Achim Gratz
2015-05-15 10:29 ` Takashi Yano [this message]
2015-05-15 11:58 ` Achim Gratz
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=20150515184100.2c2590c9b1b49b3d8617f334@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).