Show HN: Hucksh – A shell with a very good memory • Hacker News Board

Re: Show HN: Hucksh – A shell with a very good memory

#71

Post by LarryClapp » Fri, Dec 22, 2023, 6:54 PM UTC

samstave wrote: post #59

This might sound strange, but one of the things I shave always wanted are what I would call "routes" --> A journey one goes down to either connect to something through some circuitous method, so to save that. Or to attempt to install or implement something that keeps package-creeping on you, so you could just have massive undo route. Or to be able to send someone a route that they can just watch, read or playback on…

I've read your comment a couple of times, and I think (maybe) I finally understand it.

I don't think hucksh (or any shell) could provide an automatic way to undo some series of arbitrary commands. If nothing else, "/bin/rm" is forever, generally speaking.

What it could do is let you select individual commands and then automatically combine them all into a single command that you can save or copy&paste to someone else. Right now, the UI shows the command ID, which is a database key, so you could do something similar yourself, something along the lines of

  hucksh sql "select command
    from command_history
    where id in (101, 103, 105, 107, 109)
    order by id"

where the "101, 103, 105, ..." are the IDs of the commands you entered and want to reify into a single "one-liner". Noting them and entering them by hand would be a drag, but it'd work.

Hope this helps. If I've misunderstood you in some way, let me know. Thanks for your comment, regardless. :)

Re: Show HN: Hucksh – A shell with a very good memory

#72

Post by LarryClapp » Fri, Dec 22, 2023, 7:07 PM UTC

chromakode wrote: post #47

artisin wrote: post #6

Here's my 2c. It's unlikely that many users, here or elsewhere, would be comfortable downloading and executing this Hacksh binary from your Dropbox, regardless of its benefits.

Agreed. I would not consider running a closed source shell because it's not auditable.

Yeah, I've worried about this a lot. Perhaps there's someone I could hire to give hucksh a clean bill of health. I wonder how much Bruce Schneier would charge? :) (That's a joke; I'm confident that, even if he'd do it, I couldn't afford him. But something like that is what I'm thinking of.)

Googling "security audit my code" finds several companies that offer such a service. My concern would be (aside from the admittedly non-trivial benefit of just having better code), would it make a difference to anybody that was on the fence about it? I suspect that the matrix of "potential customers" vs "what auditing service they'd trust" is large.

Thank you for the comment.

Re: Show HN: Hucksh – A shell with a very good memory

#73

Post by abeyer » Fri, Dec 22, 2023, 11:44 PM UTC

LarryClapp wrote: post #69

abeyer wrote: post #62

Earlier quoted context omitted.

> a vague sense of unease with using a closed source shell/terminal combo. That's much harder to overcome than paying for a shell/terminal combo. Of course, getting reasonably compensated for open source work is an even trickier problem. I actually see them compounding... either one alone isn't great, but combine them and you're left with a tool that can be rug-pulled out from under you at any time for any reason. OS…

> commercial non-OSS with a perpetual license at least means you can keep using an old version as long as you can manage That's what hucksh has. Today's license will work with today's code (and code released in the next year) forever. Sorry if that was unclear.

Oh, ok, that's at least more reasonable. Thanks for clarifying. (and for using such a license)

Not really unclear, now that I look closer, I just saw the annual rate and hadn't actually clicked through to the license/pricing details and assumed that to mean a typical SaaS subscription model. (it's cool and all, but not a fit for me based on the direction you're going.)