On Wed, Sep 01, 2021 at 09:28:55PM -0500, Dennis Williamson wrote:
> On Wed, Sep 1, 2021, 8:42 PM Greg Wooledge wrote:
> > 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
On Wed, Sep 1, 2021, 8:42 PM Greg Wooledge wrote:
> On Wed, Sep 01, 2021 at 09:37:02PM -0400, Dale R. Worley wrote:
> > "C. Yang" writes:
> > > emacs test.txt &
> > >
> > > fg
> >
> > > bash: fg: no job control
>
> > It sounds like Bash doesn't activate the job-control features until
> >
On Wed, Sep 01, 2021 at 09:37:02PM -0400, Dale R. Worley wrote:
> "C. Yang" 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
"C. Yang" writes:
> This may be because the bashrc file is still running, and bash itself
> perhaps does not finish initializing until everything in the bashrc
> completes. This may be why CTRL+Z does not work correctly (it might
> require bash to finish initializing first)
I'm sure that's the
On Wed, Sep 1, 2021, at 8:20 PM, Ananth Chellappa wrote:
> I hope I can make a genuine contribution at some point.
If you're hoping/planning on getting these changes accepted into
bash, it might be worth hashing out details with Chet before expending
your time and energy. (I am not a
Thanks Sincerely Chet.
I hope I can make a genuine contribution at some point.
On Wed, Sep 1, 2021 at 12:27 PM Chet Ramey wrote:
> On 8/31/21 6:38 PM, Ananth Chellappa wrote:
> > Hi Team,
> >Could I get some help locating portions of the code that would
> need
> > to be tweaked to add
From: cheshire (he...@cheryllium.com)
To: mailto:bug-bash@gnu.org
Subject: Interactive commands cant be backgrounded if run from bashrc
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2
On 8/31/21 6:38 PM, Ananth Chellappa wrote:
> Hi Team,
> Could I get some help locating portions of the code that would need
> to be tweaked to add these features?
>
> If I had the time, I would love to get to know the code, but I have too
> much going on in my real job.
>
> 1.
On Wed, Sep 01, 2021 at 04:52:29PM +0100, David Collier wrote:
> greg - I'm sorry - I assume there is a proper place for me to post
> follow-up info, can you let me know where it is?
On the bug-bash mailing list is fine. If the script is too big to
post on bug-bash, then it's not useful for
greg - I'm sorry - I assume there is a proper place for me to post
follow-up info, can you let me know where it is?
I could try for a short script, but this thing is a bit like herding eels.
I narrowed it down to a single line containing 'sync' - but as you say
that's clearly impossible.
And to
On 9/1/21 5:36 AM, David Collier wrote:
> Version:
>
> GNU bash, version 5.0.3(1)-release (arm-unknown-linux-gnueabihf)
>
> Raspberry Pi using Raspbian.
>
> Installed from repo?
>
> LINENO goes backwards when run sync
I can't reprodude this.
--
``The lyf so short, the craft so long to
On Wed, Sep 01, 2021 at 10:36:21AM +0100, David Collier wrote:
> Version:
>
> GNU bash, version 5.0.3(1)-release (arm-unknown-linux-gnueabihf)
>
> Raspberry Pi using Raspbian.
>
> Installed from repo?
>
> LINENO goes backwards when run sync
>
> echo "== At this point
Version:
GNU bash, version 5.0.3(1)-release (arm-unknown-linux-gnueabihf)
Raspberry Pi using Raspbian.
Installed from repo?
LINENO goes backwards when run sync
echo "== At this point \$LINENO has correctly counted about
2800 lines=test @ 2832
On 8/31/21 3:25 PM, Lawrence Velázquez wrote:
> On Tue, Aug 31, 2021, at 4:02 AM, Lawrence Velázquez wrote:
>> ksh does not blindly remove all leading whitespace
>
> For the curious, this is how ksh(1) describes it:
>
> If '#' is appended to '<<', then leading spaces and tabs
> will
14 matches
Mail list logo
