Re: Simple patch to indicate prefix-status in status line
Hello, On Thu, Aug 09, 2012 at 08:04:46PM +, Andrew Reynhout wrote: > Hi, > > I'm attaching a small patch. It adds a token to the status line format > which will indicate whether you're in command-mode or not. I'm not sure how Nicholas feels about this, but this has been on the TODO list for a while. I think ideally this should use some form of status-bg colour change instead of relying on some specific part of the status line to draw some random ASCII symbol. This would certainly make the code cleaner. Also, you don't need to keep calling server_status_client() each time the CLIENT_PREFIX flag is toggled -- it would be easier to just set it, and let the status_draw() routines handle this when we know a refresh of the status line is needed. Do you think you could repropose a patch like this instead? -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
Please help building tmux on Solaris 10 and a suggestion
On Sat, Aug 11, 2012 at 08:28:52AM +0100, Nicholas Marriott wrote: > Hi > > Does using TERM=vt220 help? Hi and sorry for the lame subject line. I realized it after I hit the send key but it was too late! Not sure I got your meaning. exporting TERM to vt220 before the configure and build doesn't change anything, nor does it help before starting tmux. This still shows in the configure (output is the same as in original posting) > > checking for sys/tree.h... no > > checking term.h usability... no > > checking term.h presence... yes > > configure: WARNING: term.h: present but cannot be compiled > > configure: WARNING: term.h: check for missing prerequisite headers? > > configure: WARNING: term.h: see the Autoconf documentation > > configure: WARNING: term.h: section "Present But Cannot Be Compiled" > > configure: WARNING: term.h: proceeding with the compiler's result > > checking for term.h... no > > tmux builds fine but when I use it the terminal sessions don't work (as in > > various cursor movement keys like backspace go forward instead of backward) > > until I manually enter > > > > export TERM=xterm > > > > in each tmux window. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
Re: Please help building tmux on Solaris 10 and a suggestion
Oh sorry I misread your mail. What does "echo $TERM" show inside tmux, before you do the export command? On Sun, Aug 12, 2012 at 10:33:20AM +, John Long wrote: > On Sat, Aug 11, 2012 at 08:28:52AM +0100, Nicholas Marriott wrote: > > Hi > > > > Does using TERM=vt220 help? > > Hi and sorry for the lame subject line. I realized it after I hit the send > key but it was too late! > > Not sure I got your meaning. exporting TERM to vt220 before the configure > and build doesn't change anything, nor does it help before starting tmux. > > This still shows in the configure (output is the same as in original posting) > > > > checking for sys/tree.h... no > > > checking term.h usability... no > > > checking term.h presence... yes > > > configure: WARNING: term.h: present but cannot be compiled > > > configure: WARNING: term.h: check for missing prerequisite headers? > > > configure: WARNING: term.h: see the Autoconf documentation > > > configure: WARNING: term.h: section "Present But Cannot Be Compiled" > > > configure: WARNING: term.h: proceeding with the compiler's result > > > checking for term.h... no > > > > tmux builds fine but when I use it the terminal sessions don't work (as in > > > various cursor movement keys like backspace go forward instead of > > > backward) > > > until I manually enter > > > > > > export TERM=xterm > > > > > > in each tmux window. > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > tmux-users mailing list > tmux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tmux-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
Tmux unexpectedly crashed
Hi, I just experienced an unexpected crash of tmux. I had 5 or so windows open with Vim running in one and Zsh shells in the others. After changing an environmental variable in my ~/.zshrc, I switched to another window and did a `. ~/.zshrc` to source my zshrc file. At that point the tmux session just disappeared without leaving the [exited] message, or any message at all. % tmux attach-session no sessions % tmux ls failed to connect to server: Connection refused There was a 1.3MB core file left behind however: % file core core: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), SVR4-style, from 'tmux' Would it be helpful to send that file to someone in the interest of figuring out what happened? Thanks, John -- John Magolske http://B79.net/contact -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
RE: [PATCH 0/6] Basic local printing support
> Date: Sat, 11 Aug 2012 08:31:15 +0100 > From: nicholas.marri...@gmail.com > > Thanks for your work but can you explain why you want/need this? Does > anything actually use it? > Hi Nicholas, Use it for sending to a local printer when on the road, and also on occasion with Putty to capture to the Windows clipboard. Offering it up for the benefit of anyone else who might find it useful, but am happy to keep it as a private patch set as well. Either way, the last 2 patches are good cleanups even if you're not convinced about the others. Cheers, Sean -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
