Chris's Wiki :: blog/unix/FvwmStatesUnderstood Commentshttps://utcc.utoronto.ca/~cks/space/blog/unix/FvwmStatesUnderstood?atomcommentsDWiki2012-03-26T14:22:49ZRecent comments in Chris's Wiki :: blog/unix/FvwmStatesUnderstood.By Chris Siebenmann on /blog/unix/FvwmStatesUnderstoodtag:CSpace:blog/unix/FvwmStatesUnderstood:949c5cf42cedc652f9d464aa591e1b947afceb8bChris Siebenmann<div class="wikitext"><p>I decided to move my reply to an actual entry,
<a href="https://utcc.utoronto.ca/~cks/space/blog/web/AtomConstrainedEnvironments">AtomConstrainedEnvironments</a>. The short version is that <a href="https://utcc.utoronto.ca/~cks/space/dwiki/DWiki">DWiki</a>
doesn't assume write permissions to the content it serves (and often
doesn't have it).</p>
</div>2012-03-26T14:22:49ZFrom 78.35.25.18 on /blog/unix/FvwmStatesUnderstoodtag:CSpace:blog/unix/FvwmStatesUnderstood:2edae88805fe44a6a4f9e9228dbe80ae47cce7b1From 78.35.25.18<div class="wikitext"><p>But isn’t it feasible to append a header (well, footer) line to an article file containing an ID, the first time the file is found not to have one? The user would have to refrain from editing it, but asking them to does not seem a problem to me.</p>
<p>Though, do you want to avoid opening files <em>also</em>? Then the problem in fact seems inescapable…</p>
<p>In that case you could set a xattr I guess… but that too will only work if the environment is <em>just so</em>.</p>
<p>Hrm.</p>
<p>—<a href="http://plasmasturm.org/">Aristotle Pagaltzis</a></p>
</div>2012-03-22T20:34:20ZBy Chris Siebenmann on /blog/unix/FvwmStatesUnderstoodtag:CSpace:blog/unix/FvwmStatesUnderstood:69afa69a6e1f4692a1b6b0176c45077e8e7b4245Chris Siebenmann<div class="wikitext"><p>I am not so much doing Atom wrong as doing Atom in a bad environment.
<a href="https://utcc.utoronto.ca/~cks/space/blog/web/EntryAsFileProblems">Metadata is one of the deep problems for file-based content engines</a>; you don't necessarily have metadata about
entries like original publication date or a unique, stable identifier
for them. <a href="https://utcc.utoronto.ca/~cks/space/dwiki/DWiki">DWiki</a> is especially badly off essentially because it is
supposed to be a presentation layer over the filesystem.</p>
<p>(If you take a pure, metadata-less view of the filesystem you have no
other identifier for objects other than their filenames.)</p>
</div>2012-03-22T04:25:47ZFrom 78.35.25.18 on /blog/unix/FvwmStatesUnderstoodtag:CSpace:blog/unix/FvwmStatesUnderstood:0f3c91d30a75c3d0907a6866d5ba2ef111772c94From 78.35.25.18<div class="wikitext"><p>And now the feed entries have re-appeared, which reveals that you’re also doing Atom wrong. <code>:-)</code> (The <code>atom:id</code> should be minted once and stay constant forever, no matter what else about the entry changes. That URIs sometimes change was precisely the (primary) rationale behind having a separate ID instead of just using the permalink for the purpose.)</p>
<p>–<a href="http://plasmasturm.org/">Aristotle Pagaltzis</a></p>
</div>2012-03-22T03:23:30ZBy Chris Siebenmann on /blog/unix/FvwmStatesUnderstoodtag:CSpace:blog/unix/FvwmStatesUnderstood:aab12cda3a39261d8463888bd712419cdf25a17eChris Siebenmann<div class="wikitext"><p>The most embarrassing typos are article slug typos. Now fixed, which is a
total pain in the rear in this file-based wiki engine.</p>
<p>(I've had it happen before, but fortunately only a few times.)</p>
</div>2012-03-22T01:59:05ZFrom 78.35.25.18 on /blog/unix/FvwmStatesUnderstoodtag:CSpace:blog/unix/FvwmStatesUnderstood:0a01b7cd0ae2b51b68386560509675f6962fb3fcFrom 78.35.25.18<div class="wikitext"><p>“Undertood”? <code>:-)</code></p>
<p>—<a href="http://plasmasturm.org/">Aristotle Pagaltzis</a></p>
</div>2012-03-22T01:12:08ZBy Chris Siebenmann on /blog/unix/FvwmStatesUnderstoodtag:CSpace:blog/unix/FvwmStatesUnderstood:291903deca8df40c09d1a00c7576bf15412cb39aChris Siebenmann<div class="wikitext"><p>There's probably scope for improvement, but I think my misunderstanding
wasn't because of any bad writing in the manpage; it was because I had
never read the (current) manpage thoroughly. Partly this is because
I've been using FVWM long enough that I've read previous versions of
the manpage, and it's hard to sit down with something that is, oh, 70%
familiar and read it carefully to understand the new 30% (or even spot
the new 30%).</p>
</div>2012-03-21T16:30:44ZFrom 82.69.211.1 on /blog/unix/FvwmStatesUnderstoodtag:CSpace:blog/unix/FvwmStatesUnderstood:7245dfa1189eb01537461bd118af5488e9ca5427From 82.69.211.1<div class="wikitext"><p>I wonder if there's scope for improving the FVWM man page?</p>
<p>-- Thomas Adam</p>
</div>2012-03-21T12:02:04Z