6 ms·
File Explorer is merged to Helix editor
- manusachi 2y agoOne of the long-awaited features was recently merged!
- timeon 2y agoI get that Helix is really fast (I also use it sometimes) but some of those screen-grabs could be made bit slower so one could see what is actually happening. Anyway I hope this will be soon included in release! (Even if current <space>+f is also pretty good.)
- abhinavk 2y agoThese are HTML <video> controls. You can right-click and set a speed.
- georgeck 2y agoI agree. Capturing the interaction as a movie (like .mov file) makes it really difficult to understand what the user is doing. e.g. What keystrokes did the user press to finish this interaction. I wish folks would post screen grabs with tools like https://asciinema.org/ https://asciinema.org/ - this is what the helix-editor homepage uses to show the features. This is ideal for terminal apps. That said, I wish asciinema can also show the key strokes a an annotation with the ability for the viewer to pause on each keyboard interaction.
- contingencies 2y ago... but can it read emails? Jamie Zawinski's Law: Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.
- chamomeal 2y agoThey’re working on a scheme-based plugin system, so… almost!
- miki123211 2y agoAnd a corollary to this law: Except for programs embedded in applications that can already read mail (notably web apps)
- pkulak 2y agoI was waiting for this to try switching… and now I’ve discovered oil.nvim and can never go back.
- deleted 2y ago[deleted]
- Celeo 2y agoGreat news! When I'm familiar with the project space+F works great, but isn't great for discovery.
- jll29 2y agoI like the idea of doing browsing in folders containing files as navigating between edit buffers. I've been editing like that since the 1990s because that's how Emacs and XEmacs do it (M-x dired command). The ease and speed of just pressing RETURN on the .. menu to go up or on the folder name to open and look inside is unrivalled and much faster than using my mouse (and better for health - avoids RSI). Would be cool for Helix to get Emacs-like directories-as-edit-buffers functionality!
- phplovesong 2y agoOil for nvim is THE best explorer i have used. Highly recommend
- marliechiller 2y agoyazi for me!
- atkailash 2y agoI recently tried yazi after trying a few other cli file explorers and after I settle my current dot file redo I’m gonna dig into it some more
- kombine 2y agoIt is the best explorer for me too. It blends into the rest of the vim so much so that you don't feel the difference between manipulating text and files.
- CaptainOfCoit 2y agoI've been using vim/neovim for decades, and "so that you don't feel the difference between manipulating text and files" made no sense. Then I watched a video from the README (https://github.com/stevearc/oil.nvim https://github.com/stevearc/oil.nvim) and yup, that looks amazing and makes so much sense. Thanks GP for mentioning it!
- cassepipe 2y agoFor people to understand your enthusiasm I feel like you should try to explain why : It uses a buffer/pop to navigate and edit files like you're inside a buffer
- zamalek 2y agoWhat I really want to see merged is the tokens in shell commands. dotnet is my day job, and the boilerplate (its luckily just namespace nowadays) gets repetitive and typo-prone. If I could just (approximately) `dotnet new class -o $cwd`... Instead we have something like 3 closed PRs for this.
- punkbit 2y agoI used to believe that a File explorer is crucial in my text editor; after using Helix for more than a year, I’ve discovered that is not required at all; space+f much faster use flow. I work with split terminal windows, where I have supporting windows to navigate the file system. Happy to try a file explorer once again, it’ll be interesting to see how I feel a year later.
- TacticalCoder 2y ago> I’ve discovered that is not required at all; space+f much faster use flow. Some use "fuzzy find" on the filename, which is ultra fast too. I use something even faster IMO: typically I know at least some of the text of the source / test code file I want to go to. So I either use a function of the editor that can "find usage" or... I simply use ripgrep, integrated in my editor, and start typing text I know is in the file I want to visit. I still use, sometimes, a "file explorer" to find the file to open but it's not the most common. In a way using a file explorer is "sort": things are arranged in folders/directories. Fuzzy search or finding usages or ripgrep is "search". So, basically: "search, don't sort"
- homebrewer 2y agoYou're shadowbanned, mate, almost all your comments from at least the last couple of weeks are dead.
- CaptainOfCoit 2y agoProbably not the best venue, but if you read through the comments, kind of makes sense. "Assume good faith", "Converse curiously" and "Eschew flamebait" are part of the guidelines for commenting, for good reasons.
- bryanrasmussen 2y agoI don't think they're shadowbanned, just a lot of the comments have been banned the old-fashioned way.
- 2y ago
- gigatexal 2y agoYay!!! Been waiting!!!
- gigatexal 2y agoNvm this has been around for a while. Still a simple file explorer would be nice for when you want to browse the structure.