Hi:
It seems like I saw this reported already but can't find it now.
I'm thinking I'm doing something stupid, but can't figure it out
and was wondering if someone on this list can see the problem.
My usual procedure for creating a patch is as follows:
1. Take a file I want to edit, say linear_code.py in sage/coding,
copy it to a directory sagestuff, say.
2. Create a clone, say codes1.
3. Edit the file, modifying/adding the functions I want.
4. Copy the file sagestuff/linear_code.py to
sage/coding/linear_code.py, over-writing the existing file.
5. Rebuild the clone sage -br
6. Test the file sage -t sagestuff/linear_code.py
7. If there are errors, go to step 3. Other wise,
create a patch using hg_sage.commit() and
hg_sage.bundle('mybundle')
This process is no longer working for me. Now, it seems I have
to type sage -sh before step 6. Then I have to type
export EDITOR=vi (export EDITOR=emacs seems not to work)
before step 7.
Does this make sense? Is the behavior of SAGE different or am I
doing something stupid?
- David
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@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-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
