Has been fixed in #16389 (6.3.beta2)

On Tuesday, August 5, 2014 3:43:58 PM UTC+1, Johan S. R. Nielsen wrote:
>
> Hmm, it seems that the ipython_extension.py should be patched to know 
> about typeset. Directly setting the flag in IPython seems to do the trick:
> get_ipython().display_formatter.formatters['text/plain'].set_display(
> "typeset")
>
> Regards,
> Johan
>
> On Tuesday, May 20, 2014 7:07:35 AM UTC+2, Ivan Andrus wrote:
>>
>> Any help?  What should I be using in place of `%display typeset`, which 
>> no longer works?
>>
>> -Ivan
>>
>> On May 14, 2014, at 11:52 PM, Emmanuel Charpentier <
>> emanuel.c...@gmail.com> wrote:
>>
>> In 6.2, %display seems restricted to ('simple', 'ascii_art'). From a 
>> terminal :
>>
>> sage: %display typeset
>>
>> ---------------------------------------------------------------------------
>> ValueError                                Traceback (most recent call 
>> last)
>> <ipython-input-2-65343e720bd4> in <module>()
>> ----> 1 get_ipython().magic(u'display typeset')
>>
>> /usr/local/sage-6.2/local/lib/python2.7/site-packages/IPython/core/interactiveshell.pyc
>>  
>> in magic(self, arg_s)
>>    2163         magic_name, _, magic_arg_s = arg_s.partition(' ')
>>    2164         magic_name = magic_name.lstrip(prefilter.ESC_MAGIC)
>> -> 2165         return self.run_line_magic(magic_name, magic_arg_s)
>>    2166 
>>    2167     
>> #-------------------------------------------------------------------------
>>
>> /usr/local/sage-6.2/local/lib/python2.7/site-packages/IPython/core/interactiveshell.pyc
>>  
>> in run_line_magic(self, magic_name, line)
>>    2084                 kwargs['local_ns'] = 
>> sys._getframe(stack_depth).f_locals
>>    2085             with self.builtin_trap:
>> -> 2086                 result = fn(*args,**kwargs)
>>    2087             return result
>>    2088 
>>
>> /usr/local/sage-6.2/local/lib/python2.7/site-packages/sage/repl/ipython_extension.pyc
>>  
>> in display(self, args)
>>
>> /usr/local/sage-6.2/local/lib/python2.7/site-packages/IPython/core/magic.pyc 
>> in <lambda>(f, *a, **k)
>>     189     # but it's overkill for just that one bit of state.
>>     190     def magic_deco(arg):
>> --> 191         call = lambda f, *a, **k: f(*a, **k)
>>     192 
>>     193         if callable(arg):
>>
>> /usr/local/sage-6.2/local/lib/python2.7/site-packages/sage/repl/ipython_extension.pyc
>>  
>> in display(self, args)
>>     252             mode = args[0]
>>     253             if mode not in ('simple', 'ascii_art'):
>> --> 254                 raise ValueError('unrecognized display type 
>> "%s"'%mode)
>>     255             self._magic_display_status = mode
>>     256 
>>
>> ValueError: unrecognized display type "typeset"
>>
>> In other words, the ability may exist but is unreachable...
>>
>> HTH,
>>
>> --
>> Emmanuel Charpentier
>>
>> Le mercredi 14 mai 2014 04:22:36 UTC+2, Ivan Andrus a écrit :
>>>
>>> It looks like `%display typeset` no longer works (if it ever did).  I’m 
>>> fairly sure that I had tested it before (when working on #15271 where 
>>> Volker suggested using it), but maybe not.  So, at the end of the day, I’m 
>>> not sure how to turn on typesetting in Sage 6.2.
>>>
>>> -Ivan
>>>
>>> On May 13, 2014, at 12:46 AM, Emmanuel Charpentier <emanuel.c...@
>>> gmail.com> wrote:
>>>
>>> Dear list,
>>>
>>> I just installed sage 6.2 from source on Deblan testing/amd64 ; I also 
>>> installed sage_mode.
>>>
>>>  plot(sin(x), [x, -2*pi, 2*pi], figsize=4)
>>>
>>> gives me the expected plot. but
>>>  diff(sin(x),x)
>>> gives me
>>> cos(x)
>>> typed, not typeset.
>>>
>>> Ouch !
>>>
>>> For light work, where my sage's use is incidental, I'm used to work in 
>>> emacs with sage mode, copying interesting results as latex (via 
>>> right-click==>copy as latex) and pasting them in latex/noweb files. This 
>>> swell work environment just disappeared.
>>>
>>> Has anyone already seen this problem ? Has anyone successfully used 
>>> emacs_mode in Sage 6.2 ?
>>>
>>> Sincerely yours,
>>>
>>> --
>>> Emmanuel Charpentier
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "sage-support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to sage-support...@googlegroups.com.
>>> To post to this group, send email to sage-s...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/sage-support.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-support...@googlegroups.com.
>> To post to this group, send email to sage-s...@googlegroups.com.
>> Visit this group at http://groups.google.com/group/sage-support.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to