Closed calexicoz closed 5 years ago
Hey @calexicoz! Darn, thanks for letting me know! I wish I knew where that was happening. Can you confirm that when mcfly is loaded in your shell, the value of the environment variable MCFLY_HISTORY
in your shell points to a real file? MCFLY_SESSION_ID
should also be set.
Ok, I figured it out: the issue was my bash history file was missing (~/.bash_history
). It disappeared 2 days ago. I'll have to figure out why, but restoring it fixed the error.
Thanks for the help!
I'm glad you figured it out. I'll re-open this issue since I should add code to detect when this happens, for whatever reason.
Fixed in fd4a16f.
Hello @cantino , i'm running into the same panic error with latest binary. My history file is also intact.
EDIT: NVM. Turns out I was confused. I incorrectly thought I had to source mcfly.bash
or use mcfly
binary directly.
Turns out "both" is the answer. Working beautifully now! Thanks.
Glad it's working!
Hi,
I started to get those messages whenever I open a new terminal:
I can confirm they are coming from McFly because they disappear as soon as I remove the integration in my profile. Ie if I comment out this:
Sadly, the backtrace is not helpful:
I'm not 100% sure why/when it started. I'm guessing something changed on my machine but I'm not quite sure what. I upgraded to Mojave a couple weeks back but this only started a couple days ago. Aside from the message, everything else still works fine: I can use McFly and it records my commands properly.
Ideas?
Thanks!