Description
I've been facing a pair of strange issues for some month, and they begun together around the time I started using athame, so I have a strong suspect that athame is doing something I don't expect/understand, and I'm writing here to seek for help.
I will describe my discovery process:
- I work on my office machine connecting to it via
ssh - I actually use
ssh -Y, because I want to be able to take advantange of+clipboard(which is useful if I copy text from, say, my personal computer's browser to the Vim session I opened via ssh on my office machine) - Around the time I started using athame, I've realized that the
+and*Vim registers were "sometimes" not working properly; at the point that:regwas not showing them anymore - And this still happens today
- Rebooting my personal computer solves the problem everytime, but everytime it comes back after "some time"
- I asked for help on #archlinux IRC channel, and they helped me point out that something was deleting my
/tmp/.X11-unix/X0file (or probably the whole content of/tmp/.X11-unix); specifically they guided me to make use ofauditctlandausearchto point out what is deleting stuff in/tmp; this resulted in this log, where you can see there'sexe="/usr/bin/vim"when the deletion of/tmp/.X11-unix/X0takes place - This made me think of another
/tmprelated problem I'm having with the browser, which also resulted in "something" is deleting stuff in your/tmp/ - Thinking about it, I'm pretty sure that the issue happens even if I don't open a Vim session on my personal computer (in weekdays, it might happen that I open a Vim session on my computer only after work, when the issue has already happened during the the previous hours)
- Eventually I've come up with this GIF. Before recording it, I have done
mv .vimrc VIMRCand then REBOOTED the system, to make sure my.vimrcwas not playing the game. In the GIF you can see that doingmv VIMRC .vimrctriggers the issue with a few seconds delay.
Now I'm sure that the content of my .vimrc is relevant, and please, let me know if you want to see it, but the point is: if I reproduce the problem right after booting, by "creating/restoring" my .vimrc, with no Vim session alive except the one handled internally by athame, and with ausearch telling me that Vim has deleted /tmp/.X11-unix/X0, it's easy for me to think that's athame who's doing it.
Since you wrote this program, I think you might have a clue of whether athame can or cannot have this effect (maybe because of a problematic .vimrc, I don't know).
In the meanwhile, I've temporarily disabled athame with export ATHAME_ENABLED=0 to see if the problem persists or not.