try parsing it within a try/catch? remember there's parseedn.el or a little cleaner, grep for a ": ? I'd say that generally can only be json

Yeah, probably the latter would be fast and good enough. Thanks!

Also, I didn't know about parseedn.el. Will check it out

can you post a screenshot and expand on exactly what you mean, please? It's hard to grasp it without seeing it

File Contents:

(def foo)

(def bar)

(def foo)
 
 
(def bar)

I'm a fan of having two newlines per top-level form, and would like this rendering even when editing code that doesn't have this convention

I don't think that's possible. afaik there's no special text-property there to distinguish the beginning and end of the top form

I was thinking about how the asciidoc-mode changes font sizes for various headers; it would be cool if we could distinguish we're between top-level forms.

Maybe something treesitter could do?

Maybe, but you still have to traverse the file, find every top form and inject an overlay or a text-property

@U05476190 alternatively what you can do is to use form feed character and use page-break-lines.el, but you still have to manually insert them. Besides, that character still will show up in the source code.

you can write a function that inserts overlays, but you still gonna have to traverse and find every top form.

and run that function on some hook, like find-file-hook, etc.

Yeah, I suppose a different hack would be to run cljstyle to format all files (since it supports this kind of formatter out of the box). But then I'd need to make sure I can run e.g. magit such that it will ignore all whitespaces in status, diffs, etc.

> I'd need to make sure I can run e.g. magit such that it will ignore all whitespaces "D -w" in magit-status

It's just a quality of life improvement when reading code, so may not be worth the hassle. But I wanted to ask just in case there was an easy solution. Thanks for the input!

If I really, really wanted that, I'd probably use overlays. It's an interesting thing to hack on. I may even give it a try. But no promises.

I'm not familiar with overlays, but I'm assuming that's also what clojure-lsp uses for things like the code references? https://clojure-lsp.io/features/#code-lenses-showing-symbol-references

yes, lsp-mode lens are overlays

yup. Also, if you ever used magit margins, in magit-log buffer, press L - that should toggle the margins - details about each commit. Those are also overlays. That's why you can't easily copy them out.

btw, about symbol references. @UKFSJSM38, you don't use Org-Roam do you? I've been wanting to have exactly the same feature that would show the number of backlinks for headings. But I can't find time to hack on it.

I used some time ago, but I never get used, I think I'm just bad at organization 😂 anyway, I touched a good portion of lsp-mode code lens, specially the one that show code lens at the end of line and I love code lens, they are pretty fun.

sounds like a nice feature for org-roam indeed

https://emacs-lsp.github.io/lsp-dart/#flutter-widget-guides is another cool feature I did with overlays for lsp-dart, pretty fun, those lines

There's (setq-local line-spacing 20) but it's global, it doesn't know what a top-level form is I have a custom command that temporarily collapses all forms and increases the line spacing:

it's my poor man's ns outline

why not use imenu?

or lsp-treemacs

because I'm poor 😇

I mean... why am I even asking? It's inappropriate and rude to ask "why do you do X in Emacs?"... "well, because I want to and I can... isn't that obvious?"

I wish there was a :emacs-spin: emoji

Emacs doesn't spin. When it does, we do pkill -SIGUSR2

What? You guys really have too much time to fiddle around, heh? Have you switched to VSCode or something? I've heard that using Emacs is so taxing, you need to constantly tweak it, whenever you have a minute.

yeah, was one of the weekly org-roam tasks 😂

I spent whole twenty minutes today figuring out how to test REST APIs but instead of sending and receiving json, it would work with edn. No job was done in those twenty minutes. I should've used VSCode, where "everything works". And I wouldn't even dare to dream about not staring into json.

(defface lisp-large-top-level-whitespace-overlay-face
  '((t (:inherit default :height 1.5)))
  "Face for the space between toplevel forms")

(defun lisp-large-toplevel-whitespace-remove ()
  (interactive)
  (remove-overlays nil nil 'category 'lisp-large-toplevel))

;; there is a "bug", if you have a comment right above the form
;; you want to move back to the nearest empty line ?
(defun lisp-large-toplevel-whitespace-render ()
  (interactive)
  (lisp-large-toplevel-whitespace-remove)
  (save-excursion
    (goto-char (point-min))
    (while (not (eobp))
      (forward-list)
      (save-excursion
        (beginning-of-defun)
        (forward-line -1)
        (when (looking-at-p "$")
          (let ((ov (make-overlay (point) (1+ (point)))))
            (overlay-put ov 'face 'lisp-large-top-level-whitespace-overlay-face)
            (overlay-put ov 'category 'lisp-large-toplevel)))))))

better picture showcasing the effect

That's awesome! Looks great. I may steal this into my config.

it doesn't detect if there is only a single empty line right now. Maybe another unless with (looking-back "^$") or something would do that

ah, shit... yes, a while ago I struggled with a similar problem. I got annoyed that when I'd kill empty lines it would place them in the kill ring. That absurdly annoyed me, I don't know, I have OCD or something. And I just couldn't get the regexp right.

Very cool @U02CV2P4J6S! Bookmarked and will try it over the weekend. Thanks a lot!

@U0G75ARHC

(advice-add
 #'consult-yank-pop
 :before
 (defun mm/remove-whitespace-only-from-kill-ring (&rest args)
   (setf kill-ring (cl-remove-if #'s-blank-str? kill-ring))))