Re: release cycle of tmux

2014-10-20 Thread Helmut Tessarek
On 20.10.14 22:21 , Thomas Adam wrote: > Why not have both? We appreciate on-going testing of tmux git until we decide > to release a new version. In fact, we rely on it. Ok, I'll work on a variant for MacPorts that people can install the latest git version of tmux. -- regards Helmut K. C. Tessa

Re: release cycle of tmux

2014-10-20 Thread Helmut Tessarek
On 20.10.14 21:05 , Thomas Adam wrote: > Well. That is a release cycle in itself. What is it you're really asking, and > why? I'm just a bit confused. I looked at the release dates for the different versions and I couldn't make out a pattern. In 2009 there were several releases and after 2009 rat

Re: release cycle of tmux

2014-10-20 Thread Helmut Tessarek
On 20.10.14 4:41 , Thomas Adam wrote: > Whenever Nicholas and I decide it appropriate, based on on-going patches, > number of features, etc. Ok, so basically there is no release cycle. Thx for the info. -- regards Helmut K. C. Tessarek lookup http://sks.pkqs.net for KeyID 0xC11F128D /* Thou

release cycle of tmux

2014-10-19 Thread Helmut Tessarek
What is the release cycle of tmux? There is quite some activity in the repo, but releases are cut rather seldomly. Cheers, Helmut -- regards Helmut K. C. Tessarek lookup http://sks.pkqs.net for KeyID 0xC11F128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at

Re: inconsistent status bar behavior

2014-09-29 Thread Helmut Tessarek
On 2014-09-29 12:16, Thomas Adam wrote: > Your shell is doing this---or rather, some part of how it's configured > is. If you're using something like bash, check to see if it's being > changed from PROMPT_COMMAND. Thanks, this seems to be the reason. PROMPT_COMMAND='printf "\033k%s@%s:%s\033\\"

Re: inconsistent status bar behavior

2014-09-29 Thread Helmut Tessarek
On 2014-09-29 12:22, Nicholas Marriott wrote: > Your shell is doing it. Either find where and stop it or turn off > allow-rename in tmux I don't understand how my shell would change tmux's behavior. Anyway, your other solution worked perfectly: set-window-option -g automatic-rename on set-option

inconsistent status bar behavior

2014-09-29 Thread Helmut Tessarek
I'm running tmux 1.9a on AIX 6/7, MacOSX 10.6.8/10.9.5, CentOS 6.5, Fedora 7, and Fedora 20. I'm using the same .tmux.conf for all systems: https://gist.github.com/tessus/149c80d9a1ed236bb770 On all OS, the status bar shows me the name of the shell, but on Fedora 20, the status bar shows me the a

Re: web site error

2014-09-15 Thread Helmut Tessarek
On 15.09.14 22:14 , Anish R Athalye wrote: > Well, theoretically, the error on the website could be an attacker's attempt > to get people to download malicious software or something. I agree, signing commits and/or tags makes sense. I just didn't get why you used this thread. > I didn’t mean t

Re: web site error

2014-09-15 Thread Helmut Tessarek
On 15.09.14 20:58 , Anish R Athalye wrote: > Could we start having GPG signed tagged releases? It’s a nice security > feature to have. What does this have to do with the error on the web site? -- regards Helmut K. C. Tessarek lookup http://sks.pkqs.net for KeyID 0xC11F128D /* Thou shalt not

web site error

2014-09-15 Thread Helmut Tessarek
Since today the web site shows tmux version 1.9 instead of 1.9a. Also the download link points to version 1.9. It's a little bit weird, because for a short period of time, the site even showed version 2.0. Something's off. Cheers, Hel -- regards Helmut K. C. Tessarek lookup http://sks.pkqs.ne

Re: tmux expands symlinks

2014-03-07 Thread Helmut Tessarek
Hi Nicholas, Thanks for the answers. > tmux uses file descriptors for paths now which is more robust but this > is one of the side effects. So this is the intended behavior. IMO, it's still a little bit strange, because it basically makes symlinks worthless. In most cases there is a reason why

tmux expands symlinks

2014-03-06 Thread Helmut Tessarek
Something has changed in 1.9 how tmux resolves directories. I start tmux in my home directory (/home/tessus): [tessus@atvie01s 0 ~]$ pwd /home/tessus [tessus@atvie01s 0 ~]$ tmux After starting tmux, the prompt in tmux looks like this (instead of the ~): [tessus@atvie01s 0 /data/home/tessus]$ I