Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't find commands when running custom command in Terminal #42

Open
cassidyjames opened this issue Sep 22, 2020 · 2 comments
Open

Can't find commands when running custom command in Terminal #42

cassidyjames opened this issue Sep 22, 2020 · 2 comments

Comments

@cassidyjames
Copy link

cassidyjames commented Sep 22, 2020

I'm trying to use the custom command to serve a jekyll site; however, it seems like I can't use any apps or commands from that context; maybe I'm misunderstanding how this should be used?

But for example, if I use a custom command of cd ~/Projects/elementary/blog; bundle exec jekyll serve I get a bunch of issues:

  • First of all, I get Failed to execute child process “cd” (No such file or directory) which is unexpected.

  • If I try to just run bundle exec jekyll serve on its own (while testing things), I similarly get Failed to execute child process “bundle” (No such file or directory).

  • If I point to the exact path of bundle, e.g. /home/cassidyjames/.gems/bin/bundle exec jekyll serve, I get an exception that the gem can't be found (which is not the case when running the exact same command from Terminal).

Am I using this custom command wrong? How would you recommend someone do something like serve a jekyll site with Workspaces?

Using Workspaces 3.1.0 from AppCenter.

@DevAlien
Copy link
Owner

The custom command was thought for something simple app + flags etc like screenshot -c -x or whatever.
But you are already thew second person asking for a more complex thing.

For what you want to do we baiscally need to set a directory where to launch a command. (we could do this workspace wise?)

Then there should be a way to load your .bashrc file I guess for aliases and everything.

What I suggest you for the moment is create an alias on your bashrc file to execute that command.
Then in your custom command you can type something like this: bash -i -c 'my-alias'

@it-s
Copy link

it-s commented Sep 27, 2020

The custom command was thought for something simple app + flags etc like screenshot -c -x or whatever.

Hi @DevAlien ,
Issue is that simple commands are not working either.
cd /home is not a complex command, and yet it fails with Failed to execute child process “cd” (No such file or directory)
Am I missing something?

Thanks

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

No branches or pull requests

3 participants