freenode/#lisp - IRC Chatlog
Search
19:07:08
stacksmith
Good morning! Is anyone else here concerned with github being owned by msft? I am considering moving my repose elsewhere...
19:19:10
White_Flame
certainly there was a sizeable exodus of people away from GH right after the announcement
19:28:11
AeroNotix
if you're so entrenched in github that microsoft taking it over is a problem. Did you ever really give a shit about the underlying reasons to be bothered by microsoft taking GH over?
19:38:05
flip214
v0|d: Microsoft isn't known for making bought software better, so one possible fear is that GH will slowly detoriate and so another hosting must be chosen at some time.
19:50:11
aeth
The main alternative, Gitlab, is perfectly fine as far as software goes, but is not a social network like Github. Very quiet.
19:50:58
drmeister
Hi lispers - does the CLHS say anywhere that structs are not allowed to be redefined?
20:12:56
Shinmera
They'd be in QL too if the loading behaviour wasn't disagreeable with QL's requirements :/
20:15:13
jasom
Shinmera: I just found it slightly humorous that you recommended searching QL to find things, when Radiance is the first thing I think of for a useful package not in QL.
20:44:53
nikki93
hey all -- i just installed quicklisp and moved the ~/quicklisp directory to be ~/.quicklisp instead because i like it not showing up in my usual ~ directory listing and updated .sbclrc accordingly
20:45:27
nikki93
now i was wondering about the ql:*local-project-directories* thing -- do you usually set that in your .sbclrc too? and is it ok if that directory has non-lisp projects too? I like putting all of my projects as directories in ~/Development, whatever language they use
20:46:56
pjb
stacksmith: I've always been concerned by github being a commercial operation (.com). This is why I have my own git repository. And then I used gitorious.org ; but gitorious.org, begin not a commercial operation had financial problems. Finally they've been rescued by gitlab.com a commercial operation (but European based instead of US, so closer to heart).
20:47:19
pjb
stacksmith: there's also framasoft.org, which is non-commercial and even closer (French).
20:48:06
Shinmera
nikki93: That's an easy way, sure. You could also symlink the default local-projects directory.
20:48:21
pjb
stacksmith: and for enterprise git, I set up my own gitlab on enterprise owned servers.
20:48:28
Shinmera
nikki93: The latter has the advantage that it'll work with all implementations immediately, whereas otherwise you need to add the line to each init file.
20:50:05
stacksmith
pjb: much appreciated. I actually started moving things to gitlab.com. While commercial, at least gitlab not invested in sinking open-source.
20:50:54
stacksmith
pjb: and all the evil ones put together does not even begin to approach Google...
20:52:04
stacksmith
Shinmera: true enough, although the subject of where to keep source is on-topic.
21:04:03
defaultxr
does anyone know if there is some way to get output sent to the slime-repl buffer from a command run via uiop:run-program in real-time, as it's printed by the command? i wrote a basic shell script to test that just does 'echo hi' and then 'sleep 10', and while i see 'hi' right away when i run it from the command line, if i run (uiop:run-program "/path/to/test.sh" :output *standard-output*) in my lisp, i only
21:04:04
defaultxr
see 'hi' after the script exits, after the 'sleep 20' finishes. using SBCL 1.4.10, Emacs 26.1, Swank from Quicklisp, Slime from MELPA. already tried using (finish-output) in case that would have any effect but it doesn't seem to.
21:04:43
Colleen
defaultxr: About simple-inferiors https://shinmera.github.io/simple-inferiors#about_simple-inferiors
21:08:15
defaultxr
trying this, but unfortunately it has the same issue... running (simple-inferiors:run "/path/to/test.sh" :output t) and i don't get the output until the script finishes
21:08:24
pjb
stacksmith: there's of course https://gitlab.common-lisp.net/explore/projects?sort=latest_activity_desc
21:09:57
pjb
stacksmith: but of course, the question is that any of those repositories may fail or be bought by evil companies. The only solution is to clone your repositories on all of them…
21:10:44
Shinmera
defaultxr: also, are you sure you pasted the right example? There's a second required argument to the function...
21:11:34
stacksmith
pjb: I am not entirely paranoid yet - just don't want to waste time, support evil or eat animals, whenever possible.
21:12:53
pjb
stacksmith: it's not being paranoid. common-lisp.net has already been done. gitorius.org has been bought by gitlab.com, and github.com has been bought by microsoft.
21:13:52
pjb
stacksmith: so it WILL occur again, so you better clone your repositories. It's easy to push on all of them at once. cf. eg. https://github.com/informatimago/bin/blob/master/git-groups
21:14:49
pjb
even github.com has already been down, several time (or if not specifically done, at least unaccessible for 24 hours from certain parts of the network).
21:14:56
Shinmera
Also useful: updating all git repositories in a directory with this Lisp snippet. http://plaster.tymoon.eu/view/650
21:15:52
pjb
It was a DNS problem IIRC. Perhaps it was common-lisp.org and it became common-lisp.net ?