My #emacs discovery for today is dired-omit-mode. It hides less interesting files (object files, backups etc). There are a few options to tweak what you want hidden.
The default binding is C-x M-o but I've also put it on just M-o in my config so that I can toggle it quickly.
@holgerschurig@rzeta0 I do frequently wish Emacs were written in Common Lisp - which has package namespaces and gradual typing. Emacs Lisp is kind of special.
Today I learned and practiced using Pikchr. Pikchr is a low-level diagram markup language. This is my second attempt at it and I think it clicked this time.
The program is available is a single function library and a CLI that emits SVG.
I used a lot of dot (from graphviz) in Org documents. But sometimes it arranges the objects in ways I don't like, and with dot it's often a fight against it to get the layout I like.
@holgerschurig I don't have much experience with graphviz but I had similar problem with Mermaid. Pikchr does give you more finer control over layout with the trade-off of complexity.
If I execute them, I get what I want.
But when part of the init.el they seem to get reset.
If I include them towards the top of the init.el,
I can notice the larger font and then it "disappears".
@al3x Since I had a similar issue, look at the end of your init.el, where you have your (custom-set-variables ...) (which is created by the customize facility). It is very likely that you once changed your font interactively with customize and have this configuration still in your init.el.
#emacs#logseq anyone have a working setup with logseq (in orgdown) and #orgroam playing nice in logseq's folder (orgroam dailies in 'journals', etc)? Currently my vault is a mix of org and md but I'm hoping to at least get the org files recognized while I work on converting the md (or figure out #mdroam). I tried playing with org-logseq but even though I'm matching correctly on its grep for the folder and I have title properties I couldn't get it working after a good attempt. #askfedi
@Neblib I "kind of" do. I am using heavily modified org-roam-logseq.el though. There still are some issues, e.g. Logseq fails to recognize ID references as backlinks (linking itself works).
I was planning a blog post about my setup, but with recent news about Logseq DB development I am considering ditching it.
@wigol yeah the logseq db announcement was a bit disappointing for sure. Emacs 30 being on Android takes away some of the reasons for a logseq as the mobile end of a org workflow, especially if developer interest refines that mobile experience further.
The rootwork v0.2 blog posted about the author's journey through text editors, from classics such as vi(m) and Emacs to tools I've never heard of. They explain what they use the editors for and why.
After spending some time learning meow's editing model, I've finished a moderate customization of the default qwerty layout. It's an attempt to find a synthesis of my emacs, vi, and CUA muscle memory while favoring selection-first editing.
Is there a way, even using a different structure (but possibly keeping those items grouped), to have an unique numbering for all those items in the page?
@AAMfP you can either use the start parameter in your ol, generated manually on conversion from org mode, or define a CSS counter and use that in the ::mark (IIRC) of your ol
Ever been too scared to use the #Emacs file manager Dired? I have and still remember what it's like, especially when I was new to it. But it doesn't have to be that way. Here's my take on making Dired a bit easier to use, for beginners and experienced alike.
Announcing Casual Dired, now on MELPA. Read more about it at the link below.
@scathach@thgs in my last days of c++ i had started replacing the self-insert keys to completely eliminate holding shift (because it was a source of RSI.) so things like typing ;; would become :: and - would become an underscore if next to an identifier character kind of stuff
For the entire time I've been using #Emacs, I never used (or wanted) any kind of spell-checking. That is changing now that I'm using it a lot more to write notes/documentation with #OrgMode / #OrgRoam.
Ideally I want to only do spell-checking on comments, when editing code, and similar configurability for Org documents.
What is the recommended method for something like that in 2024 (on macOS, if that makes any difference)?
Huh, TIL Emacs has a cheat sheet command, M-x cheat-sheet. Really need that for all the C-x r commands. Though, general tip: After any prefix keymap you can press ? to see all the keybindings under it, like so: C-x r ? (second screenshot shows what that looks like)
Instead of enabling Evil mode globally, I now have it turned on only in buffers with major modes derived from prog-mode or text-mode.
Since Evil is disabled in non-editing buffers like Magit and Dired (where it was a nuisance), I got rid of Evil collection and cut my startup time in half.
One of my students opened up #Emacs today, opened up a GUI file manager, found a file, grabbed the icon, dragged it onto Emacs, and dropped it. And it WORKED. I'm not sure which part distressed me more.
It hides various secrets like passwords, username, email addresses, IP addresses and hash sums in Emacs buffer, so you can show these buffers online without risking privacy.
To anyone in and around Erlangen/Nueremberg, I am organising a german introduction to Emacs next week (10.5.) at my university. My intention is to give a high-level, value-driven overview instead of wasting time on accidental and superficial features such as Magit, Org-Mode, SLIME, etc. (there are plenty of those already).
