This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-22
Channels
- # announcements (7)
- # babashka (17)
- # beginners (45)
- # biff (2)
- # cider (16)
- # clj-on-windows (3)
- # cljs-dev (12)
- # clojure (27)
- # clojure-austin (1)
- # clojure-europe (18)
- # clojure-norway (5)
- # clojurescript (36)
- # conjure (35)
- # core-async (2)
- # datascript (4)
- # datomic (4)
- # emacs (15)
- # fulcro (23)
- # holy-lambda (12)
- # hyperfiddle (1)
- # introduce-yourself (5)
- # nbb (11)
- # off-topic (37)
- # pathom (34)
- # pedestal (9)
- # reitit (4)
- # releases (1)
- # remote-jobs (1)
- # sci (5)
- # scittle (3)
- # shadow-cljs (88)
- # tools-build (4)
I think I got my general.el keybinding issue sorted out, but I've done it by not using , c
as the prefix but instead , ;
which is feeling a bit... spooky gas to me
maybe just some weird state i got into, but somehow my indenting completely broke (auto indenting stopped working, highlight region and indent stopped working). resetting clojure-mode on the buffer got things working again, but i've never run into something like this in ~10 years of using clojure on emacs
Is there a way to search the git log/changelog of clojure libs from a project without traveling to a web browser? if i visit the code in my app it takes me to the m2 cache which as far as i know isn't git/github aware.
That's an interesting thought. I guess it's probably possible to write a package that would query maven/clojars and fetch repo location, to allow operations like git-grep/blame/etc.
Yea. I'm going to look around. If it doesn't exist, maybe i can do something.
This is an interesting idea but I think a rather rare use case. Why/when do you want to do that? Occasionally, I have a similar need but then it's quite easy to simply find it on github and display the history through their UI.
That's basically the essence of the task - figuring out the host URL of the git forge for the lib. And the rest is very simple - you just need to concoct the git-blame-URL. For GitHub/GitLab it would be like .../blob/blame...
.
There's a package: http://github.com/sshaw/git-link. Here's a tiny extension to it I use:
(defun git-link-blame ()
(interactive)
(cl-flet ((git-link--new* (x) (replace-regexp-in-string "/blob/" "/blame/" x)))
(advice-add 'git-link--new :override #'git-link--new*)
(let ((link (call-interactively 'git-link)))
(advice-remove 'git-link--new #'git-link--new*)
(git-link--new link))))
You run it in a file - it will produce the git-blame link. It even works for selected region.> Why/when do you want to do that? What do you mean "why"? Emacsen rarely ask that question. "Because I want that shit. That is why..."
Hehehe. Yah, totally. I constantly have to deal with my inner Emacsen and Clojurist fighting. One wants to write some emacslisp all the time (because I want that shit...). The other one wants to stay pragmatic and avoid writing code as much it is possible (you aren't gonna need it).
In this case I had updated from clojure 1.8 to 1.9 which caused to dependencies to throw exceptions. From my editor i can quickly go to the location of the Exception but I having something assist me to search for the existing solution to this problem would be useful. I mean, in a better world, there would be no breaking changes, but i don't live in that world. Is it really rare? I feel like every time i'm on wants to keep there libs up to date but is afraid of breaking changes?
in this case, the small step that would nice to have automated is just going from the dep to it's github repo even. that way i could search in context for the changelog.