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

[ERROR] pak <name> opens Pack Atom View (PAV) in the pakScripts, not in $PATH #2

Closed
tburnam opened this issue Mar 25, 2017 · 0 comments
Assignees

Comments

@tburnam
Copy link
Owner

tburnam commented Mar 25, 2017

Reproduction steps:

$ pak <name>

pak then:

  • Builds executable bash <name> file in /pakScripts
  • Opens executable bash <name> in PAV
  • Copies executable bash <name> file to /usr/local/bin

But when changes are made on the PAV, they don't update the $PATH's executable.

Solution

There should be a dual persistence here in order to facilitate training environment for feature futures.

For now:
a.) Write a utility script in /pakScripts that updates the executable in /usr/local/bin

@tburnam tburnam self-assigned this Mar 25, 2017
@tburnam tburnam closed this as completed Jun 17, 2017
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

1 participant