Mitchell Hashimoto
๐ค SpeakerAppearances Over Time
Podcast Appearances
Yeah, I completely agree. It's actually one of the last remaining discussion points before the 1.0 is some of these defaults that we want to set in that sense. Because the trade-off between these defaults is that if we put those key bindings as defaults or those behaviors as defaults, then things like TUI programs can't map them because you're taking over them.
Yeah, I completely agree. It's actually one of the last remaining discussion points before the 1.0 is some of these defaults that we want to set in that sense. Because the trade-off between these defaults is that if we put those key bindings as defaults or those behaviors as defaults, then things like TUI programs can't map them because you're taking over them.
And so do you want to actually... We're talking about whether that's important or not or if it's more important that by default people expect what you just did. And I think it's also important when I consider that it's where people are coming from. If you're coming from Terminal.app or iTerm or something, then this is likely to not really be an issue because we behave... almost identical to those.
And so do you want to actually... We're talking about whether that's important or not or if it's more important that by default people expect what you just did. And I think it's also important when I consider that it's where people are coming from. If you're coming from Terminal.app or iTerm or something, then this is likely to not really be an issue because we behave... almost identical to those.
But if you're coming from something like Warp, then yeah, it's going to be a big issue. And so... I'm not super sure. I mean, that discussion actually did lead to the sort of, I think, extreme path, which we're not going to go down because it's too complicated, of inspecting their machine to be like, are you a ZShell user? Were you a warp? Is warp installed?
But if you're coming from something like Warp, then yeah, it's going to be a big issue. And so... I'm not super sure. I mean, that discussion actually did lead to the sort of, I think, extreme path, which we're not going to go down because it's too complicated, of inspecting their machine to be like, are you a ZShell user? Were you a warp? Is warp installed?
Like, should we behave more like warp on first startup? Like, are we going to guess basically based on what you have? And I'm not ready to go down that path yet. We do it. We do that for other things, but I'm not ready to go down that path for things like input manipulation. But it's unfortunately complicated. But I agree with you.
Like, should we behave more like warp on first startup? Like, are we going to guess basically based on what you have? And I'm not ready to go down that path yet. We do it. We do that for other things, but I'm not ready to go down that path for things like input manipulation. But it's unfortunately complicated. But I agree with you.
I, I, I fight the nerd snipe every day of my life to write a shell. I, I, that's, that's something I'm holding. When are you going to give in, man?
I, I, I fight the nerd snipe every day of my life to write a shell. I, I, that's, that's something I'm holding. When are you going to give in, man?
I'm holding strong. Cause there's so many bug reports. So many that I get that I am like, this is a shell bug, not my bug. But then, you know, I do think I do. I don't just dismiss it. I do think, can I as a terminal emulator, uh, mitigate this bug. But ultimately, this is not my bug. And so, yeah, it's frustrating.
I'm holding strong. Cause there's so many bug reports. So many that I get that I am like, this is a shell bug, not my bug. But then, you know, I do think I do. I don't just dismiss it. I do think, can I as a terminal emulator, uh, mitigate this bug. But ultimately, this is not my bug. And so, yeah, it's frustrating.
It's also frustrating because all the cool new post 1.0 features we want to build that we kind of touched on, it's going to be blocked on downstream adoption. right? It's like any, you know, web browser comes out with a feature. It doesn't matter until a website implements it. And so that's going to happen here too.
It's also frustrating because all the cool new post 1.0 features we want to build that we kind of touched on, it's going to be blocked on downstream adoption. right? It's like any, you know, web browser comes out with a feature. It doesn't matter until a website implements it. And so that's going to happen here too.
But if we have, I've, I've joked around building a ghosty shell that only works in the ghosty terminal emitter. So it's kind of crap because you would never use it remotely, but like, it's more of a tech demo of like, this is what shells could be if they implement all the capabilities of ghosts. It's kind of like Chrome web experience, web experiments.
But if we have, I've, I've joked around building a ghosty shell that only works in the ghosty terminal emitter. So it's kind of crap because you would never use it remotely, but like, it's more of a tech demo of like, this is what shells could be if they implement all the capabilities of ghosts. It's kind of like Chrome web experience, web experiments.
Like we need the ghosty terminal experiments to like, where people visit it and with the Chrome one, like I would visit it and be like, holy crap, a browser could do this. And then it changed my whole perception of a browser, like sometimes years before any website behaved similarly. And I have talked with, with folks about doing the same thing for terminals.
Like we need the ghosty terminal experiments to like, where people visit it and with the Chrome one, like I would visit it and be like, holy crap, a browser could do this. And then it changed my whole perception of a browser, like sometimes years before any website behaved similarly. And I have talked with, with folks about doing the same thing for terminals.
this 2e works best in ghosty you know that's already happening i think more than people expect um i would i would say right now like neovim works best in ghosty and then it works it degrades great for other for other things but they're i think almost the entire neovim
this 2e works best in ghosty you know that's already happening i think more than people expect um i would i would say right now like neovim works best in ghosty and then it works it degrades great for other for other things but they're i think almost the entire neovim