Mike Sawka

Thanks for submitting. These are all great suggestions. Will have to look through each individually to see if they are a fit and how they could be integrated.

Ah, this is something I never thought about making customizable, but I like it! What type of granularity do you think would be most useful? A global setting, a setting...

I think a confirm for this might be annoying. My thought here is to provide some small window of undo (maybe 5 seconds). So, if you accidentally delete a block...

this is something that we would really like to support, but it is likely more of a medium term priority given all the other issues that we have to fix...

Ah, thanks for reporting, will take a look -- probably like you said that we're not re-reading the original output correctly when transferring a running command. Quick question, was there...

Thanks for submitting! Completely integrating bash history could be tricky. Your suggestion about having bash history show up as a separate option in ctrl-r is really good though -- that...

100% yes! We have already organized the code base so our viewers are located in the `src/plugins` directory and we are working to finalize a v1 of the core plugin...

This could be tricky, as we've never tested a non-64-bit version of waveshell/mshell. I just verified that it does build correctly, but I don't have a test environment. We're close...

Hi, thanks for submitting the issue! A couple quick questions: * "add icon to remove item from history" -- got it, this makes sense. * "edit item/prompt from history" --...

Thanks for submitting! I like this idea. The "move *or* copy" makes sense too. We also will have a way to bookmark commands and create playbooks, but are still playing...