[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Interactive commands cant be backgrounded if run from bashrc
From: |
Dennis Williamson |
Subject: |
Re: Interactive commands cant be backgrounded if run from bashrc |
Date: |
Wed, 1 Sep 2021 21:28:55 -0500 |
On Wed, Sep 1, 2021, 8:42 PM Greg Wooledge <greg@wooledge.org> wrote:
> On Wed, Sep 01, 2021 at 09:37:02PM -0400, Dale R. Worley wrote:
> > "C. Yang" <hello@cheryllium.com> writes:
> > > emacs test.txt &
> > >
> > > fg
> >
> > > bash: fg: no job control
>
> > It sounds like Bash doesn't activate the job-control features until
> > .bashrc is completed.
>
> Well, there's an easy fix for that. Just put "set -m" before the
> last two commands.
>
> I tested with "set -m" and "vim & fg" just now, and it appeared to work.
>
>
Do processes started in .bashrc have a terminal? I would suspect that
something without a try would either complain or work differently. I'll
have to play around with it.
- Interactive commands cant be backgrounded if run from bashrc, C. Yang, 2021/09/01
- Re: Interactive commands cant be backgrounded if run from bashrc, Chet Ramey, 2021/09/02
- Re: Interactive commands cant be backgrounded if run from bashrc, C. Yang, 2021/09/02
- Re: Interactive commands cant be backgrounded if run from bashrc, Greg Wooledge, 2021/09/02
- Re: Interactive commands cant be backgrounded if run from bashrc, Chet Ramey, 2021/09/02
- Re: Interactive commands cant be backgrounded if run from bashrc, C. Yang, 2021/09/02
- Re: Interactive commands cant be backgrounded if run from bashrc, Chet Ramey, 2021/09/02
- Re: Interactive commands cant be backgrounded if run from bashrc, C. Yang, 2021/09/02