Starship Custom Commands

[ghost]

Starship Custom Commands

When setting up the format string, we can access all the Starship config options with "$option_name". But this is a nesting level too high in the case of custom commands:

custom = {
  myCmd1 = {
    command = "echo hello";
    when = true;
  };
  myCmd2 = {
    command = "echo world";
    when = true;
  };
};

As far as I can tell, the only way to access the above custom commands in the format string is with $custom, which will print "helloworld" in the prompt. But they should be individually accessible with $myCmd1 and $myCmd2.

I'm a noob, so if there is in fact a way to use custom commands individually that I'm missing, I apologize.

[ncfavier]

I'm a bit confused, what does this have to do with Home Manager?

[ncfavier]

From a quick glance at the Starship docs, it looks like you should be able to use ${custom.myCmd1} (after escaping it properly so that Nix doesn't treat it as a string interpolation)?

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

[ghost]

I am sorry I missed this, thank you for the reply.

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.