On 15 July 2012, at 18:35, Kevin Tran wrote:
> I tried applying the patch, but the prompt never returns when I do:
> $ patch ~/Desktop/foo.diff
>
> This is what foo.diff looks like: http://dpaste.com/771005/plain/
First google hit for "how to apply a patch":
http://www.cyberciti.biz/faq/appy-pa
I got an error while applying the patch. This is what I did:
$ svn co https://tmux.svn.sourceforge.net/svnroot/tmux tmux
$ cd tmux/trunk/
$ patch < ~/Desktop/foo.diff
patching file input.c
patching file tmux.h
patch: malformed patch at line 46: void
window_pane_resize(struct wind
You are missing redirection. Either
patch <~/Desktop/foo.diff
Or
cat ~/Desktop/foo.diff|patch
On Sun, Jul 15, 2012 at 10:35:11AM -0700, Kevin Tran wrote:
>I tried applying the patch, but the prompt never returns when I do:
>$ patch ~/Desktop/foo.diff
>This is what foo.diff looks
He should use smcup and rmcup from terminfo.
Does this patch work for you?
On Sat, Jul 14, 2012 at 03:59:54PM -0700, Kevin Tran wrote:
> The author of urwid says that he is using ^[7^[[?47h to switch to the
> alternate screen and ^[[?47l^[8 to switch back.
>
> What are the sequences that tmux
The author of urwid says that he is using ^[7^[[?47h to switch to the alternate
screen and ^[[?47l^[8 to switch back.
What are the sequences that tmux is expecting?
On Jul 11, 2012, at 9:38 AM, Nicholas Marriott wrote:
> You need to save the email (make sure your mailer saves it raw and does
>
You need to save the email (make sure your mailer saves it raw and does
not wrap lines), then checkout tmux SVN and do:
cd tmux/trunk
patch Outside of tmux my TERM is xterm-256color. The author of pudb said he
>thinks the problem is in urwid (a Python console user interface library).
>
What is TERM outside tmux?
This program is using 1047h to switch to alternate screen mode which
unless you are using a very old terminfo is not in the xterm entry, so
it's probably a bad idea to rely on it working.
Anyway please try this which adds it to tmux:
Index: input.c
You need to restart tmux entirely with - so you get the server log too.
On Tue, Jul 10, 2012 at 03:28:11PM -0700, Kevin Tran wrote:
> When I did that it created a file called tmux-client-41746.log with 2 lines:
> 15:27:37:haitran:~ $ cat tmux-client-41746.log
> client got 3
> client got 4
>
When I did that it created a file called tmux-client-41746.log with 2 lines:
15:27:37:haitran:~ $ cat tmux-client-41746.log
client got 3
client got 4
On Jun 24, 2012, at 2:49 AM, Nicholas Marriott wrote:
> Looks like it clears the screen. Kill tmux entirely, run tmux with
> -, then reproduce
Looks like it clears the screen. Kill tmux entirely, run tmux with
-, then reproduce the problem and send me the logs from the current
directory please.
On Sat, Jun 23, 2012 at 07:11:10PM -0700, Kevin Tran wrote:
> typescript follows:
>
> Script started on Sat Jun 23 19:09:49 2012
> ]7;fil
typescript follows:
Script started on Sat Jun 23 19:09:49 2012
]7;file://ktmacbookpro/Users/haitran]7;file://ktmacbookpro/Users/haitran]7;file://ktmacbookpro/Users/haitran]7;file://ktmacbookpro/Users/haitran]7;file://ktmacbookpro/Users/haitran[0;32m19:09:50:haitran:~
$ [0mpython pudb
Ok, run the program in script inside tmux and send me the typescript
file please.
On Fri, Jun 22, 2012 at 06:05:01PM -0700, Kevin Tran wrote:
> 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 probabl
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
>>
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
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
>
>
> 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
-
16 matches
Mail list logo
