Clojurians Log v2

I normally use git log --follow -p -- $file_or_dir to see a continous history of changes for a file Although Magit would be better!

I use magit-log-buffer-file and that works for both files and directories but then I get only a list of commits. To see a diff for a specific commit, I can just press Enter, but not sure how to get a summary diff for all the commits, properly. (I could select all the commits and do magit-diff but that includes everything that changed between the first and last selected commit)

magit-diff supports selecting both files and ranges

to select specific files, just press - twice and then r for range if I remember correctlyu

Ah, yes, -- is what I wanted 🙂 Thanks!

I'd like to list all the commits touching given file or directorymagit-file-dispatch for the current buffer file in Dired, you can mark specific files and dirs and run magit-dired-log, that will show the commits pertaining only the marked files.

I proposed to use metosin/tools and convert our schemas, so this:

(s/defschema error_schema
  {(s/required-key "status") s/Int
   (s/required-key "code")   s/Str
   (s/required-key "title")  s/Str
   (s/required-key "detail") s/Str})

(s/defschema error_schema
  (st/required-keys
   {"status" s/Int
    "code"   s/Str
    "title"  s/Str
    "detail" s/Str}))

Zed (or similar) users probably would be like: "well, AI could've done that directly in the Clojure buffer", but that's not the point, innit? There are multiple ways to do that in Emacs as well. Can you ask a Zed model to change your font, colors, terminal settings? Making changes to the exact same instance it's running in?

yeah it is truly fun time with Emacs these days. A mix of gptel and codex-cli has been a powerful ally for remaining productive in a sudden switch to python at my job XD

Holy mother of Alan. You can't even make this shit up. Just when I wrote "all my conversations with LLMs get stored ...", I decided to check "what the heck have I been even storing?" Even though I don't have to do that, I typically keep one topic of a conversation per file. I have also "quick question" workflow where simple, small conversations all get stored in http://quick.org file. I can always separate the context window within different headings by narrowing. So, I was going through all my LLM log files. And remembered there is something like dired-preview mode - I don't need to open each file, then kill the buffer just for the sake of peeking into it. But I didn't have that package installed. I asked LLM and it gave me the exact instructions - I could've searched, but that was quicker. https://imgur.com/a/ZIRvQns. I decided to make permanent changes in my config, but if it was a one-time thing, I wouldn't even have to save it. It took me longer to tell you I did it, than actually doing all that. See? I just added a new feature to my editor, without restarting it, without closing anything, without losing any context, with a minimal interruption from work, just by typing some text, and all that within minutes.

Yes, I agree 100%. It's a personal jorney. The information is omnipresent, but you only start realizing it when you reached the point of no return. Same with cars: you don't even notice how many Hyundai cars drive out there until you buy one. But I really appreciate everyone who shares and shows his tools/workflows. If an former colleague of mine hadn't shown me this weird language, I still wouldn't know about Clojure today.

I almost can hear your excitement. This looks very amazing. Unfortunately it's the same with Clojure, it's almost impossible to transport this feeling to people who haven't experienced it yet by themselves. Even if you show/share it, not everyone get it.

> it's almost impossible to transport this feeling to people who haven't experienced it Yup, that's well-known phenomena - "tacit vs explicit" knowledge. Known since around 1960s. • Tacit: personal, context-specific knowledge we can't fully articulate (riding a bike, recognizing faces, REPL-driven code writing, etc.) • Explicit knowledge: formal, codifiable stuff that can be written and shared (equations, procedures, facts) Just like master musicians outperform novices through accumulated tacit knowledge but can't magically turn every newbie into a maestro, the same way, the excitement we feel through using a Lisp REPL cannot be taught by using words and hand-waving.

The hard [sad] part of it all is that I can't even confirm my personal, empirical hypotheses for why I love using Lisp, yet I fail most of the time to inspire other developers to give it a try. There's no way to know what shaped my emotions and how my tacit knowledge formed. Perhaps I really needed to go through years of different programming language stacks to arrive finally, one day, at where I am.