starship

[lmorg]

I've been playing around with starship a little more. @orefalo code and seeing if it made more sense to incorporate in the hint text rather than prompt (since this was the premise behind the hint test originally).

I quite like the results so thought I'd share. This isn't to say this is how people "have" to run starship on Murex. But it gives another option

[lmorg]

code:

ENV.STARSHIP_SHELL = "murex"
ENV.STARSHIP_SESSION_KEY = starship(session)

private starship_prompt {
    cast str

    NUM_JOBS=0
    # Evaluate the number of jobs before running the preserved prompt command, so that tools
    # like z/autojump, which background certain jobs, do not cause spurious background jobs
    # to be displayed by starship. Also avoids forking to run `wc`, slightly improving perf.
    #for job in $(jobs -p); do [[ $job ]] && ((NUM_JOBS++)); done

    exitnum -> set STARSHIP_CMD_STATUS

    # Prepare the timer data, if needed.
    if { $STARSHIP_START_TIME } then {
        now = datetime(--in {now} --out {unix})
        DURATION = $now - $STARSHIP_START_TIME
      
        starship prompt -s $STARSHIP_CMD_STATUS -j $NUM_JOBS -d $DURATION
        unset STARSHIP_START_TIME
    } else {
        starship prompt -s $STARSHIP_CMD_STATUS -j $NUM_JOBS
    }
}

event onPrompt starship=before {
    prompt = starship_prompt()
    GLOBAL.STARSHIP_HINT   = $prompt[1] # hint text is first line of starship prompt
    GLOBAL.STARSHIP_PROMPT = $prompt[2] # shell prompt is the second line
}

event onPrompt starship=after {
    ENV.STARSHIP_START_TIME = datetime(--in {now} --out {unix})
}

config set shell hint-text-func {
    out $STARSHIP_HINT
}

config set shell prompt {
    out $STARSHIP_PROMPT
}

[orefalo]

I actually like it better at the bottom....

[orefalo]

ah, here it is.... I read this msg yesterday in my mail and couldn't find it this morning.

Listen, I think this could be a great addition to the script - with a parameter to configure the behavior.

As of now, this is the latest version - https://github.com/orefalo/murex-module-starship
I added terminal width and jobs handling
Looking at your code, I need to bring your edits, but I have a problem with the jobs-

I am trying to get the number of external jobs with this command - fid-list --background -> count-> export NUM_JOBS
it returns 2 or 3, I believe it accounts for the current prompt script.

Would you have a solution?

export STARSHIP_SHELL="murex"
rand int -> :str: left 16 -> export STARSHIP_SESSION_KEY

config set shell prompt {

    # Get the command status
    exitnum -> set STARSHIP_CMD_STATUS

    # Prepare the timer data, if needed.
    if { $STARSHIP_START_TIME } then {
        datetime --in "{now}" --out "{unix}" -> cast int -> set END_TIME
        out $STARSHIP_START_TIME -> cast int -> set START_TIME
        $END_TIME - $START_TIME -> set DURATION
      
        out ${starship prompt --terminal-width=$ENV.COLS -s $STARSHIP_CMD_STATUS -j $ENV.NUM_JOBS -d $DURATION}
        unset STARSHIP_START_TIME
    } else {
        out ${starship prompt --terminal-width=$ENV.COLS -s $STARSHIP_CMD_STATUS -j $ENV.NUM_JOBS}
    }
}

event onPrompt starship=before {

    # how many bg jobs do we have
    fid-list --background -> count-> export NUM_JOBS

    # if $COLUMNS not defined
    if { $ENV.COLUMNS > 0 } then {
        export COLS = $ENV.COLUMNS
    } else { 
        try {
            tput cols -> export COLS
        }
        catch {
            export COLS = 128
        }
    }
}

event onPrompt starship=after {
    datetime --in "{now}" --out "{unix}" -> cast int -> export STARSHIP_START_TIME
    
}

[lmorg]

Just so I understand correctly, you only want to know the background jobs spawned by the previous command line?

[orefalo]

Never mind, it's my mistake.

[orefalo]

This is the latest version,

Now, it has one last remaining issue: I can't read the exitnum proper.

ENV.STARSHIP_SHELL="murex"
ENV.STARSHIP_SESSION_KEY = starship(session)

private starship_prompt {
 
    # get the command status
    STARSHIP_CMD_STATUS=exitnum()

    cast str

    # how many bg jobs do we have
    fid-list --background -> count -> set NUM_JOBS

    # if $COLUMNS is defined, use it
    if { ENV.COLUMNS > 0 } then {
        COLS=ENV.COLUMNS
    } else {
        try {
            COLS=tput(cols)
        }
        catch {
            COLS=128
        }
    }

    # Prepare the timer data, if needed.
    if { $STARSHIP_START_TIME } then {
        datetime --in "{now}" --out "{unix}" -> cast int -> set END_TIME
        now = datetime(--in {now} --out {unix})
        DURATION = $now - $STARSHIP_START_TIME
      
        starship prompt --terminal-width=$COLS -s $STARSHIP_CMD_STATUS -j $NUM_JOBS -d $DURATION
        unset STARSHIP_START_TIME
    } else {
        starship prompt --terminal-width=$COLS -s $STARSHIP_CMD_STATUS -j $NUM_JOBS
    }
}

event onPrompt starship=before {
    prompt = starship_prompt()
    GLOBAL.STARSHIP_HINT   = $prompt[1] # hint text is first line of starship prompt
    GLOBAL.STARSHIP_PROMPT = $prompt[2] # shell prompt is the second line
}

event onPrompt starship=after {
    ENV.STARSHIP_START_TIME = datetime(--in {now} --out {unix})
}

config set shell hint-text-func {
    out $STARSHIP_HINT
}

config set shell prompt {
    out $STARSHIP_PROMPT
}

[lmorg]

what about the requirement to see the exit numbers of all the commands in a pipe?

[orefalo]

I think I am getting closer with this,

event onCommandCompletion starfish=command {
    # get the command status
    ENV.STARSHIP_CMD_STATUS=$Interrupt.ExitNum
}

[lmorg]

That would just return the exit number for starship. Not for the last command that ran

[orefalo]

Well, to me the most elegant solution would be an event, similar to the above - but for the last command ran.

what about the requirement to see the exit numbers of all the commands in a pipe?

I am partially seeing what you have in mind, if we get it though an event, it could work.
This is driven from the starship implementation, which is rendering the prompt on before.

[orefalo]

In fact, the events you already have... what about passing the command exit code to them?