Hi Everyone,
I use tmux 1.9a on Mac 10.10.2 pretty heavily and I've noticed that
every couple of weeks lately the server simply dies.
I did some research and discovered the `-` flags to spit out logs.
A crash just happened, what do I do to figure out what's going on?
I've captured all the cl
I have this exact setup working. Maybe share your .tmux.conf?
Mine's here:
https://github.com/timvisher/bash_configuration/blob/master/dotfiles/tmux.conf
On Thu, Jul 17, 2014 at 10:18 PM, Frimann Kjerulf wrote:
> Hi
>
> I'm running iTerm2 on a mac and connecting to various tmux versions on a fe
On Tue, Feb 25, 2014 at 5:25 PM, Nicholas Marriott
wrote:
> What shell are you using? Does this happen in other shells?
I use bash. From my (perhaps wrong) experimentation with it in ksh, it
appears _not_ to happen. If you could give me a recipe for testing it
in a way that would give you informa
On Tue, Feb 25, 2014 at 10:00 AM, Nicholas Marriott
wrote:
> This is confusing, what is " do the same but just type a and so on until
> after it should have wrapped both for working and nonworking.
Attached.
> Also does the first line of "stty -a" match the actual rows an
On Tue, Feb 25, 2014 at 9:36 AM, Nicholas Marriott
wrote:
> Can you do the same with a working TERM and show me that typescript file
> too?
Attached.
[root@host ~]# TERM=screen
[root@host ~]# script
Script started, file is typescript
[root@host ~]# staho eustaeho usntaeho usntaeoh usntaeohu snae
On Tue, Feb 25, 2014 at 9:23 AM, Nicholas Marriott
wrote:
> if you run:
>
> eval `resize`
>
> in the shell does it help?
# eval `resize`
bash: resize: command not found
> if not, please run "script" then type at the prompt until it should have
> wrapped and then hit enter, type "exit"
On Mon, Feb 24, 2014 at 5:56 PM, Nicholas Marriott
wrote:
> So the problem is not that your PS1 doesn't wrap, it's that your typing
> into the shell prompt doesn't wrap.
I'm sorry. I thought that was clear but it clearly wasn't. :)
> Does it wrap if you type into "cat"?
Yes.
--
In Christ,
Ti
On Sat, Feb 22, 2014 at 12:35 PM, Nicholas Marriott
wrote:
> Hmm. Are you starting a new terminal each time you test or logging in
> and out or what?
Testing procedure is:
1. Edit terminfo
2. tic -x terminfo
3. ntmux test
4. prefix-key 1
5. type a bunch until i get to the right edge of the scree
On Fri, Feb 21, 2014 at 10:33 AM, Nicholas Marriott
wrote:
> You can just copy setaf and setab, the idea is to leave everything except
> them and colors alone
# infocmp -x screen screen-256color
comparing screen to screen-256color.
comparing booleans.
comparing numbers.
colors: 8,
On Fri, Feb 21, 2014 at 3:01 AM, Nicholas Marriott
wrote:
> On Thu, Feb 20, 2014 at 07:25:31PM -0500, Tim Visher wrote:
>> On Thu, Feb 20, 2014 at 6:40 PM, Nicholas Marriott
>> wrote:
>> > Did you try modifying a copy of screen terminfo from the running system
>>
On Fri, Feb 21, 2014 at 3:01 AM, Nicholas Marriott
wrote:
> On Thu, Feb 20, 2014 at 07:25:31PM -0500, Tim Visher wrote:
>> On Thu, Feb 20, 2014 at 6:40 PM, Nicholas Marriott
>> wrote:
>> > Did you try modifying a copy of screen terminfo from the running system
>>
On Fri, Feb 21, 2014 at 3:00 AM, Nicholas Marriott
wrote:
> Easy way to test is to change screen) to screen*) in the file and logout
> and in again but I suspect you are right and it's something else.
Yep. Something else. :)
--
In Christ,
Timmy V.
http://blog.twonegatives.com/
http://five.sen
On Thu, Feb 20, 2014 at 6:40 PM, Nicholas Marriott
wrote:
> Otherwise I suggest you also check the shell startup files (in /etc too)
> to see if there is anything that matches xterm and screen but not
> screen-*.
I did find something here but I'm unclear as to how to interpret it.
In the vanilla
On Thu, Feb 20, 2014 at 6:40 PM, Nicholas Marriott
wrote:
> Did you try modifying a copy of screen terminfo from the running system
> instead of copying it from another? You only really need colors, setaf
> and setab.
How would I go about doing that? All I find on my system are compiled
terminfo
On Thu, Feb 20, 2014 at 3:44 PM, Nicholas Marriott
wrote:
> How long is it and how wide is your terminal when it doesn't wrap? Or do you
> mean it doesn't wrap when you type?
# echo '$copy-of-current-prompt' | wc -c
64
It never wraps. Size of terminal doesn't seem to make any difference.
Small o
On Thu, Feb 20, 2014 at 3:25 AM, Nicholas Marriott
wrote:
> What's in your PS1?
# echo $PS1
[\u@\h \W]\$
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Commo
On Wed, Feb 19, 2014 at 6:02 PM, Nicholas Marriott
wrote:
> Check what is different between your screen and screen-256color with
> infocmp, there should be very little:
>
> $ infocmp -x screen screen-256color
# infocmp -x screen screen-256color
comparing screen to screen-256color.
comparing b
I'm on CentOS 5.8 using a back-ported screen256-color.terminfo that I
snagged from a copy of CentOS 6 using tmux 1.8.
With TERM=screen-256color, my prompt will not wrap long lines.
With TERM={screen,xterm,xterm-256color} my prompt wraps fine.
This is _not_ a tmux issue directly, as if I simply s
On Tue, Feb 18, 2014 at 6:36 AM, Marcel Partap wrote:
> Hi,
> please comment on this.
> - sends keyboard UP/DOWN sequences per mouse wheel event
> - active in alternate screen mode (like xterm)
> - also active when pressing SHIFT outside alternate screen (like
> previous iteration)
> - scrolls 3 l
19 matches
Mail list logo
