Yash: Yet Another Shell
github.com
Yash: Yet Another Shell
1–10 of 54 posts
Re: Yash: Yet Another Shell
#2It's quite nice. However a few basic functions are missing, like separate history for each instance.
Re: Yash: Yet Another Shell
#3What's the tl;dr on why one would use Yash vs anything else? ReadMe doesn't really explain what's unique here.
Re: Yash: Yet Another Shell
#4Best “yet another*” project name in awhile. Cool stuff
Re: Yash: Yet Another Shell
#5I've never seen a mid-sized C codebase that annotate "restrict", "nonnull" pointers and "pure", "const" functions so thoroughly, very interesting, would be an important case study if I ever get around to write C optimizer passes.
Re: Yash: Yet Another Shell
#6What's the tl;dr on why one would use Yash vs anything else? ReadMe doesn't really explain what's unique here.
Might not be a goal of the author. Maybe they just wanted to make a shell :)
Re: Yash: Yet Another Shell
#7I kind of wish there was a shell that had the option for histories localized to a directory. So I can go into a directory and then look at what I was doing when I was last in that directory. Some complicated compilation command line to compile and link a source file and a bunch of libraries that was run when I was last in that directory, for example. There'd still be the 'history' command for everything and then maybe 'dhistory' for the commands that I ran in that specific directory when I was last there.
Re: Yash: Yet Another Shell
#8It's quite nice. However a few basic functions are missing, like separate history for each instance.
Scenario: Something forces a reboot. I've got 4 bash shells open. I've been doing some compilation & linking of libraries with a crazy long gcc command. After I reboot, that's not in my history because only the first-opened bash shell's history seems to get saved and I've gotta recreate the commandline again. Is there any shell that would let me see all the history from all of the different shells I might have had open?
Re: Yash: Yet Another Shell
#9I kind of wish there was a shell that had the option for histories localized to a directory. So I can go into a directory and then look at what I was doing when I was last in that directory. Some complicated compilation command line to compile and link a source file and a bunch of libraries that was run when I was last in that directory, for example. There'd still be the 'history' command for everything and then mayb…
atuin.sh
Re: Yash: Yet Another Shell
#10What's the tl;dr on why one would use Yash vs anything else? ReadMe doesn't really explain what's unique here.
You probably shouldn't. Some times it's just fun to write a shell.