Re: ASDF3: How to globally disable output translations on Windows
On Tue, Mar 8, 2016 at 3:59 PM, 9nauuk <9na...@hmamail.com> wrote: > As a side note, on Windows, if (get-folder-path :local-appdata) is ever > nil, and XDG_DATA_HOME is not defined, (xdg-data-home "config/") in > XDG-CONFIG-HOME will explode in you face. > Wait, shouldn't local-appdata *always* be defined by Windows? >> the filesystem. I believe "XDG" stands for "Easter Egg Hunt" in some >> language > > Quite fitting. What happens to the good, old, dot-files (such as .emacs, > .gnus, .cshrc, ...etc.)? Why this convoluted way? > I was recently bitten by Emacs and Clojure not agreeing on where the $HOME for placing those files would be (Emacs deciding to put it under .../Roaming/... so it would be shared between machines or some such). Plus, under Windows, it isn't so nice multiplying Unix-style config files in the HOME directory (wherever it be). > In both transitions from ASDF to ASDF2 and from ASDF2 to ASDF3, I had > to spend time to make object files stay where I want them to stay. > Apologies about that. We try to pander to the common case first while enabling people like you to customize, but I admit we don't test customizations as often, especially not on Windows. > Lng Live ASDF3! > May it die in peace and soon leave place to ASDF4. (No, I don't know that anyone is working on an ASDF4.) —♯ƒ • François-René ÐVB Rideau •Reflection• http://fare.tunes.org A man is usually more careful of his money than he is of his principles. — Edgar Watson Howe
Re: ASDF3: How to globally disable output translations on Windows
Hi, I'd like to thank Robert Goldman, Faré, and 73budden for replying to my message. Robert brought my attention to XDG-CONFIG-HOME in uiop.lisp. After taking a look at it and XDG-CONFIG-DIRS, I realized the following 3 directories (I don't think they would ever evaluate to NIL and (NIL NIL) on a Micros*t Windows machine): (get-folder-path :local-appdata) (mapcar 'get-folder-path '(:appdata :common-appdata)) would always take precedence over "config/", which means ASDF3 would never see $HOME/config/common-lisp/asdf-output-translations.conf.d/. The source code of XDG-CONFIG-DIRS also points out an easy way to globally disable output translations on Windows: Define an environment variable, XDG_CONFIG_DIRS, that points to whatever config directory you use. As a side note, on Windows, if (get-folder-path :local-appdata) is ever nil, and XDG_DATA_HOME is not defined, (xdg-data-home "config/") in XDG-CONFIG-HOME will explode in you face. > the filesystem. I believe "XDG" stands for "Easter Egg Hunt" in some > language Quite fitting. What happens to the good, old, dot-files (such as .emacs, .gnus, .cshrc, ...etc.)? Why this convoluted way? In both transitions from ASDF to ASDF2 and from ASDF2 to ASDF3, I had to spend time to make object files stay where I want them to stay. Lng Live ASDF3! Best wishes, -9nauuk
Re: ASDF3: How to globally disable output translations on Windows
Hi! This works for me with asdf 3.1.6 https://en.wikibooks.org/wiki/Common_Lisp/External_libraries/ASDF/Budden%27s_infrequently_asked_questions#How_do_I_make_portable_lisp_program_with_it.27s_own_fasl_cache_in_a_given_directory.3F
