Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange output artifacts in footer of notebook #2005

Closed
fonnesbeck opened this issue Jun 22, 2012 · 8 comments · Fixed by #2012
Closed

Strange output artifacts in footer of notebook #2005

fonnesbeck opened this issue Jun 22, 2012 · 8 comments · Fixed by #2012

Comments

@fonnesbeck
Copy link

Occasionally, I will notice an odd footer appear at the bottom of an iPython notebook with what appears to be a series of x's:

http://cl.ly/1E1V0P03342v341j0w12

Any idea what this is? It has happened in a couple of very different notebook projects. Running 0.13.dev on Python 2.7.1 (OS X 10.7.4).

@Carreau
Copy link
Member

Carreau commented Jun 22, 2012

Related to the comment i posted on #1883 i think. Used to test the font height to get around a bug.

@ellisonbg
Copy link
Member

Hmm, that is the pager area, and it looks like there is a payload of
some sort showing up. This area is written to when you do things like
"foo?".

On Fri, Jun 22, 2012 at 7:53 AM, Chris Fonnesbeck
reply@reply.github.com
wrote:

Occasionally, I will notice an odd footer appear at the bottom of an iPython notebook with what appears to be a series of x's:

http://cl.ly/1E1V0P03342v341j0w12

Any idea what this is? It has happened in a couple of very different notebook projects. Running 0.13.dev on Python 2.7.1 (OS X 10.7.4).


Reply to this email directly or view it on GitHub:
#2005

Brian E. Granger
Cal Poly State University, San Luis Obispo
bgranger@calpoly.edu and ellisonbg@gmail.com

@fonnesbeck
Copy link
Author

No, just any error does not generate it. The problem is that its so subtle that I don't notice it right away, so I have not been able to pinpoint when it happens. However, running all the cells of a working notebook does not trigger it, so it appears to be related to an exception somehow. I will try keeping a closer eye on it.

@fperez
Copy link
Member

fperez commented Jun 22, 2012

@mcelrath, it looks like that Courier New bug is going to haunt us forever... I haven't seen this problem yet, but we should do something about it before the release. Argh...

@mcelrath
Copy link

Nah it's a minor problem, please pull #2012 to fix it.

@fperez
Copy link
Member

fperez commented Jun 23, 2012

Great, thanks! Will have a look now...

@fperez fperez closed this as completed in 086258d Jun 23, 2012
@fperez
Copy link
Member

fperez commented Jun 23, 2012

@fonnesbeck, please let us know if the merge of #2012 fixes everything. I reviewed it and the code looked clean, but since the problem doesn't seem to be easy to trigger, I prefer to merge now so we have more testing in the wild.

@fonnesbeck
Copy link
Author

I've just pulled the fix, so I will let you know if I see it again. Thanks for the fast action.

mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014
Fix spurious appearance of the #fontarea when fonts don't have any problem; also remove loud dialog when problematic font is detected and simply adjust baseline.  Users will have a slightly offset baseline for bold/italic highlights, but without any functional problems.

Fixes ipython#2005.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants