Skip to content

Research a more elegant command completion signal #15

@dotnetKyle

Description

@dotnetKyle

Instead of echoing the command completion signal, research using prompt replacement to give a command completion signal to all commands:

the way to do this is this:

In PowerShell, run this command before running any others:

function prompt { \"af9704340bb848388fa07b4273836385\" }

In cmd:

prompt af9704340bb848388fa07b4273836385

In bash:

export PS1="af9704340bb848388fa07b4273836385"

every prompt will start with that guid and when you see that, you know that the command has finished and we can start the next one.

You can dynamically replace this with Environment.CurrentDirectory + ">" or something similar.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions