Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error in MacOS Sierra
See original GitHub issueAfter using the normal installation method given on the website: After every command that I enter I am getting this error message: __bh_precmd:19: no such file or directory: /Users/vikas.y/.bashhub/log.txt. Also no commands are getting synced.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
If an error occurred while updating or installing macOS
The message might say that an error occurred while downloading, preparing, or installing, or that the installer is damaged or could not be ......
Read more >macOS Sierra problems: Here's how to fix the most common ...
If you get an error message while installing macOS Sierra saying that you don't have enough hard drive space, then restart your Mac...
Read more >9 Ways to Fix an Error Occurred While Preparing the Installation
Fix 1: Restart your Mac ... The first step when you see an error occurred while preparing the installation sierra is to restart...
Read more >How to fix “An Error has Occurred” when downloading macOS ...
Method 1. Reset settings stored in NVRAM and PRAM · Shut down your computer; · Turn it on and immediately press and hold...
Read more >Fix macOS Sierra 10.12.1 Update Stuck or Fail to Download ...
If your Mac shows a error message that "An error has occurred" or "Failed to Download" while you are trying to downloading a...
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 Free
Top 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
Yes, it looks like just creating the log.txt fixes the issue and there is no need of removing
/. Looks like I tried to overfix the problem. 😄But anyway the absence of log.txt is a problem which needs to be resolved. Thanks for the help.
This is very confusing as I’ve never heard of this issue before. Do you have to create the log manually and remove
/? My guess is the backslash is preventing the log from getting created for some reason. That could be changed to simplytouchthat file during installation.Could you try reinstalling and simply creating that file when it’s erroring. e.g: