Skip to content

Conversation

@doonv
Copy link
Contributor

@doonv doonv commented May 4, 2022

Just a simple explanation about using the run-external command to run aliased paths.

(Is there a better name for this?)

@fdncred fdncred marked this pull request as draft May 5, 2022 00:38
@fdncred
Copy link
Contributor

fdncred commented May 5, 2022

we shouldn't land this because this is a reserved command that will change in the future. it's not really for use.

@doonv
Copy link
Contributor Author

doonv commented May 5, 2022

we shouldn't land this because this is a reserved command that will change in the future. it's not really for use.

Oh.

@doonv
Copy link
Contributor Author

doonv commented May 5, 2022

I guess this will be put on hold until a better command is finalized.

@kubouch
Copy link
Contributor

kubouch commented May 5, 2022

You can also do ^'some/long/path' instead of run-external

@doonv
Copy link
Contributor Author

doonv commented May 5, 2022

You can also do ^'some/long/path' instead of run-external

That's not explained explained in the docs right? (Doing it with commands in the PATH is explained, doing it with actual path strings is not.)

@kubouch
Copy link
Contributor

kubouch commented May 5, 2022

Yeah, it might not be covered well enough. You can do for example this as well: let cmd = 'some/path/to/command; ^$cmd` which would also be good to document.

Rather than in the "Aliases" section, I would add it somewhere more appropriate, since it's not alias-specific. For example here: https://www.nushell.sh/book/pipeline.html#working-with-external-commands

@fdncred
Copy link
Contributor

fdncred commented May 5, 2022

thanks for understanding.

@fdncred fdncred closed this May 5, 2022
ayax79 pushed a commit to ayax79/nushell.github.io that referenced this pull request Jun 26, 2024
ayax79 pushed a commit to ayax79/nushell.github.io that referenced this pull request Jun 26, 2024
This PR is part of porting all old scripts nushell#221 and ports `make_release`
folder
## Summary

### make_release/this_week_in_nu_weekly.nu
This script has already been ported and has received some updates: nushell#433.
So I just removed it
```yaml
from: before_v0.60/make_release/this_week_in_nu_weekly.nu
to: make_release/this_week_in_nu_weekly.nu
functions:
    do-work: make_release/this_week_in_nu_weekly.nu:1:query-week-span
```

### make_release/this_week_in_nu_release.nu

I have ported this, but I'm not sure if we need it because it has
strange name and we have `prs.nu` and `make_release/release-note/`

```yaml
from: before_v0.60/make_release/this_week_in_nu_release.nu
to: make_release/this_week_in_nu_release.nu
functions:
    do-work: make_release/this_week_in_nu_release.nu:1:do-work
```

### make_release/nu_release.nu

This has already been ported to `make_release/nu_release.nu` and has
received new updates nushell#828 so I just removed it

```yaml
from: before_v0.60/make_release/nu_release.nu
to: make_release/nu_release.nu
```

### make_release/gen-js-ext.nu
This has already been moved to `make_release/gen-js-ext.nu` and has
received new updates nushell#621 but not completely ported so I have ported it
- pipeline `for` to `each`
- `$nu.scope.commands` to `scope commands`
- explicit `print`
```yaml
from: before_v0.60/make_release/gen-js-ext.nu
to: make_release/gen-js-ext.nu
functions:
  gen_keywords: make_release/gen-js-ext.nu:1:gen_keywords
  gen_sub_keywords: make_release/gen-js-ext.nu:20:gen_sub_keywords
```

### make_release/gen-ts-ext.nu
I have ported this script
```yaml
from: before_v0.60/make_release/gen-ts-ext.nu
to: make_release/gen-ts-ext.nu
functions:
  gen-ts-cmds-begin: make_release/gen-ts-ext.nu:1:gen-ts-cmds-begin
  gen-ts-cmds: make_release/gen-ts-ext.nu:18:gen-ts-cmds
  gen-ts-subs: make_release/gen-ts-ext.nu:40:gen-ts-subs
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants