named jobs in RPROMPT

named jobs in RPROMPT

[Daniel]

I wanted to have a list of background jobs, with names (and some little
marker for suspended/running) in RPROMPT. I tried by turning on prompsubst
and made jobfunction which print $jobstates and then set
RPROMPT=$(jobfunction) But I get nothing, it seems jobstates is empty
during prompt generation? How can I do this?

Re: named jobs in RPROMPT

[Bart Schaefer]

On Sep 20,  7:27am, Daniel wrote:
} Subject: Re: named jobs in RPROMPT
}
}   setopt promptsubst
} Now consider:
}   RPROMPT='"$jobstates"'
} and
}   my_jobs() { print $jobstates }
}   RPROMPT='"$(my_jobs)"'
} 
} The first one display the jobstates array, the second doesn't.

That's because $(...) is a subshell which has no jobs of its own.
Consider:

    sleep 10 & print $jobtexts
    print $(sleep 3 >/dev/null & print $jobtexts)
    print $jobtexts

} My idea is to have my_jobs print a very compact list of jobs, fitting in
} the right prompt.

Instead of having my_jobs print the list to stdout, which forces you
to create a sub-process whose output can be captured, just have my_jobs
assign the list directly to RPROMPT.

Re: named jobs in RPROMPT

[Julien Jehannet]

2011/9/20 Daniel <quite@hack.org>:
> (...)
> But thanks anyway, because now I tried to minimize my code even more.
>
>  setopt promptsubst
> Now consider:
>  RPROMPT='"$jobstates"'
> and
>  my_jobs() { print $jobstates }
>  RPROMPT='"$(my_jobs)"'
>
> The first one display the jobstates array, the second doesn't. Also, running
> my_jobs from the prompt does display the array. Could this be because inside
> the function, there are no background jobs? It's in a different context, or
> something like that?
>
> My idea is to have my_jobs print a very compact list of jobs, fitting in
> the right prompt.

I would reset RPROMPT periodically instead.
Maybe something similar to :

  % my_jobs() { RPROMPT=$jobstates }
  % precmd_functions=(my_jobs)

But this is just for testing because you will certainly clutter your
rprompt this way.
Don't forget that if the line is too long, the content will not be displayed.

-- 
J u l i e n    J e h a n n e t

Re: named jobs in RPROMPT

[Daniel]

 <fhml <at> herrmann-koenigsberg.de> writes:

> 
> Hey there.
> 
> > [...] and then set
> >RPROMPT=$(jobfunction) But I get nothing, it seems jobstates is empty
> >during prompt generation?
> 
> When you do >>PROMPT=$(code)<< then 'code' gets executed and the result is
stored in PROMPT. Sometimes
> that is not what you want. What you probably want is >>PROMPT='$(code)'<<. See
the little 's? Those
> prevent 'code' from being evaluated immediately. Now the code gets evaluated
every time the PROMPT is shown.

I'm well aware of the function of single-quotes and the need for them here.
Sorry I omitted them from what was pseudo-code but didn't look like that ;)

But thanks anyway, because now I tried to minimize my code even more.

  setopt promptsubst
Now consider:
  RPROMPT='"$jobstates"'
and
  my_jobs() { print $jobstates }
  RPROMPT='"$(my_jobs)"'

The first one display the jobstates array, the second doesn't. Also, running
my_jobs from the prompt does display the array. Could this be because inside
the function, there are no background jobs? It's in a different context, or
something like that?

My idea is to have my_jobs print a very compact list of jobs, fitting in
the right prompt.
  

RE: named jobs in RPROMPT

[fhml]

Hey there.

> [...] and then set
>RPROMPT=$(jobfunction) But I get nothing, it seems jobstates is empty
>during prompt generation?

When you do >>PROMPT=$(code)<< then 'code' gets executed and the result is stored in PROMPT. Sometimes that is not what you want. What you probably want is >>PROMPT='$(code)'<<. See the little 's? Those prevent 'code' from being evaluated immediately. Now the code gets evaluated every time the PROMPT is shown.

A simple example where 'code' is 'date'. Lets say its currently 1970-01-01 00:00:00. When you enter >>PROMPT=$(date)<<, '$(date)' gets evaluated immediately, which is the same as if you typed >>PROMPT="1970-01-01 00:00:00"<<. Of course, that will never change. If you use 's, then '$(date)' gets stored in PROMPT - just as you typed it, not evaluated. Now every time PROMPT is evaluated '$(date)' gets evaluated which gives you a brand new date every time your PROMPT is updated.

Greetings :)