414 karma · joined November 19, 2017
This is why the tool places emphasis on feature flags and provides them as a built-in part of its solution. To give developers the power to work in the same branch without tripping over each other's feet.
I'm Aram and am the founder of both Devsession and Zellij (the OSS project that powers Devsession).
I've been devoting all of my time to Zellij as an OSS maintainer for over a year and am now starting Devsession as an attempt to make this work financially sustainable.
Would be happy to answer questions and I hope you like these labors of love I started!
If you'd be willing to open an issue in our Github repo: https://github.com/zellij-org/zellij with your pairing experiences, that would be great. If not, please do feel free to reach out personally: aram@poor.dev
Were you able to get screen to allow two different users to focus on two different panes in the same tab? As in, to see two different cursors and see each other typing in real time?
I think a big difference is that you'll get to have two different cursors in the same tab (and are able to focus on different panes).
My experience has taught me that tools become better the more people use them and are able to participate in their creation and maintenance. The more user friendly a tool is, the more users you'll have. Personally, I think a tool can be very user friendly and still powerful enough for advanced users.
I used a very similar setup to yours before I started Zellij! The reason I started the project was in order to be able to formalize such a setup (for me it was implemented as a soup of bash scripts which I dreaded moving to another machine, not to mention handing to another user).
One of the things we want to do with Zellij is port it to the web and maybe even in the future to use it as a sort of "backend" to power tiling window managers. I'd be totally open to do this in a standardized way if maintainers of other tiling managers are game.
Really, I think this mostly requires imagination from those of us developing for this platform. We have all the capabilities we need. We just need to create apps that don't require you to look up cheat sheets and man pages to use, and provide powerful alternatives to existing GUIs. There's a bit of a renaissance in this area as of late, but I feel this is just the beginning.
I'm 99% sure it's inserting ANSI escape codes (I'm maintaining a terminal emulator myself, and really that's how everything works), but I could of course be wrong.
The idea was that users should spend most of their time in "normal" mode, deferring to "locked" mode only for cases like you mentioned (ctrl-r in bash or in vim). The modal ergonomics are built on that.
I'd ideally like to find one word that describes locked mode better than "locked", which I agree is not ideal. I spent quite some time thinking about it and asking others, but most of us are not native English speakers - so maybe there's something obvious we're missing. :)
Would you be willing to open an issue in the github repo? I am not aware of this bug and would be very happy to address it.
I would especially be interested if this happens to be the same bug as: https://github.com/imsnif/bandwhich/issues/51
Thanks!
My major language in recent years has been javascript (and years before that perl). Rust was a breath of fresh air for me as I did not previously have "access" to system-level functionality.
I very much love the ease with which I can rely on other people's code (feels like home coming from node.js) - even though as mentioned in this thread it does have its downsides (eg. longer compiler times).
The learning curve is indeed challenging, but the tooling is amazing, the compiler has better error messages than I could even have imagined, and the community is incredibly friendly and welcoming. All in all, I'd say it's worth the effort. :)
I am the author of "what" and am very happy to hear people like this tool I made. :)
"what" was my first real attempt at rust, and I love the project very much.
That said, it is a hobby project - and so I will likely be a few days responding to all issues and contributions that came from this thread.
"what" has already received some great contributions that are major parts of the code base. I would be very happy for more (in the form of features, bug fixes, issues and packaging).
A note to those having issues installing: as mentioned in this thread, packaging for all the various linux distributions and mac is a great effort. I apologize that at the moment the installation is a little bumpy (especially for those not very familiar with rust).
A good first step for if "cargo install what" isn't working is to try to `rustup update` so you get the latest version of rust and cargo.
Other than that, I hope to support your setup in the future, and/or hear from you in the issues of the repo. Debug help for OSes I do not have access to would be greatly appreciated. :)
Thank you all!