It looks like ipython is printing invalid (or at least unknown to Emacs)
I got it to ignore them by setting
(setq ansi-color-drop-regexp
"
\\[\\([ABCDsuK]\\|[12][JK]\\|=[0-9]+[hI]\\|[0-9;]*[HfDnC]\\|\\?[0-9]+[hl]\\|J\\)")
There is also a bug in my version of Emacs which causes these elim
I would really like to have %attach back working.
Best,
Travis
On Friday, August 12, 2016 at 12:50:23 PM UTC-5, Volker Braun wrote:
>
> Presumably attach (or, more generally, using the python inputhook) doesn't
> work since Ipython 5 now implements its own input handling.
>
>
>
>
> On Friday, A
leif wrote:
> Bill Page wrote:
>> BTW, is it normal to run 'make' after 'git trac checkout'?
>
> Sure you should, to make the changes take effect in your Sage
> installation. (But that's not always necessary, really depends on what
> you pull. In any case, running 'make' is safe, as when nothing
Bill Page wrote:
> BTW, is it normal to run 'make' after 'git trac checkout'?
Sure you should, to make the changes take effect in your Sage
installation. (But that's not always necessary, really depends on what
you pull. In any case, running 'make' is safe, as when nothing has to
get rebuilt / u
BTW, is it normal to run 'make' after 'git trac checkout'? I just did
that and 'make' seems to be re-building almost everything.
On 13 August 2016 at 17:07, Bill Page wrote:
> Yes indeed it does! Much appreciated.
>
> On 13 August 2016 at 17:05, Volker Braun wrote:
>> I removed the leading slash
Yes indeed it does! Much appreciated.
On 13 August 2016 at 17:05, Volker Braun wrote:
> I removed the leading slash from the branch name on that ticket, works now.
>
> On Saturday, August 13, 2016 at 10:22:55 PM UTC+2, Bill Page wrote:
>>
>> OK, I thought that might be it (although all I really w
I removed the leading slash from the branch name on that ticket, works now.
On Saturday, August 13, 2016 at 10:22:55 PM UTC+2, Bill Page wrote:
>
> OK, I thought that might be it (although all I really wanted was
> read-only access), so I ran 'git trac config', see below. But it still
> fails.
OK, I thought that might be it (although all I really wanted was
read-only access), so I ran 'git trac config', see below. But it still
fails.
I guess it's just not my day ...
On 13 August 2016 at 16:13, Volker Braun wrote:
> You missed "git trac config"
>
wspage@sarah ~/sage $ git trac config
You missed "git trac config"
On Saturday, August 13, 2016 at 8:50:35 PM UTC+2, Bill Page wrote:
>
> :( :{ :[
>
> wspage@sarah ~ $ git clone
> https://github.com/sagemath/git-trac-command.git
> Cloning into 'git-trac-command'...
> remote: Counting objects: 776, done.
> remote: Total 776 (delta
:( :{ :[
wspage@sarah ~ $ git clone https://github.com/sagemath/git-trac-command.git
Cloning into 'git-trac-command'...
remote: Counting objects: 776, done.
remote: Total 776 (delta 0), reused 0 (delta 0), pack-reused 776
Receiving objects: 100% (776/776), 380.53 KiB | 174.00 KiB/s, done.
Resolvin
Volker Braun wrote:
> http://combinat.sagemath.org/doc/developer/git_trac.html
[Hello Google,]
Canonical URLs: ;-)
*
http://doc.sagemath.org/html/en/developer/git_trac.html#installing-the-git-trac-command
*
http://doc.sagemath.org/html/en/developer/git_trac.html#check-out-an-existing-ticket
leif wrote:
> Bill Page wrote:
>> It seems like I am always confused when I try to use sagetrac, but I
>> did not expect this:
>>
>> wspage@sarah ~/sage $ ./sage --dev checkout --ticket=21231
>> sage-run received unknown option: --dev
>> usage: sage [options]
>> Try 'sage -h' for more information.
http://combinat.sagemath.org/doc/developer/git_trac.html
In particular check out the sections on "Installing the Git-Trac Command"
and then "Check out an Existing Ticket"
On Saturday, August 13, 2016 at 6:55:10 PM UTC+2, Bill Page wrote:
>
> Sorry, I'm still confused. What exactly do I have to
Sorry, I'm still confused. What exactly do I have to do to checkout a trac
ticket for testing and where is it documented? Google searches only seem to
mention --dev.
On Aug 13, 2016 12:19 PM, "leif" wrote:
Bill Page wrote:
> It seems like I am always confused when I try to use sagetrac, but I
>
Bill Page wrote:
> It seems like I am always confused when I try to use sagetrac, but I
> did not expect this:
>
> wspage@sarah ~/sage $ ./sage --dev checkout --ticket=21231
> sage-run received unknown option: --dev
> usage: sage [options]
> Try 'sage -h' for more information.
The "devscripts" ha
It seems like I am always confused when I try to use sagetrac, but I
did not expect this:
wspage@sarah ~/sage $ ./sage --dev checkout --ticket=21231
sage-run received unknown option: --dev
usage: sage [options]
Try 'sage -h' for more information.
--
What am I doing wrong?
I just did
wspage@sar
Joseph Hundley wrote:
> Quick update: removing the backslash seems to fix the problem with
> all.py. It was probably a stray character introduced when I went in to
> do some other minor fixes.
Yes. I didn't say explicitly, but I of course meant "remove it if it's
also in the corresponding file be
17 matches
Mail list logo
