xport: command not found
See original GitHub issue-
🗹 I am on the latest Hyper.app version
-
🗹 I have searched the issues of this repo and believe that this is not a duplicate
-
OS version and name: Ubuntu 17.10
-
Hyper.app version: Latest
-
Link of a Gist with the contents of your .hyper.js: https://gist.github.com/marcus-sa/55c30f3dfa13f1f45886da3732676af2
-
Relevant information from devtools N/A
-
The issue is reproducible in vanilla Hyper.app: ☒
Issue
All of sudden after restarting my PC, when I open up Hyper this error occurres:
Export: command not found
If I open up the native terminal it works fine.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
bash: xport: command not found
I have used export to change my PATH variable . export not xport , ...
Read more >xport: command not found · Issue #2815 · vercel/hyper
I am on the latest Hyper.app version I have searched the issues of this repo and believe that this is not a duplicate...
Read more >bash: xport: command not found
Hi, Everytime I opened a Terminal - Konsole I receive this message first: Does anybody know how to fix this? greetings.
Read more >bash: xport: command not found
Hi, Everytime I opened a Terminal - Konsole I receive this message first: bash: xport: command not found [gonzalo@dhcp-4841-10 gonzalo] Does anybody.
Read more >Unix & Linux: bash: xport: command not found (2 Solutions!!)
Unix & Linux : bash: xport : command not foundHelpful? Please support me on Patreon: https://www.patreon.com/roelvandepaarWith thanks & praise ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
ok, please verify your rc files (
.bashrc
,.profile
…). I think that you have a typoi had the same issue and was the .profile were i find the typo