On Sat, Oct 11, 2008 at 9:58 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Oct 11, 6:54 am, Matthias Meulien <[EMAIL PROTECTED]> wrote:
>> Hi,
>
> Hi Matthias,
>
>> I successfully compiled Sage 3.1.2 from source. But I had troubles
>> with many commands... I finaly realized that all functions using a GAP
>> subprocess where buggy, which was related to a corrupted prompt; see:
>>
>> sage: gap._eval_line('1+3;')
>> '4\n\x1b[1m\x1b[34mgap> \x1b[0m'
>>
>> Removing $HOME/.gaprc (in my case it turn color prompt on, using the
>> command "ColorPrompt(true);") doesn't help... To fix the problem I had
>> to remove $HOME/.gaprc AND compile the GAP component again. Now it
>> works well, even with $HOME/.gaprc back.
>>
>> May be one should change the compilation process so that it ignore
>> $HOME/.gaprc during build time?
>
> Hmm, it sounds like we should ignore the global .gaprc and use one in
> $SAGE_DOT instead. I am no GAP expert, so if anyone knows how to
> accomplish this please let us know so we can open a ticket to fix
> this.According to the reference manual http://www.gap-system.org/Manuals/doc/htm/ref/CHAP003.htm#SECT004 GAP will look for .gaprc in the home directory. I don't know how to change this (or if it can be changed) but Steve Linton does. I also don't quite understand the original poster's issue. Did he try to create a color prompt using a modified .gaprc? If so, I think that can be tricky. > > Cheers, > > Michael > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
