If it turns out to be the case, I'll still go to the interview but never work with that recruiter again. We've reached a point in tech now where processes are (nearly) tool agnostic; and to focus on that given the context of the resume (which the role based on my experience in the role with other companies), this is especially true. I don't need to rely on notepad to manipulate CSV data, I can easily use Excel, Sublime or any other tool that can open a comma separated file.
So I'm going to softly reject the notion that this recruiter was looking for someone who uses a specific tool. With the experience you mentioned, I can absolutely see why they'd want a certain toolset because perhaps their internal development lifecycle relies on features not present elsewhere.
If that's the case with a recruiter, it's entirely their job and responsibility to their candidates to find this out and outline it in a job post to explain this without inundating interested prospects with tool-speak. This could have easily been accomplished, but it wasn't.