Comments (5)
Ok, this seems to be some bug / miscommunication with Xach.. He was supposed to switch QuickLisp to pull from stable branch, but this last updated pulled tip, and not stable branch..
Log4Slime is not even in the stable branch, it looks like QuickLisp now has rev 26f358e from master.
The bug you reporting was a bug, but already fixed around 2 weeks ago in master, in the commit bb7f3fa
You have two choices here, both involve making a local copy log4cl via ~/local-projects, as described in readme. You can checkout either "stable" branch if you don't want any disruption or "master" branch for latest.
I meanwhile will try to sort out this issue with Xach and decide what to do
from log4cl.
This issue explains some rather strange bug reports. It seems correct decision here is to resume pulling QuickLisp from master branch, since otherwise would be just jerking people around.
from log4cl.
Meanwhile opened quicklisp/quicklisp-projects#524 as this issue may affect other projects then Log4CL, if some other projects also requested "pull from branch" from QuickLisp
from log4cl.
Replacing the Quicklisp log4cl folder's contents with a clean pull fixed the issue.
Thanks a lot for the quick reply!
This could be closed from my initial problem's perspective, but I'll leave it open for now in relation to the Quicklisp bug.
Of course, you may close this if you see it fit.
from log4cl.
It makes no sense to downgrade QuickLisp version now, so I've asked Xach to switch back to continue pulling "master" now instead.. Bumped version to 1.1.1 in preparation for next QuickLisp freeze, nad closing this issue.
from log4cl.
Related Issues (20)
- Log4Slime Elisp side fails to detect numeric EQL specializer
- public API changed: log:config :daily doesn't accept a pathname anymore, only strings HOT 2
- log expansion should not capture stream HOT 2
- Log levels of parent loggers are not applied to messages of children. HOT 3
- Add syntax sugar for logging macros to drop innermost level of auto-naming
- Should serialized-appender use a recursive lock? HOT 6
- slime error message when loading log4cl HOT 1
- log4cl not detecting existing package name
- dependency on sb-posix is not declared HOT 2
- problem on ABCL HOT 2
- Consider using Conium rather than SWANK-BACKEND
- Troubles with log4slime HOT 2
- log4cl:project-options doesn't work. HOT 1
- Unable to install `Log4Slime`
- I haven't thanked you enough. HOT 1
- JOIN-THREAD-ERROR HOT 3
- Recursive lock attempt with `log4cl`
- PLEASE REPORT BUGS IN MAINTAINED FORK https://github.com/sharplispers/log4cl
- Sly integration HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from log4cl.