Very impressive, Nathan. > So, here's some types of advice I'd love to receive on this: > > 1. Should I actually be suggesting changes to sagetex.sty? Or is there a > way to do that in my own .sty file? I couldn't call Dan's ST@stuff > commands from my own document, because I think TeX @ things are local or > something...*mumbles cluelessly* > > 2. Not sure if I can run sagesilent blocks when not inside a document, > which I'd need to do to move the class definition into a .sty file. Or > should I use something like \AtBeginDocument? Not sure if that will work > either. TeX is so touchy, and I'm rather new at this. > > 3. The goal is, of course, to get this nicely packaged into a single .sty > file that includes sagetex.sty, and then add the features mentioned above, > and then contribute it...someplace. When the time comes, what's the > appropriate "someplace"? > >> >>>
Maybe a pull request at https://bitbucket.org/ddrake/sagetex/ ? I think you and Dan should talk a little about whether a new .sty file or adding a new block type is better - and what the name of the block should be, etc. -- You received this message because you are subscribed to the Google Groups "sage-edu" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-edu+unsubscr...@googlegroups.com. To post to this group, send email to sage-edu@googlegroups.com. Visit this group at http://groups.google.com/group/sage-edu?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
