Package Details: tmuxinator 3.1.2-1

Git Clone URL: https://aur.archlinux.org/tmuxinator.git (read-only, click to copy)
Package Base: tmuxinator
Description: Manage complex tmux sessions easily
Upstream URL: https://github.com/aziz/tmuxinator
Licenses: MIT
Submitter: lucacesari
Maintainer: fryfrog (flipee)
Last Packager: fryfrog
Votes: 75
Popularity: 0.125540
First Submitted: 2013-06-26 07:49 (UTC)
Last Updated: 2024-02-18 05:30 (UTC)

Dependencies (6)

Required by (1)

Sources (2)

Pinned Comments

FrederickZh commented on 2021-04-15 13:37 (UTC)

@lewiji You need to rebuild AUR ruby gems after major ruby upgrades: paru -Qqo /usr/lib/ruby/gems/2.7.0 | paru -S -- -

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »

mehalter commented on 2019-11-28 14:10 (UTC)

Is there a way to unflag a package marked out of date? This package was flagged out of date, but is currently the latest version.

solatis commented on 2019-05-02 05:38 (UTC)

Can someone update this? The current version triggers a warning with tmux 2.9, and 1.0.0 has been released.

noirvent commented on 2019-02-12 08:46 (UTC)

@archerie Had the same problem. Actually reinstalling package ruby-erubis and whatever package tmuxinator is complaining about (for me there was ruby-xdg too) with pacman did the trick

cgirard commented on 2019-01-14 13:07 (UTC)

@deathsbreed: you should rebuild your ruby-* packages after ruby version update.

deathsbreed commented on 2019-01-14 12:05 (UTC)

After an update of tmuxinator, it started failing saying that it couldn't find the erubis gem, which I did have installed. Turns out the erubis gem was located in /usr/lib/ruby/gems/2.5.0 while my GEM_PATH only included /usr/lib/ruby/gems/2.6.0. I'm not sure how one would solve this, but as a temporary fix you can just add the line export GEM_PATH="$GEM_PATH:/usr/lib/ruby/gems/2.5.0" to your .bashrc or whatever shell rc file you have.

marceljoseph commented on 2018-11-13 23:01 (UTC)

Is it possible to add the completion plugins to ~/.bin as stated in the readme upstream?

asermax commented on 2018-10-21 00:10 (UTC) (edited on 2018-10-21 00:13 (UTC) by asermax)

@slav if you want to disable the message until the mantainer's update their code, you can go into /usr/lib/ruby/gems/2.5.0/gems/tmuxinator-0.12.0/lib and modify the tmuxinator.rb file to include 2.8 as a valid version.

@deathsbreed you could auto apply that change through a patch on the PKGBUILD, but it's probably more work than it's worth, it's probably gonna get update soon anyways :P

slav commented on 2018-10-19 19:57 (UTC) (edited on 2018-10-19 20:00 (UTC) by slav)

@deathsbreed Thanks for letting know. Yes I ignore it. I just would like to report that it happen after Tmux upgrade to last version.

deathsbreed commented on 2018-10-19 08:47 (UTC)

slav, this happen because of how tmuxinator is written. They have it programmed to recognize deprecation, but only by comparing it to a list of supported version strings instead of trying to see if the version of tmux is later than v1.5. I'd say you should simply ignore it until tmuxinator updates itself. There might also be an option to omit that message, but I am not aware of it.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »