(It'd be great to have someone else confirm that they're able to build/run it!) It supports the most basic use case of allowing a user to define a number of project configuration options (create n windows split window n into nn panes scope each window/session/pane to a given directory run a series of commands in each pane, etc.) in a TOML file and it then uses that configuration to spawn a tmux session. Rmuxinator is pre-alpha, but it is functional and I plan to keep picking at it as I find time. (For instance, project configuration files are implicitly typechecked by Serde which cleaves off a bunch of ad hoc validation that happens in tmuxinator.) This is not a performance critical project, but it should eventually be much faster, too. In addition to greatly simplifying distribution of the utility, the program is much more robust due to Rust's nature. Since I'd been experimenting with Rust for some time and wanted to dive into a project that might actually be useful, I've started working on a tmuxinator successor written in Rust: rmuxinator. There are ways to "simplify" the distribution of Ruby gems by shipping a Ruby interpreter along with the library or using containers, but, IMO, both of those options are too complex. The project is available via a few different package managers, but those can/do present other problems relating to the issues mentioned above. Installing and using the library can be problematic for people not familiar with the Ruby ecosystem. as a result of the project being written in Ruby (its dynamic runtime, reliance on RubyGems, etc.). Tmuxinator is widely used and stable, but there are regularly issues arising around installation, distribution, etc. I'm one of the maintainers of tmuxinator, a Ruby library which allows users to manage tmux sessions using project configuration files. We'll do our best to keep these links up to date, but if we fall behind please don't hesitate to shoot us a modmail. This is not an official Rust forum, and cannot fulfill feature requests. ![]() Err on the side of giving others the benefit of the doubt.Īvoid re-treading topics that have been long-settled or utterly exhausted. Please create a read-only mirror and link that instead.Ī programming language is rarely worth getting worked up over.īe charitable in intent. If criticizing a project on GitHub, you may not link directly to the project's issue tracker. Post titles should include useful context.įor Rust questions, use the stickied Q&A thread.Īrts-and-crafts posts are permitted on weekends.Ĭriticism is encouraged, though it must be constructive, useful and actionable. For content that does not, use a text post to explain its relevance. ![]() Posts must reference Rust or relate to things using Rust. We observe the Rust Project Code of Conduct. Strive to treat others with respect, patience, kindness, and empathy. Please read The Rust Community Code of Conduct The Rust Programming LanguageĪ place for all things related to the Rust programming language-an open-source systems language that emphasizes performance, reliability, and productivity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |