[tmux:tickets] #104 changing terminal-overrides has no effect
--- ** [tickets:#104] changing terminal-overrides has no effect** **Status:** open **Created:** Sat Feb 22, 2014 11:33 PM UTC by Ian! D. Allen **Last Updated:** Sat Feb 22, 2014 11:33 PM UTC **Owner:** nobody Changing the value of `terminal-overrides` has no effect on the current session. You have to detach the session and re-attach it before the new value is used. If the session is part of a grouped session, even detach/attach won't work. The changed value of `terminal-overrides` is never used once a session is grouped. Whatever value is set stays set once the session is grouped. If you kill off all but one of the groups, then you can make `tmux` use the changed value using detach/attach on the last session. Mentioning these two things would be helpful in the man page. --- Sent from sourceforge.net because tmux-users@lists.sourceforge.net is subscribed to https://sourceforge.net/p/tmux/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/tmux/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk___ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
[tmux:tickets] #103 set-option incorrectly removes trailing semicolon
--- ** [tickets:#103] set-option incorrectly removes trailing semicolon** **Status:** open **Created:** Sat Feb 22, 2014 10:59 PM UTC by Ian! D. Allen **Last Updated:** Sat Feb 22, 2014 10:59 PM UTC **Owner:** nobody You type: :set-option status-right 'foo;' or at the command line: $ tmux set-option status-right 'foo;' where `status-right` is any string option and `tmux` replies incorrectly with: Set option: status-right -> "foo" deleting the trailing semicolon. I found this trying to do this: :set-option terminal-overrides '*:tsl=\E]0;' It is not good to have that semicolon deleted. Don't do that. --- Sent from sourceforge.net because tmux-users@lists.sourceforge.net is subscribed to https://sourceforge.net/p/tmux/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/tmux/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk___ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
[tmux:tickets] #102 starting-directory (-c) option not working
--- ** [tickets:#102] starting-directory (-c) option not working** **Status:** open **Created:** Sat Feb 22, 2014 08:52 PM UTC by jfelchner **Last Updated:** Sat Feb 22, 2014 08:52 PM UTC **Owner:** nobody I just upgraded to 1.9 and I'm having a bit of an issue with the new -c option which was added to 'new-session' and 'new-window'. I have a function which I can pass a project name and it will open a new tmux session/window set for the project. I have the following lines in a function that I execute: old_tmux="$TMUX" unset TMUX tmux new-session-A -d -s "$session_name" -c "$working_directory" tmux send-keys -t "$session_name" "$EDITOR ." C-m tmux new-window -t "$session_name" -c "$working_directory" tmux select-window -t "$session_name:1" export TMUX="$old_tmux" Everything works great, but when I open new windows or panes, it defaults to my home directory instead of the value of $working_directory. The initial windows however open in the "$working_directory". I'm on Mac OSX 10.8 --- Sent from sourceforge.net because tmux-users@lists.sourceforge.net is subscribed to https://sourceforge.net/p/tmux/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/tmux/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk___ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
Expand AUTHOR section in man page?
Hi,
I've read in the man page for tmux only one author, but i think thats
a mistake as there are more, as shown -
.
$ grep -ri 'copyright (c)' *.c | awk '{print $6, $7}' | sort | uniq
George Nachman
Jonathan Alvarado
Joshua Elsasser
Marcel P.
Nicholas Marriott
Romain Francoise
Thiago de
Thomas Adam
Tiago Cunha
.
but these are not under that man page section.
David Chanters
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
Re: Expand AUTHOR section in man page?
On Sun, Feb 23, 2014 at 09:31:35PM +, David Chanters wrote:
> Hi,
>
> I've read in the man page for tmux only one author, but i think thats
> a mistake as there are more, as shown -
>
> .
> $ grep -ri 'copyright (c)' *.c | awk '{print $6, $7}' | sort | uniq
> George Nachman
> Jonathan Alvarado
> Joshua Elsasser
> Marcel P.
> Nicholas Marriott
> Romain Francoise
> Thiago de
> Thomas Adam
> Tiago Cunha
> .
>
> but these are not under that man page section.
No, but then so what? What about the other countless people who've
contributed just patches or one-time bug fixes, shouldn't they be included
here as well?
The list soon becomes rather unweildy and unmaintainable. It's true that by
accident on your part, that list above mentions the more "serious" tmux
contributors who've perhaps contributed a lot more code, but I don't think
having to maintain this list is worth it every time.
-- Thomas Adam
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
Re: Expand AUTHOR section in man page?
Mr Thomas -
On 23 February 2014 21:37, Thomas Adam wrote:
> On Sun, Feb 23, 2014 at 09:31:35PM +, David Chanters wrote:
>> Hi,
>>
>> I've read in the man page for tmux only one author, but i think thats
>> a mistake as there are more, as shown -
>>
>> .
>> $ grep -ri 'copyright (c)' *.c | awk '{print $6, $7}' | sort | uniq
>> George Nachman
>> Jonathan Alvarado
>> Joshua Elsasser
>> Marcel P.
>> Nicholas Marriott
>> Romain Francoise
>> Thiago de
>> Thomas Adam
>> Tiago Cunha
>> .
>>
>> but these are not under that man page section.
>
> No, but then so what? What about the other countless people who've
> contributed just patches or one-time bug fixes, shouldn't they be included
> here as well?
>
> The list soon becomes rather unweildy and unmaintainable. It's true that by
> accident on your part, that list above mentions the more "serious" tmux
> contributors who've perhaps contributed a lot more code, but I don't think
> having to maintain this list is worth it every time.
Then we might just include the list I gave above if those are the more
important ones?
David Chanters
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
Re: Expand AUTHOR section in man page?
If anyone who has contributed feels they don't have enough recognition
they are free to come and talk to me themselves.
On Sun, Feb 23, 2014 at 09:31:35PM +, David Chanters wrote:
> Hi,
>
> I've read in the man page for tmux only one author, but i think thats
> a mistake as there are more, as shown -
>
> .
> $ grep -ri 'copyright (c)' *.c | awk '{print $6, $7}' | sort | uniq
> George Nachman
> Jonathan Alvarado
> Joshua Elsasser
> Marcel P.
> Nicholas Marriott
> Romain Francoise
> Thiago de
> Thomas Adam
> Tiago Cunha
> .
>
> but these are not under that man page section.
>
> David Chanters
>
> --
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
> ___
> tmux-users mailing list
> tmux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tmux-users
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
