BTW - thanks for Mistral. Another tool in the box!
BTW - thanks for Mistral. Another tool in the box!
Quite right!
You need to take it all (AI or internet searches) with a huge pinch of salt. Even ye olde text books were not infallible and often out of date, so sodium chloride was also required even then.
The code either works or it doesn’t - it’s all in the testing. If you deploy AI suggestions without thought you deserve the consequences.
so just use chatgpt or gemini - pretty sure they sucked in all of reddit to form their KB
I followed up on github as you suggested and a very nice young man took a look at it and said that the code already does work the right way (at least the way I and their little poll think it should work). But, it turns out that the fix (from 2021) has not been deployed - it’s to be in the next release.
So I don’t know what will happen now - I’ll continue to use my workaround, so I’m happy enough.
So he’s a journalist </s> Thanks for the warning, saved me a read.
OK, more than wow! Probably the most helpful, in-depth and up to date coverage of this topic I’ve seen in 40 years of barely scratching the surface of emacs. Thank you!
I find the various linters and checkers a bit too intrusive while I’m trying to code - I prefer to just have a check when I stop fiddling with the code and save it. So I have these checks run in after-save-hook - if there are errors, I get a popup otherwise nothing and all is good:
;; ** syntax checking on file save:
(defun bh/check-syntax ()
"Check syntax for various languages."
(when (eq major-mode 'emacs-lisp-mode)
(ignore-errors (kill-buffer byte-compile-log-buffer))
(let ((byte-compile-warnings '(not free-vars obsolete unresolved)))
(unless (byte-compile-file buffer-file-name)
(pop-to-buffer byte-compile-log-buffer))))
(when (eq major-mode 'sh-mode)
(compile (format "bash -n %s && shellcheck -f gcc %s" buffer-file-name buffer-file-name) t))
(when (eq major-mode 'ruby-mode)
(compile (format "ruby -c %s" buffer-file-name) t))
(when (eq major-mode 'python-mode)
(compile (format "python -B -m py_compile %s" buffer-file-name) t))
(when (eq major-mode 'awk-mode)
(compile (format "AWKPATH=$PATH gawk --lint --source 'BEGIN { exit(0) } END { exit(0) }' --file %s" buffer-file-name) t)))
(add-hook 'after-save-hook #'bh/check-syntax)
I don’t work much with json files but I daresay the idea could be extended to them. Sorry about the crappy elisp.
virt-manager for the win!
“64-128mb ram” is hardly “low memory”!
I’ll join in too - here’s mine
You can’t avoid IBM/RedHat - they contribute to the kernel and many, many other parts of Linux eg systemd. I have no idea what you mean by DIY distros, what a peculiar adjective in this context. Linux itself is DIY. Life is DIY.
That said, voidlinux is an independent distro without systemd or snaps based on runit for init and xbps for package management. It’s also a STABLE rolling release.
waybar is good
scrcpy for android connectivity; syncthing to get files to and fro android (and any other linux system)
clipman for clipboard manager
wallpaper - whatever for? with a TWM you rarely see the background
emacs - because it’s life (I jest)
Can’t believe no-one mentioned voidlinux yet. It’s very tasty.
I daresay there’s a way to do something like this with fzf
Maybe check here: https://linux-hardware.org/
waypipe - yes. But also wayvnc - I’ve been using wayvnc for a couple of years to export a headless wayland session from a file server. FOr my sins I use vncviewer on XWayland to consume it as it still seems to be the fastest.
To imply that systemd is merely an init system is ingenuous at best and dishonest at worst - systemd is so much more than an init system, as that article mentioned. Since the article was written in 2014 systemd has grown massively in scope, even more than the author feared.
It manages DNS, home directories, system services, seat managment, cron, system logging, booting… the list is ever growing. As such many people fear it is becoming too dominant through making more and more software dependent on it. It is not atomic - it is very difficult to have just one piece of systemd as its parts are tightly integrated and inter-dependent.
One could even claim that systemd failed in it’s original remit - to make startup as fast as macOS by running tasks in parallel and by deferring service startup until they are actually needed. The result has been a not very performant init system - many init systems are faster eg runit, dinit. The systemd people now claim that speed is not a design goal.
It is, however, open source and very widely adopted. Most people don’t care - they just want to run their browser and word processor.
What for? Even if they have improvements in some areas, the original POSIX standard utilities will continue to be needed for script compatibility. You’re not going to swap them out - at best you can add them and then you just have an additional code base to support with additional attack surface to protect.
I vote for voidlinux - I have no idea why, but I get almost double the battery life compared to fedora. No doubt it’s something stupid I’ve done on fedora but - I just love void.
voidlinux: gave me much better battery life - I assume because it starts as a minimal system and one adds only the essentials to do the job - compared to the soup-to-nuts distros that pile everything in so that newbies are acccomodated. Of course, the voidlinux approach needs more linux skills - but it’s not that hard and the doco is great.
Also, I love the back to basics runit init system and runsv service runner (I’m old so I like that stuff) and the ultra fast xbps packaging system.