public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: interactive-services-detection not started on 32-bit cywin executables
Date: Sun, 19 Jan 2014 22:49:00 -0000	[thread overview]
Message-ID: <52DC565D.20400@cygwin.com> (raw)
In-Reply-To: <CAO2ddnZo51aGT-cjjxjTbvNmXtBkq4vRr4-E-6YXAVa_YcwYTw@mail.gmail.com>

On 1/17/2014 7:08 AM, BGINFO4X wrote:
> Hello,
>
> I attach here my tests to clarify:
>
> #Test1 - Only bash
> C:\cywin\bin\bash.exe
>
> Result: bash exits. Interactive window not opened.

<snip>

>> For example, when launching only bash.exe as a service, bash EXITS immediately.
>>
>> But, If I launch bash.exe  and then another win32bit executable (ex:
>> msys sh.exe), then OIUDetect is "captured" and bash.exe doesn't exit.
>>
>> So "it seems that 32 bits cygwin are not correctly managed on 64 bits systems"
>>
>>> The only workaround I can think of is to start the uiodetect service.
>>
>> No, this is not the question: uiodetect is always started.

Yes, you know this now but this was the question you were asking in the
last round.  Fortunately, you do not need my answer now. :-)

>> Could you help me?

You're invoking bash non-interactively.  Since you want an interactive
shell, you should be using the '-i' flag.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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:[~2014-01-19 22:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 11:53 Fwd: " BGINFO4X
2014-01-17 12:08 ` BGINFO4X
2014-01-19 22:49   ` Larry Hall (Cygwin) [this message]
     [not found]     ` <CAO2ddnZQ4otrozE-BqKzLn66wyL6oE8uVHLUA7zjF3T52kwg7g@mail.gmail.com>
2014-01-21 17:21       ` BGINFO4X
  -- strict thread matches above, loose matches on Subject: below --
2014-01-16 17:10 BGINFO4X
2014-01-16 18:56 ` Larry Hall (Cygwin)
2014-01-16 19:15 ` Larry Hall (Cygwin)

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=52DC565D.20400@cygwin.com \
    --to=reply-to-list-only-lh@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).