On Wednesday, February 20, 2013 at 11:49 PM, Nicholas Marriott wrote:
> Are you telling me that in iterm these are on by default? Even if tmux
> or the user doesn't ask for them?
>
>
No, sorry I wasn't clear. They are not on by default. You can turn them on the
same way you'd turn them on in tm
Hi, I see this item in TODO file: - support title stack, both internally
and externally
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1149299+0+archive/2010/freebsd-questions/20100207.freebsd-questions
How difficult is to implement that ? Are there any plans to implement
that in near future?
--
Perfect!
Thank you very much for the help!
Doug
On Tue, Feb 19, 2013 at 4:24 PM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
> Hi
>
> You need a grouped session, create it with tmux new -tfirstsession.
>
>
> On Tue, Feb 19, 2013 at 03:47:45PM -0800, Douglas Mayle wrote:
> >Hi al
Are you telling me that in iterm these are on by default? Even if tmux
or the user doesn't ask for them?
On Wed, Feb 20, 2013 at 04:42:01PM -0800, Aaron Jensen wrote:
>On Wednesday, February 20, 2013 at 3:56 PM, Aaron Jensen wrote:
>
> On Wed, Feb 20, 2013 at 3:36 PM, Nicholas Marriot
Aleks pinged me and wanted to weigh in directly (CCing to get him on the
thread)
On Wednesday, February 20, 2013 at 4:42 PM, Aaron Jensen wrote:
>
>
> On Wednesday, February 20, 2013 at 3:56 PM, Aaron Jensen wrote:
>
> > On Wed, Feb 20, 2013 at 3:36 PM, Nicholas Marriott
> > mailto:nichola
On Wednesday, February 20, 2013 at 3:56 PM, Aaron Jensen wrote:
> On Wed, Feb 20, 2013 at 3:36 PM, Nicholas Marriott
> mailto:nicholas.marri...@gmail.com)> wrote:
> > I will look at the diff tomorrow, but I don't see why we need an option.
> >
> > If you enable focusing in your terminal, you'l
On Wed, Feb 20, 2013 at 3:36 PM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
> I will look at the diff tomorrow, but I don't see why we need an option.
>
> If you enable focusing in your terminal, you'll get it in tmux (if the
> application has turned it on). That's what you want, righ
Thanks, I actually meant window_id, but wrote window_index. I will try this
out.
-Anthony
On Feb 20, 2013, at 3:30 PM, Nicholas Marriott
wrote:
> select-window -t:foo
>
> But note that foo will follow the normal rules to match window names, so
> if you want it to be only exact match you wil
Ok no worries, thanks.
On Wed, Feb 20, 2013 at 08:48:11PM +0100, Romain Francoise wrote:
> Nicholas Marriott writes:
>
> > This is with:
>
> > valgrind --leak-check=full --trace-children=yes --trace-children-skip=*sh
> > --log-file=out ./tmux new
>
> > How are you running valgrind?
> > Are yo
I will look at the diff tomorrow, but I don't see why we need an option.
If you enable focusing in your terminal, you'll get it in tmux (if the
application has turned it on). That's what you want, right?
On Wed, Feb 20, 2013 at 07:43:35AM -0800, Aaron Jensen wrote:
>On Tuesday, February 19,
select-window -t:foo
But note that foo will follow the normal rules to match window names, so
if you want it to be only exact match you will need to have a script to
find it from lsw like what you have, although I suggest you use
#{window_id} not #{window_index}.
If you don't care about exact mat
On 20 February 2013 22:59, Anthony Molinaro wrote:
> Hi,
>
> I was trying to figure out if there is a way to select a window by its
> name programmatically. Specifically, I want a shell script that does
> the following
>
> #!/bin/sh
>
> window=$1
>
> if ; then
>
> else
> tmux new-window -n
Hi,
I was trying to figure out if there is a way to select a window by its
name programmatically. Specifically, I want a shell script that does
the following
#!/bin/sh
window=$1
if ; then
else
tmux new-window -n $window
fi
It seems like for the first command, I can use tmux list-windows
Nicholas Marriott writes:
> This is with:
> valgrind --leak-check=full --trace-children=yes --trace-children-skip=*sh
> --log-file=out ./tmux new
> How are you running valgrind?
> Are you sure you are using a clean, unmodified checkout from latest git?
> What are you doing to test?
I have a l
On Wednesday, February 20, 2013 at 8:21 AM, Aaron Jensen wrote:
> Updated patch. Something that is confusing to me is that when I turn the
> filter off, something is still preventing ^[[O from getting printed to the
> screen. I'm guessing something in tux's input key handling is filtering them
>
Updated patch. Something that is confusing to me is that when I turn the filter
off, something is still preventing ^[[O from getting printed to the screen. I'm
guessing something in tux's input key handling is filtering them out? It makes
me wonder how I ever saw it and if the filtering is reall
On Tuesday, February 19, 2013 at 11:53 PM, Aaron Jensen wrote:
> 3) I removed the option completely, it's not needed I don't think.
>
> 4) akracun had added some logic to let panes track their focus status so they
> couldn't ever get double notified. It's not a bad idea, but I was worried
> that
For your set global options:
tmux show -g
tmux showw -g
For default:
tmux -Ltmp -f/dev/null start\; show -g
tmux -Ltmp -f/dev/null start\; showw -g
On Wed, Feb 20, 2013 at 10:26:37AM +0530, Sinbad wrote:
>how can i all the set options values, all the configured and
>default ones, much
18 matches
Mail list logo
