public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Leo <leoslists@letterboxes.org>
To: cygwin@cygwin.com
Subject: Re: bash under emacs gives "cannot set terminal process group"
Date: Thu, 01 Mar 2012 22:34:00 -0000	[thread overview]
Message-ID: <8F78C505-4A85-4C2B-B0F1-29547378F4A6@letterboxes.org> (raw)
In-Reply-To: <33415299.post@talk.nabble.com>


On 01/03/2012, at 3:35 AM, wytten wrote:

> 
> I have the same issue.  More information: If you back down cygwin bash to
> BASH_VERSION='3.2.51(24)-release', the messages about job control no longer
> appear when bash starts.  However I still can't interrupt jobs started with
> M-x compile or M-x shell-command, so I'm guessing this has something to do
> with the latest version of cygwin.dll
> 

Yep, I can confirm this: The version 3 bash kind of works - but when I invoke a bash inside that bash it hangs. I can get back to emacs by Ctrl-G, but I have to kill the bash then. :-(

I still would like to find out what has change in the cygwin1 setup??? The I/O control must have changed somehow.

Maybe then it would be possible to invoke the cygwin bash differently, so that it plays nicely with the native emacs.

Thanks, Leo

--
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-03-01 22:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 12:45 leoslists
2012-02-27 15:19 ` Ken Brown
2012-06-25 20:46   ` sethflash
2012-06-27 13:55     ` Ken Brown
2012-02-28 10:25 ` Leo
2012-02-28 12:56   ` Ken Brown
2012-02-29 19:31     ` wytten
2012-03-01 22:34       ` Leo [this message]
2012-03-11 19:00         ` bash under emacs gives Jack

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=8F78C505-4A85-4C2B-B0F1-29547378F4A6@letterboxes.org \
    --to=leoslists@letterboxes.org \
    --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).