Update README.md for background tasks (nushell#826)

Rayan Amal · web-flow · commit 5782e2b5d2e1 · 2024-04-28T16:07:57.000-05:00
diff --git a/modules/background_task/README.md b/modules/background_task/README.md
@@ -48,7 +48,7 @@ with-env { FOO: ($foo | to json) } {
 }
 ```
 
-## How can I reuse custom commands in a background task?
+### How can I reuse custom commands in a background task?
 
 You can define these commands in a seperate module, like so:
 
@@ -63,3 +63,6 @@ task spawn {
   foo bar
 }
 ```
+## Troubleshooting
+
+- On some setups (e.g. NixOS with `nu` installed as a binary in user's `$HOME`), `sh` (which `pueue` delegates tasks to run) might fail to find `nu` in the `$PATH`. In this case hard-coding the location of your nu binary in the `task spawn` function definiton in `task.nu` can solve the issue.

Original file line number	Diff line number	Diff line change
`@@ -48,7 +48,7 @@ with-env { FOO: ($foo \| to json) } {`
`48`	`48`	`}`
`49`	`49`	```
`50`	`50`
`51`		`-## How can I reuse custom commands in a background task?`
	`51`	`+### How can I reuse custom commands in a background task?`
`52`	`52`
`53`	`53`	`You can define these commands in a seperate module, like so:`
`54`	`54`
`@@ -63,3 +63,6 @@ task spawn {`
`63`	`63`	`foo bar`
`64`	`64`	`}`
`65`	`65`	```
	`66`	`+## Troubleshooting`
	`67`	`+`
	`68`	+- On some setups (e.g. NixOS with `nu` installed as a binary in user's `$HOME`), `sh` (which `pueue` delegates tasks to run) might fail to find `nu` in the `$PATH`. In this case hard-coding the location of your nu binary in the `task spawn` function definiton in `task.nu` can solve the issue.