Mitchell Hashimoto

I usually ask them, why aren't you using Vim in a terminal? What's they're so close, so why aren't you doing that? And even going further then, I will ask people that simply use VS Code or a total non-editor, I mean, anything, what draws you to using a graphical interface over a terminal one? And right now, that answer is really easy in a lot of cases.

I usually ask them, why aren't you using Vim in a terminal? What's they're so close, so why aren't you doing that? And even going further then, I will ask people that simply use VS Code or a total non-editor, I mean, anything, what draws you to using a graphical interface over a terminal one? And right now, that answer is really easy in a lot of cases.

There's really obvious reasons why the terminal version is inferior. And my goal is to look into how to improve that. So concretely, for example, one of the things that brought up with Vim is that in the terminal version, you can't drag and drop things like images or even things like files to a certain extent. You can't just drag a file into Vim and have it open a new tab.

There's really obvious reasons why the terminal version is inferior. And my goal is to look into how to improve that. So concretely, for example, one of the things that brought up with Vim is that in the terminal version, you can't drag and drop things like images or even things like files to a certain extent. You can't just drag a file into Vim and have it open a new tab.

Going a little bit further, if you write

Going a little bit further, if you write

click in vim in the native app you'll get a native context menu and if you right click in the terminal you get this like kind of funky block character drawn one and that doesn't feel great in the native m you could have native tabs and so one of the things i'm actually looking into is how can you get a terminal program to be able to use native tab widgets even though it's driven by one program but it's showing up as multiple distinct tabs that you could pull out into separate windows and stuff like that

click in vim in the native app you'll get a native context menu and if you right click in the terminal you get this like kind of funky block character drawn one and that doesn't feel great in the native m you could have native tabs and so one of the things i'm actually looking into is how can you get a terminal program to be able to use native tab widgets even though it's driven by one program but it's showing up as multiple distinct tabs that you could pull out into separate windows and stuff like that

And I think even, you know, one of the more extreme ideas I have is that a community member brought up is like, what if you actually had also had a browser, which, which seems weird, because I'm painting them as a dichotomy, but I don't think they're necessarily dichotomy. The argument was,

And I think even, you know, one of the more extreme ideas I have is that a community member brought up is like, what if you actually had also had a browser, which, which seems weird, because I'm painting them as a dichotomy, but I don't think they're necessarily dichotomy. The argument was,

If you're browsing documentation, which is often in HTML, right now you have to do a link that opens in a browser in the same way that you could just draw text in a browser.

If you're browsing documentation, which is often in HTML, right now you have to do a link that opens in a browser in the same way that you could just draw text in a browser.

What if you could just embed a browser widget into part of your terminal UI so that the documentation part just is, that happens to just be normal browser technology without, so you could like live in this sort of platform for reasonable overlap, right? I'm not trying to replace the browser, but just for a reasonable amount. If you're,

What if you could just embed a browser widget into part of your terminal UI so that the documentation part just is, that happens to just be normal browser technology without, so you could like live in this sort of platform for reasonable overlap, right? I'm not trying to replace the browser, but just for a reasonable amount. If you're,

Yeah, if you're like opening a PDF, like why does the PDF have to open in a separate thing? It opens directly in the browser. Why can't a PDF open directly in a terminal? Stuff like that.

Yeah, if you're like opening a PDF, like why does the PDF have to open in a separate thing? It opens directly in the browser. Why can't a PDF open directly in a terminal? Stuff like that.

Exactly. And I don't think it's like why and then I don't think every answer is we have to make that work in a terminal. I just like I think the knowledge of knowing why and being critical about if you can maybe extend the point at which you have to eject is a useful thought exercise.

Exactly. And I don't think it's like why and then I don't think every answer is we have to make that work in a terminal. I just like I think the knowledge of knowing why and being critical about if you can maybe extend the point at which you have to eject is a useful thought exercise.

I think so. So there are terminal people out there that I don't need to shame, but they are like sort of militant about disliking multiplexers. I'm not that person. If you want to use a terminal multiplexer and ghosty, I want to make it work. However, I do think that terminal multiplexers make the terminal experience worse, but but there's no better option right now.

I think so. So there are terminal people out there that I don't need to shame, but they are like sort of militant about disliking multiplexers. I'm not that person. If you want to use a terminal multiplexer and ghosty, I want to make it work. However, I do think that terminal multiplexers make the terminal experience worse, but but there's no better option right now.