<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<body text="#000000" bgcolor="#ffffff">
Any approach that involves storing data in a separate file<br>
runs into problems when someone tries to move the file,<br>
rename the file, mail the file, back up the file, compress<br>
the file, put the file into an archive file, and so on.<br>
Glen Foy wrote:
<blockquote type="cite" cite="mid:71F0A1DE-C8A9-4BA9-8DAF-686E60BD9B4C@clairvaux.org">
<pre wrap="">On Jun 20, 2009, at 12:44 PM, Gail Zacharias wrote:
<pre wrap="">Yeah, here's the thing... The API can easily provide any number of
functions such as save/load-buffer-as-html or save/load-buffer-as-
rtf or save/load-buffer-in-home-baked-format-with-font-info-encoded-
in-lisp-comments or whatever, stuff like that would be trivial to
write. The problem is that it's not clear to me what Hemlock should
actually do to save the attributes, given the reality of living in a
unix file system. Any thoughts?
If we are just talking about Hemlock as a source code editor, it may
not be necessary or even desirable to distribute styled files.
Everyone has their own idea of what source code should look like anyway.
From that point of view, the styling information could be stored in
an associated invisible file and distributed or not distributed as the
author saw fit. When hacking, Hemlock would look for the associated
file, using it if it was there. This would be a simple solution.
People may, however, want to use Hemlock for other purposes. In which
case the two file approach is not so good.
This issue clearly needs some brainstorming.
Openmcl-devel mailing list
<a href="mailto:Openmclemail@example.com" class="moz-txt-link-abbreviated">Openmclfirstname.lastname@example.org</a>
<a href="http://clozure.com/mailman/listinfo/openmcl-devel" class="moz-txt-link-freetext">http://clozure.com/mailman/listinfo/openmcl-devel</a>