4 ms·
I'm not downvoting you if you show me a modern IDE that out-of-the-box(!) can do filename completion in the way Martin describes ("type 'articles emacs' to get
by deng 3y ago
I'm not downvoting you if you show me a modern IDE that out-of-the-box(!) can do filename completion in the way Martin describes ("type 'articles emacs' to get a list of any file paths that contain 'articles' and 'emacs' in their file path").
- cmrdporcupine 3y agoI believe the JetBrains tools can actually do this (ctrl-shift-N if I recall) and can do it for symbols, filenames, and classes, etc. Keyword match with some fuzzy logic. Though actually I'm not sure if they'll do it on directory name components or just the filename itself. They will, however, have 5x the memory and battery consumption and not be nearly as snappy in response time, nor nearly as customizable.
- deng 3y agoYou're right, I think it also can do this with directory components. I think if you'd type some like 'artic/emacs' it would actually work, but I cannot test at the moment. So no downvote from me.
- cmrdporcupine 3y agoNah, you should downvote... because the comment violated HN decorum guidelines and generally has bad manners?
- deng 3y agoHe's not wrong, though. I've been an Emacs user for decades, I'm still using it and I don't regret the time I have invested in it. It motivated me to learn LISP and a ton of other stuff, I love orgmode, calc, Gnus, and I wouldn't want to miss all that. But you have to see what it is good at and where it is severely lacking when it comes to modern software development. When younger developers see me using Emacs and ask me whether they should pick it up, I always say: if you'd like to be enlightened and get a glimpse of how the old LISP machines worked, if you like tinkering with complex systems just for the fun of it, go for it. There's a good chance it'll make you a better software developer eventually. However, if you simply want something that gets the job done, just use VSCode.
- cmrdporcupine 3y agoOk but he is wrong though. a) he's wrong to call it outdated... because that's not the case, it's a very vibrant community and with boatloads of dev happening b) he's wrong to say it only does 10% of blah blah blah -- capability wise my config does pretty much everything I had with CLion/RustRover in terms of my C++/Rust workflow... but also a whole lot more on other fronts c) he's wrong to formulate a comment like that because it's inflammatory and not nice Honestly, futzing with VSCode is pretty much as 'brittle' and 'batteries not included' situation as emacs, though obviously more popular. Every time I went from CLion over to VSCode I just threw my hands up in annoyance. My emacs + lsp + company + rust-analyzer + projectile + treemacs setup works better for me, though obviously that's somewhat because I have 30 years of mild-muscle-memory for emacs keybindings. (Though there is cua-mode, y'know) Would I recommend it for brand new devs, or for my 13-year old son starting out or something? Probably not. But it's really none of my business what tools other people use.