Never gave me a practical problem in many years of elisping Personally I'd be happy to see it more commonly used!

Typical convention is the second one, but plenty of people use slash namespacing. Not worth worrying about it 🙂

That is so helpful, thanks for your quick feedback!

https://github.com/purcell/package-lint gives me errors such as:

99:0: error: `clay/make-last-sexp' contains a non-standard separator `/', use hyphens instead (see Elisp Coding Conventions).  

TIL about p-lint. Guess we should use it in CIDER etc (which predates that linter)

I've seen a lot of things in the form clay/make-last-sexp and this its very useful to identify the source of these functions. It makes it very clear to me this way.

Thanks, it helps to know.

Agreeing with package lint here. Emacs itself also uses - everywhere

Macro to the rescue

Start in dired at the first file

Go into the file, press F3 to start recording a macro

Jump to dired, next line, enter

F4 to end the macro

https://github.com/protesilaos/dired-preview might save you having to open them at all, but I agree macro + dired is the way to go otherwise

Now you can press F4 to go to the next file

I think I’ll try using macros* since I’d like to get more experience using macros. Thank you both! 🙏 ❤️

Another approach being to feed them into Clojure and cider-inspect the result

these are not written macros

these are kmacros - keyboard macros, recorded live

very powerful tool 🙂

oh, man this is totally amazing. I had no idea it would be so simple to do and so easy it would be to use. 😁 😁 😁 😁

I realise you've already learned used macros to solve this, which is probably way better, but if you use the emacs server, you could also open them all with emacsclient -nw -c *.json and run server-edit, which is bound to C-x # by default, to say you're done editing that file and move on to the next one. When you get to the end of the list it will return you to the terminal prompt. Also, if you just wanted to read them, you can use less *.json to display each in turn and then :n to goto the next one (three less characters than vim ;P) or if you've installed bat then that will display them all in a paginated fashion (like less) and probably give you syntax highlighting.

@U0P0TMEFJ with your suggestion, I was able to come up with this abomination:

ls sites/*json | xargs -n 1 less

ls sites/*json | xargs -n 1 bat --paging=always

I was remote working for a company in Berlin a while ago, but I'm generally UK based 😉 ... I hope your currently location is treating you well too. 🙂

Oslo as usual, with real snow this winter, which I appreciate!

Oslo is nice. We had a great holiday in Tromsø a few years ago in Jan to see the Aurora, and spent a few days in Oslo. The Norwegian scenery can be amazing ;)

>> Vim was then opened with all the files, :next shows me the next file. Problems: > • I have to type 5 letters each time I move to the next file. I’d prefer an action that was one letter. FYI, :n works just as well as :next, I didn't even know :next was possible and always used :n

https://youtu.be/q4ZJPiW9beE?si=_ivbugBevAMhwTg7 ... this seems like a good reason to live in Oslo 😉