Nicolas Pernetty | 1 Feb 23:46
Picon
Favicon

Re: IPython in XEmacs now working on Windows

On Sun, 28 Jan 2007 10:29:27 -0700, "Fernando Perez"
<fperez.net <at> gmail.com> wrote :

> > > > Ok I just want to add a command line option to IPython to
> > > > inhibit readline related commands (like the \001 and \002 in
> > > > colorANSI.py). As soon as one of the win32 gurus agrees for
> > > > that, I'll work on it.
> > >
> > > Great.  Ville, Jorgen?  I don't want to emit judgment on a patch
> > > which I won't even be testing myself, since I don't run the
> > > platform.  I'll leave this one up to you guys.
> >
> > Too bad I can't comment on win32 stuff at the moment either; I'm
> > still away from home (in Sweden) on a Linux-only laptop. I have one
> > month to go, so someone else should review this stuff...
> 
> Oops, sorry.  You'd mentioned this a few weeks ago but I'd forgotten.
> 
> Nicolas: send the patch in, and we'll have a look at it regardless (we
> can still read it and evaluate it as pure code).  Hopefully someone
> else can help with testing it. If push comes to shove I'll set things
> up under VMWare for a test myself (I can do it, it just takes me much
> more time than for a regular win32 user since I don't have anything
> set up in everyday use).

Hello,

As promised here is the patch.
I basically did 3 things :
1) Inhibit \001 and \002 in case we are on w32 AND emacs
(Continue reading)

Pete Forman | 2 Feb 16:22

Re: IPython in XEmacs now working on Windows

I've applied that patch by hand and pylab seems to work okay.  Thanks.

XP Pro SP2
XEmacs native 21.5.17
python-mode.el 4.79
ipython.el 1851
Python 2.5
IPython 0.7.3 + patch
wxPython Unicode 2.6.3.3

~/.matplotlib/matplotlibrc has one changed line

backend      : WxAgg

These emacs variables set using customize

py-python-command-args
("-pylab" "-colors" "LightBG")
ipython-command
"d:/Program Files/Python25/Scripts/ipython.bat"

After starting XEmacs, enter this in *scratch*

(require `ipython)

There are a few niggles.

1) I failed putting (require `ipython) in ~/.xemacs/init.el (formerly
~/.emacs).  There was an error about py-shell-map being undefined.
Perhaps using an autoload might make things smoother.
(Continue reading)

Pete Forman | 2 Feb 16:37

Re: IPython in XEmacs now working on Windows

A couple more version numbers that I missed off my list:

SciPy 0.5.2
NumPy 1.0.2
matplotlib 0.87.7
--

-- 
Pete Forman                -./\.-  Disclaimer: This post is originated
WesternGeco                  -./\.-   by myself and does not represent
pete.forman <at> westerngeco.com    -./\.-   the opinion of Schlumberger or
http://petef.port5.com           -./\.-   WesternGeco.
Pete Forman | 2 Feb 17:06

Re: IPython in XEmacs now working on Windows

Pete Forman <pete.forman <at> westerngeco.com> writes:

 > A couple more version numbers that I missed off my list:

 > NumPy 1.0.2

Actually NumPy 1.0.1

Time to go home.  At least the subject is correct now.
--

-- 
Pete Forman                -./\.-  Disclaimer: This post is originated
WesternGeco                  -./\.-   by myself and does not represent
pete.forman <at> westerngeco.com    -./\.-   the opinion of Schlumberger or
http://petef.port5.com           -./\.-   WesternGeco.
Nicolas Pernetty | 6 Feb 02:57
Picon
Favicon

Re: IPython in XEmacs now working on Windows

On Fri, 02 Feb 2007 15:22:23 +0000, Pete Forman
<pete.forman <at> westerngeco.com> wrote :

> I've applied that patch by hand and pylab seems to work okay.  Thanks.
> 
> XP Pro SP2
> XEmacs native 21.5.17
> python-mode.el 4.79
> ipython.el 1851
> Python 2.5
> IPython 0.7.3 + patch
> wxPython Unicode 2.6.3.3
> 
> 
> ~/.matplotlib/matplotlibrc has one changed line
> 
> backend      : WxAgg
> 
> 
> These emacs variables set using customize
> 
> py-python-command-args
> ("-pylab" "-colors" "LightBG")
> ipython-command
> "d:/Program Files/Python25/Scripts/ipython.bat"

I don't have to customize this particular variable : if you put your
directory in your PATH environment var, ipytohn.el/python-mode.el will
find your ipython by themselves !

