Hi,
I'd like to build tmux from CVS, but I don't know how: there aren't
any shell scripts, configure scripts, or configure input scripts in
the repo and my attempts to use the Makefile fail:
$ make -verison
GNU Make 3.81
$ make
Makefile:50: *** missing separator. Stop.
Am I missing some
You need to use SVN.
On Fri, Jun 22, 2012 at 01:08:59PM -0700, Jonathan Daugherty wrote:
> Hi,
>
> I'd like to build tmux from CVS, but I don't know how: there aren't
> any shell scripts, configure scripts, or configure input scripts in
> the repo and my attempts to use the Makefile fail:
>
>
I am running:
python 2.7.1
pudb==2012.1
urwid==1.0.1
pigments==1.5
tmux==1.6
When I use pudb in a tmux session, the python shell shows at the bottom when it
should clear the screen.
Screenshots
Outside of a tmux session: http://imgur.com/uZHpG
Inside a tmux session: http://imgur.com/tjirf
What
>
>
> What's happening? Is this a problem with tmux or with pudb? How do you fix
> this?
>
>
If you change (and export) the value of $TERM from within the tmux session
to the same value it has when you run out of tmux, does it behave the same
way?
--
Fabio
-
> You need to use SVN.
I don't know if any of this is expected behavior, but it doesn't work
for me. When I run 'autogen.sh', I get the following result:
configure.ac:18: installing `etc/compile'
configure.ac:9: installing `etc/config.sub'
configure.ac:7: installing `etc/missing'
configu
Use git instead? https://github.com/ThomasAdam/tmux.git
Rob
--
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 resp
Try autoconf 2.65 or later, and you need pkg-config installed.
On Fri, Jun 22, 2012 at 03:38:34PM -0700, Jonathan Daugherty wrote:
> > You need to use SVN.
>
> I don't know if any of this is expected behavior, but it doesn't work
> for me. When I run 'autogen.sh', I get the following result:
>
Your TERM is probably wrong, it needs to be "screen" inside tmux.
On Fri, Jun 22, 2012 at 02:59:42PM -0700, Kevin Tran wrote:
>I am running:
>python 2.7.1
>pudb==2012.1
>urwid==1.0.1
>pigments==1.5
>tmux==1.6
>When I use pudb in a tmux session, the python shell shows a
Inside tmux $TERM is screen-256color.
Outside tmux $TERM is xterm-256color.
It behaved the same way with $TERM from within a tmux session set to
xterm-256color.
On Jun 22, 2012, at 3:34 PM, Fabio Spelta wrote:
>
> What's happening? Is this a problem with tmux or with pudb? How do you fix
> th
I think my $TERM is correct. Inside tmux $TERM is screen-256color.
On Jun 22, 2012, at 3:46 PM, Nicholas Marriott wrote:
> Your TERM is probably wrong, it needs to be "screen" inside tmux.
>
>
> On Fri, Jun 22, 2012 at 02:59:42PM -0700, Kevin Tran wrote:
>> I am running:
>> python 2.7.1
>>
10 matches
Mail list logo
