<html><head></head><body>I get all you're saying, but I don't think it's relevant. This is for people who want to WRITE code, so hiding their code from them in a config directory doesn't make sense.<br>
<br>
I'm fine with putting config files in those hidden directories(although I feel compelled to say that XDG makes that you complicated), but not source code that people want to edit. People shouldn't have to play ls -a hide and seek to find their own source code...<br><br><div class="gmail_quote">On March 12, 2014 11:20:23 PM CDT, Daniel Herring <dherring@tentpost.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On Wed, 12 Mar 2014, Robert P. Goldman wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> I am sorry, but I promise you that this will NOT be consistent with XDG. I have no idea why those people think it's a good idea to put files in directories where ls cannot find them.<br /> <br /> ASDF already has a deeply-nested, invisible-to-ls location that is XDG compliant where you can put your files if that's what floats your boat.<br /> <br /> It was writing a description of where to put your files in this XDG-compliant location that convinced me that we needed an alternative that was obvious and easily accessible.<br /> <br /> In case you haven't guessed, I'm not a fan of this standard! :-)<br /></blockquote><br />I would agree that XDG is over-engineered and under-specified.<br /><br />However, ls finds dot files just fine (alias ls="ls -A" if it helps), and <br />"normal use
rs"
usually install programs in "system directories", not their <br />home directory.<br /><br />Given the current CL ecosystem, things are constantly changing, <br />implementations provide little fasl compatibility, CL installs are often <br />per-user, etc. Thus the current best default for sources is in $HOME. I <br />would argue that the use of $HOME is the real problem, and "hiding" things <br />is the right solution for users (as opposed to developers who can be <br />expected to memorize a slightly obscure path).<br /><br />Two default paths is not better than one.<br /><br />There is a reason MS Windows has "hide system files" enabled by default. <br />Some things are too complicated for "casual users", and an obscure <br />"~/common-lisp" is just asking for grandma to delete the folder she <br />"doesn't want"...<br /><br />In systems like OS-X-style "disk images" and Java-style jarfiles, the <br />entire application is self-contained. Thus it is quite appropriate fo
r <br
/>the full path to be user-visible, for deleting the file is uninstalling <br />the app.<br /><br />- Daniel<br /><br />P.S. In case I've gone off-kilter, I promise to get some sleep before any <br />further replies.<br /><br /></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>