(Continue reading)

Pete Forman | 6 Feb 18:56

Re: IPython in XEmacs now working on Windows

Nicolas Pernetty <nicopernetty <at> yahoo.fr> writes:

 > On Fri, 02 Feb 2007 15:22:23 +0000, Pete Forman
 > <pete.forman <at> westerngeco.com> wrote :
>
>> [snip]
>> 
>> These emacs variables set using customize
>> 
>> py-python-command-args
>> ("-pylab" "-colors" "LightBG")
>> ipython-command
>> "d:/Program Files/Python25/Scripts/ipython.bat"
>
 > I don't have to customize this particular variable : if you put
 > your directory in your PATH environment var,
 > ipytohn.el/python-mode.el will find your ipython by themselves !

I don't like having too many entries in PATH.  ipython is the only
script that I use from that directory.

>> After starting XEmacs, enter this in *scratch*
>> 
>> (require `ipython)
>> 
>> 
>> 
>> There are a few niggles.
>> 
>> 1) I failed putting (require `ipython) in ~/.xemacs/init.el (formerly
(Continue reading)

Lev Givon | 7 Feb 19:50
Favicon

ipython terminal weirdness

I have noticed that ipython occasionally appears to derange the
terminal in which it was started insofar that its output no longer
contains any newlines. Resetting the terminal (via !reset) temporarily
clears the problem. 

Is this behavior indicative of some terminal setting misinteraction,
or does it seem like a bug in ipython? I am running ipython 0.7.3 on
Linux; my TERM is set to xterm. I have observed the above behavior in
earlier versions of ipython.

						    L.G.
Fernando Perez | 7 Feb 19:57
Picon
Gravatar

Re: ipython terminal weirdness

On 2/7/07, Lev Givon <lev <at> columbia.edu> wrote:
> I have noticed that ipython occasionally appears to derange the
> terminal in which it was started insofar that its output no longer
> contains any newlines. Resetting the terminal (via !reset) temporarily
> clears the problem.
>
> Is this behavior indicative of some terminal setting misinteraction,
> or does it seem like a bug in ipython? I am running ipython 0.7.3 on
> Linux; my TERM is set to xterm. I have observed the above behavior in
> earlier versions of ipython.

I've also seen it on occasion, and I really wish I knew what the hell
causes it so I could fix it for good, as it drives me nuts.  But I
don't have the foggiest clue as to what actually triggers the problem:
it seems pretty random and isn't frequent enough that I've been able
figure out what's going on.

So if anyone has ideas, I'm all ears...

Cheers,

f
Lev Givon | 7 Feb 20:17
Favicon

Re: ipython terminal weirdness

Received from Fernando Perez on Wed, Feb 07, 2007 at 01:57:21PM EST:
> On 2/7/07, Lev Givon <lev <at> columbia.edu> wrote:
> >I have noticed that ipython occasionally appears to derange the
> >terminal in which it was started insofar that its output no longer
> >contains any newlines. Resetting the terminal (via !reset) temporarily
> >clears the problem.
> >
> >Is this behavior indicative of some terminal setting misinteraction,
> >or does it seem like a bug in ipython? I am running ipython 0.7.3 on
> >Linux; my TERM is set to xterm. I have observed the above behavior in
> >earlier versions of ipython.
> 
> I've also seen it on occasion, and I really wish I knew what the hell
> causes it so I could fix it for good, as it drives me nuts.  But I
> don't have the foggiest clue as to what actually triggers the problem:
> it seems pretty random and isn't frequent enough that I've been able
> figure out what's going on.
> 
> So if anyone has ideas, I'm all ears...
> 
> Cheers,
> 
> f

Perhaps ipython is emitting some escape sequence in order to colorize
output that actually redefines (i.e., blanks) the terminal's
representation of the linefeed character?

							L.G.
(Continue reading)

Fernando Perez | 7 Feb 20:19
Picon
Gravatar

Re: ipython terminal weirdness

On 2/7/07, Lev Givon <lev <at> columbia.edu> wrote:

> Perhaps ipython is emitting some escape sequence in order to colorize
> output that actually redefines (i.e., blanks) the terminal's
> representation of the linefeed character?

The color escapes are regular ANSI escapes, and I've had very
long-running sessions with plenty of colored output where this does
NOT happen.

I suspect the culprit is an interaction with the system pager ('less'
in my case).  I have a hunch that I've seen this problem only after
having used less to page long sections of info.  But it doesn't happen
always, so I just don't know.

Cheers,

f

Gmane