> As far as I understand your problem, it is solved in a forthcoming > version of the vim package (those links are no longer installed by vim, > but only created as slaves via alternatives).
Thank you, that is what I hoped. > But still: what's exactly your problem? I think these links cause problems in certain conditions (#230229). Perhaps if several packages are unpacked together? Despite what it says at the end of #230229, they were not cleaned up completely at that time. So I thought: finish the job. It may also prevent future problems. For me personally, the problem is only cosmetic. I was searching semi-automatically for links/alternatives/... that are "extra files" in the sense of package cruft and that may need changing in some way. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
