It appears to be an #emacs-ish program that uses #commonlisp for customization.
Apparently there have been other emacs clones based on #go and #rust and I guess those are called #emacsen ?
Without going too into my personal details, I’m not a professional programmer and most of my experience is with a modern programming language, #swift, and a high level programming language, #python.
I’ve tried learning #elisp several times by completing various programming exercises and I end up quitting because something obnoxious comes up that, from my minimal programming experience, appears to be due to elisp‘s age. Again, I’m not a pro, so this is just my amateur take.
I did a some programming challenges with #clojure which was hugely fun (mostly because of how fun it feels in emacs 😁) so I don’t think it’s the #lisp part of emacs I have a distaste for.
I’ll probably give it a serious go within the next week here and possibly report back, but I can’t imagine an emacs clone without #magit#orgroam and ChatGPT-shell will really ever become my daily driver 🙃
Every 6 months or so I say to myself, "I'm going to document all my computer doings on a website," and I jump into #hugo . Very shakily get it to kind of work, get some posts going, give up, come back 6 months later and try to add a post and everything breaks.
I'm thinking I'm just gonna do HTML + CSS so I can... know what's going on?
Anyone else do this? Anyone know a good way to turn #orgmode files (or preferably) one giant orgmode file into posts on a website?
I know of #ox-hugo but this also turns into.... a bunch of figuring out (of things I'm not entirely interested in).
@ctietze I’m always glad to see a solution to #xcode and I’m glad for everyone’s mentions in this toot thread, but in the end, I feel like it’s better to just use Xcode and force solutions onto through a mixture of yabai/skhd, better touch tool and hammerspoon.
Does anyone have an alternative to XCTest for running #swift tests?
I've tried using the #XCTest many times, but the only time I've ever been able to use it was with an absolutely new project, and I have to keep double checking that the package itself (not the tests) continue working... until it doesn't.
I've fiddled with it time after time after time. A lot of tests I need to run just check for equality it's like... I might as well just make a test on it's own that tests for equality with a few hardcoded values.
@ctietze I do assume that when I’m using a library as old as XCTest and it’s being as obtuse as I find it to be, there’s something going on on my end.
I am glad you’ve made it known that XCTest, broadly speaking, works. I’ll keep futzing around.
Currently, I get an error for every Core Data call my program uses and then each error I click, it takes me to the spot of the error, than all the core data errors go away for that spot. I do this for every “error” until I have no errors, try to run the test, all the errors appear again.
I haven’t done enough futzing to warrant help from Internet yet, but I’ll reply here when (if) I get to a more concrete problem.
@ctietze Okay, it was just a matter of putting all the files into the target membership of the testing. I certainly had tried very little before complaining on the Internets about it.
Quick question to you or anyone else. Is there any downside to including any files in my xcode directory in the tests target membership? Should I just put every file into tests membership? Is there anyway to default this for when making a new file?
@ctietze I just mean I had to tick this box for my #coredata file and a couple of others. I'm pretty sure I should be doing this for any files I want #xctest to see and be able to use (test).
If this is it not the case and is a bad sign please let me know!
The disappearing errors were, I think, because when I tried to run the tests the errors came up, then when I clicked the error and it brought me to the code the compiler looked at it for regular building (not testing) and would erase the error markings, until I tried to run the test.
If there's anything else I'm missing, please let me know, and thanks for the feedback 👍
@louis I think it would be neat to have "Stupid (#emacs) questions Sundays".
This is far and away the friendliest emacs community I've ever encountered as far as helping and answering questions... even "stupid" ones!
There's always a fear about asking "stupid" questions, especially when you're asking a bunch of grizzled been-using-emacs-since-1992 programmers.
For me, emacs is very much about discovery, and, I suspect, even the wisest emacs gurus can get nice little tidbits from seemingly "obvious" information.
Anyway, just my two cents, thanks for the community!
Pressing ( when in dired mode enables dired-hide-details-mode.
This makes dired show only the file names which is... 99% of the time exactly what I want, and I /especially/ don't want the file name after all the other information about the file.
A file's ownership information is never of any concern to me and having it as the first (most important) column while having the file name (the most important information) in the last column where it can awkwardly word wrap or fall of the screen is... quite annoying.
Also...
This does not make dired-hide-details-mode run whenever I open a dired window
However, the first question I have is how do they plan to make money? It's not clearly mentioned on the site as far as I can tell so I can't help but feel a little skeptical.
@daviwil I used to use this quite some time ago, but I believe they were bought up by an advertising company. I can only imagine privacy breaching reasons for why.
