-
Notifications
You must be signed in to change notification settings - Fork 33
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
Does athame tamper with /tmp/ or X11? #90
Comments
Setting |
I doubt athame itself is directly responsible. It sounds like vim is deleting your file because of something in your vimrc. Since athame literally calls vim, it’s going to cause any problems you see from running vim |
Probably, but that specific behavior (deleting stuff in |
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:
ssh
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)+
and*
Vim registers were "sometimes" not working properly; at the point that:reg
was not showing them anymore/tmp/.X11-unix/X0
file (or probably the whole content of/tmp/.X11-unix
); specifically they guided me to make use ofauditctl
andausearch
to 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/X0
takes place/tmp
related problem I'm having with the browser, which also resulted in "something" is deleting stuff in your/tmp/
mv .vimrc VIMRC
and then REBOOTED the system, to make sure my.vimrc
was not playing the game. In the GIF you can see that doingmv VIMRC .vimrc
triggers 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 withausearch
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.The text was updated successfully, but these errors were encountered: