On Sep 21, 2011, at 8:53 PM, John H Palmieri wrote:
> On Wednesday, September 21, 2011 11:26:39 AM UTC-7, Felix Salfelder wrote:
> On Wed, Sep 21, 2011 at 09:11:57AM -0700, Tom Boothby wrote:
> > I capitulate on the hidden file idea, in favor of putting 'em in
> > ~/.sage/ though one might note that we're exchanging one hidden file
> > for another ;)
> i agree. prefixing a dot is not quite a solution as i thought yesterday.
>
> putting them in ~/.sage would require some pathname mangling or hashing,
> that wouln't make it easier to list/find them than a prefixed filename
> (be it with a dot or not).
>
> if I got it right, caching the preparser output is for debugging or for
> performance (correct me if im wrong). if it is for debugging, it would
> be perfectly safe to hide it from the user, if it is for performance, it
> would make more sense to put it into /tmp or /dev/shm.
>
> Another idea would be to not cache it at all: don't save any file, but save
> the preparsed file as a string and feed that in to sage-python. ("sage
> -preparse" would still wrute to a file.)
Doesn't that give less useful backtraces? I can also be instructive to look at
the preparsed file to see what actually changes.
My vote is for saving the preparsed file right beside sage file with a name
like bob.preparsed.py. It then becomes easy to filter out the file in emacs
when opening a file, but it's still there if I really do want it. I presume
there are similar capabilities in vim and other editors. Unfortunately, I
don't know of a way to make bash ignore certain file extensions when
completing. Putting them in ~/.sage might be okay, but I think it would make
things more mysterious to new users.
-Ivan
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
