:
>
>Vertical is top-bottom split of course, that's obvious, your
>perception
>of what is intuitive is wrong.
>
>On Fri, Dec 21, 2012 at 10:14:24AM +0530, Sinbad wrote:
>> * *ok, :join-pane -h -t 1 -s 2, did what i was looking for.
Fri, Dec 21, 2012 at 3:30 PM, Nicholas Marriott
><[1]nicholas.marri...@gmail.com> wrote:
>
> Vertical is top-bottom split of course, that's obvious, your perception
> of what is intuitive is wrong.
>
> On Fri, Dec 21, 2012 at 10:14:24AM +0530, Sinba
Hi,
On 21 December 2012 12:01, Sinbad wrote:
> how can i join pane with the last window
> i've been to as the source window.
Assuming current session:
joinp -s!
-- Thomas Adam
--
LogMeIn Rescue: Anywhe
how can i join pane with the last window
i've been to as the source window.
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Im
las Marriott <
> nicholas.marri...@gmail.com> wrote:
>
>> Vertical is top-bottom split of course, that's obvious, your perception
>> of what is intuitive is wrong.
>>
>>
>> On Fri, Dec 21, 2012 at 10:14:24AM +0530, Sinbad wrote:
>> >ok, :
-bottom split of course, that's obvious, your perception
> of what is intuitive is wrong.
>
>
> On Fri, Dec 21, 2012 at 10:14:24AM +0530, Sinbad wrote:
> >ok, :join-pane -h -t 1 -s 2, did what i was looking for.*
> >i thought -v would give split like*
> >
Vertical is top-bottom split of course, that's obvious, your perception
of what is intuitive is wrong.
On Fri, Dec 21, 2012 at 10:14:24AM +0530, Sinbad wrote:
> ok, :join-pane -h -t 1 -s 2, did what i was looking for.*
>i thought -v would give split like*
>* * * |
ok, :join-pane -h -t 1 -s 2, did what i was looking for.
i thought -v would give split like
|
1 | 2
and -h would split like
1
-
2
but it's other way round, i would say the -v and -h
semantics are counter-intuitive.
On Tue, Dec 18, 2012 at 12:11 PM, Thomas Adam wrote:
Hi,
On 18 December 2012 06:23, Sinbad wrote:
> i tried -v option, it doesn't work. this is how i am using it.
> even with the below command, it always splits horizontally.
>
> :join-pane -v -t 1 -s 2
It does work. What is it what's not working for you, or more likely,
wha
i tried -v option, it doesn't work. this is how i am using it.
even with the below command, it always splits horizontally.
:join-pane -v -t 1 -s 2
On Mon, Dec 17, 2012 at 12:38 PM, Thomas Adam wrote:
> Hi,
>
> On 17 December 2012 06:46, Sinbad wrote:
> > i have two windo
Hi,
On 17 December 2012 06:46, Sinbad wrote:
> i have two windows in a tmux session, 1 and 2;
> now i want to move the two windows to a single
> pane, i am using join-pane -t 1 -s 2, when i
> do this i get the horizontal split with the
> top window containing the window 1 and
i have two windows in a tmux session, 1 and 2;
now i want to move the two windows to a single
pane, i am using join-pane -t 1 -s 2, when i
do this i get the horizontal split with the
top window containing the window 1 and bottom
window containing window 2, but instead of that
i need the window to
On Tue, Dec 11, 2012 at 12:03:40PM +0530, Sinbad wrote:
>how do i vertical split using join-pane command.
What do you mean?
>and also junk chars are shown as pane dividers
>how can i change that. $TERM is set to xterm-256color
>both inside and outside tmux.
This is
how do i vertical split using join-pane command.
and also junk chars are shown as pane dividers
how can i change that. $TERM is set to xterm-256color
both inside and outside tmux. For pane divider i tried
setting export LANG=en_US.UTF-8 as indicated in
other post, it didn't help.
-s
blem which could be a
> > bug. Let me paste the commands to recreate it:
> >
> > # My tmux session starts with one window, named '1:bash'
> > move-window -t 8
> > new-window -d
> > split-window
> > join-pane -d -t 1
> >
> > tmux now
ove-window -t 8
> new-window -d
> split-window
> join-pane -d -t 1
>
> tmux now complains that it can't join a pane to his own window.
> Is that "works as expected"?
I think you're misunderstanding how you reference panes here. You probably
mean to say:
join
Hello everyone.
I recently started to use tmux and I ran into a problem which could be a bug.
Let me paste the commands to recreate it:
# My tmux session starts with one window, named '1:bash'
move-window -t 8
new-window -d
split-window
join-pane -d -t 1
tmux now complains that it ca
Fixed, thanks.
On Fri, Aug 17, 2012 at 12:15:50AM +0200, Michael Scholz wrote:
> > Now that is interesting because this area of tmux hasn't changed in a
> > while. Hmm. Does the following resolve the issue for you?
> >
> > diff --git a/trunk/names.c b/trunk/names.c
> > index 11baae3..44b96ab 10
> Now that is interesting because this area of tmux hasn't changed in a
> while. Hmm. Does the following resolve the issue for you?
>
> diff --git a/trunk/names.c b/trunk/names.c
> index 11baae3..44b96ab 100644
> --- a/trunk/names.c
> +++ b/trunk/names.c
> @@ -55,6 +55,10 @@ window_name_callback(
On Thu, 16 Aug 2012, Nicholas Marriott wrote:
> You're right. This is cos windows can now stick around w/o having any
> panes or winlinks. This is the fix:
Yes, it fixes the crash. Thank you very much for your fast fix!
Mike
-
Hi,
On 16 August 2012 15:06, Michael Scholz wrote:
> After updating tmux-1.7 to revision 2860 join-pane doesn't work any
> longer. One can reproduce it (without any ~/.tmux.conf file) with
>
> % tmux-1.7 new \; neww -d \; joinp -s 1 -t 0
> [lost server]
>
> and tmux-1.
es--;
if (ne->window != NULL)
- ne->window->references--;
+ window_remove_ref(ne->window);
+
TAILQ_REMOVE(¬ify_queue, ne, entry);
free(ne);
}
On Thu, Aug 16, 2012 at 04:06:30PM +0200, Michael Scholz wrote:
> After
After updating tmux-1.7 to revision 2860 join-pane doesn't work any
longer. One can reproduce it (without any ~/.tmux.conf file) with
% tmux-1.7 new \; neww -d \; joinp -s 1 -t 0
[lost server]
and tmux-1.7 dumps core.
% gdb -q tmux-1.7 tmux-1.7.core
Core was generated by `tmux-1.7'
Hi
Looks good thanks, but move-pane will need to go in the man page?
On Sat, Feb 04, 2012 at 12:25:40PM -0800, George Nachman wrote:
> This patch adds a new command, move-pane. It is a wafer-thin wrapper
> around the implementation of join-pane and simply removes the
> restriction th
This patch adds a new command, move-pane. It is a wafer-thin wrapper
around the implementation of join-pane and simply removes the
restriction that source and target must belong to different windows.
In order for move-pane to be complete, join-pane gets a -b argument
that says to place the source
On 2010-12-23T20:07:16, Nicholas Marriott wrote:
> join-pane takes a pane target so it tries the target as a pane index
> first, so in the -t0 case you are asking it to join with pane 0 in the
> current window which is not possible.
>
> The -t1 case works because there is no pane 1
join-pane takes a pane target so it tries the target as a pane index
first, so in the -t0 case you are asking it to join with pane 0 in the
current window which is not possible.
The -t1 case works because there is no pane 1 so it moves on to try
windows.
You need to qualify the target to make it
If I create two windows 0 and 1, and then from window 1 try to
join-pane -t0 I get an error "Can't join to own window". Is this
expected behavior? It works fine if I am in window 0 and do
join-pane -t1.
/Allan
--
Allan Wind
Life Integrity, LLC
<http:/
bind
ctl-b M to break-pane on the extant window and ship all the other panes
except the focus pane into their own windows within the session and then
ctl-b T to gather up all extant windows in a given session and place them
(via join-pane) in the focus window as panes.
On 18 août 2010, at 17:16, Thomas Adam wrote:
> On 18 August 2010 15:15, Florian CROUZAT wrote:
>> What I'd like to have is the ability to bind "join-pane -t origin" to put it
>> back automagically on it's source window.
>
> What's more realist
> "full-screen" (it now has it's own window).
> I do my stuff, then I want to put the pane back in it's original window, and
> I can't have a keyboard bind for that because I have to manually specify the
> window's index using :join-pane -t 2
>
>
on the one I want to read
> "full-screen" (it now has it's own window).
> I do my stuff, then I want to put the pane back in it's original window, and
> I can't have a keyboard bind for that because I have to manually specify the
> window's index using :j
own window).
I do my stuff, then I want to put the pane back in it's original window, and I
can't have a keyboard bind for that because I have to manually specify the
window's index using :join-pane -t 2
What I'd like to have is the ability to bind "join-pane -t origin&
with? ?i rarely want a
> >> window created from brake-pane to be permenant, i'd prefer them
> >> transient.
> >
> > Not really, it doesn't remember that type of history. It would be nice
> > to be able to do it somehow.
>
> is it possible to emula
ember that type of history. It would be nice
> to be able to do it somehow.
is it possible to emulate this though? i see join-pane accepts "-s"
and "-t" - is it not possible to, at the point of calling
"break-pane", store these values for use with "-s"
On Sat, Apr 03, 2010 at 02:19:12PM +0100, David Chanters wrote:
> hi all --
>
> i often use break-pane to work on a window "fullscreen" as it were,
> but i am wondering if the following are possible:
>
> - When i use break-pane can i signify in the status-line that the new
> window created from b
hi all --
i often use break-pane to work on a window "fullscreen" as it were,
but i am wondering if the following are possible:
- When i use break-pane can i signify in the status-line that the new
window created from break-pane is a broken pane?
- Is there a way of getting such a window to rejo
37 matches
Mail list logo
