Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install use-local #3

Closed
daimrod opened this issue Mar 31, 2012 · 6 comments
Closed

Install use-local #3

daimrod opened this issue Mar 31, 2012 · 6 comments

Comments

@daimrod
Copy link

daimrod commented Mar 31, 2012

It would be nice if clhs:print-emacs-setup-form and the README mentioned clhs:install-clhs-use-local.

@Hexstream
Copy link
Owner

clhs:print-emacs-setup-form already does mention clhs:install-clhs-use-local, though only if clhs-use-local.el is not already present in ~/quicklisp/! clhs:print-emacs-setup-form conditionally prints the following before the other instructions:

(Please run (clhs:install-clhs-use-local) in the (Common Lisp) REPL.
This will install clhs-use-local.el in your ~/quicklisp/ directory.
The step below depends on this file.)

As for the README, it already mentions to use clhs:print-emacs-setup-form, which will mention (clhs:install-clhs-use-local) as appropriate.

I guess this behavior is a bit magic for someone who tries to understand how things work exactly, but I was aiming for best usability for a user who just wants to get this "install and setup local CLHS" thing over with as fast as possible.

If you think that's a bit too much magic, maybe I'll slip a hint about the conditional printing in clhs:print-emacs-setup-form (when ~/quicklisp/clhs-use-local.el is present) in the next release, but I'm not inclined to make a new release just for this. It could say something like this:

(~/quicklisp/clhs-use-local.el detected, you may proceed with the step below)

@daimrod
Copy link
Author

daimrod commented Mar 31, 2012

Ok, so that's why I do know about clhs:install-clhs-use-local but I couldn't remember where I heard about it. A message would be nice, but I understand your relectance to make a new release.

@Hexstream
Copy link
Owner

Turns out I need to make a new release because of an unrelated bug (Issue #4), so I'll fix this in passing.

How convenient!

@daimrod
Copy link
Author

daimrod commented Mar 31, 2012

Nice, I close the issue.

@daimrod daimrod closed this as completed Mar 31, 2012
@Hexstream
Copy link
Owner

Well, since I said I'd fix this but it's not yet fixed, I'll reopen the issue so that I can close it from a commit at an appropriate time, else it's a bit too confusing for my tastes. (To me closing an issue means fixed or won't-fix or not-a-bug).

@Hexstream Hexstream reopened this Mar 31, 2012
@Hexstream
Copy link
Owner

D'oh, forgot to close the issue from commit. o_o

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants