#doomemacs — Public Fediverse posts

I had not realised how slow doom-modeline is ! Especially in prog-mode.

Just moved to a different modeline and the whole editor feels so much snappier !

#emacs #EmacsGroundup #doomEmacs #doomModeline #lambdaModeline

I had not realised how slow doom-modeline is ! Especially in prog-mode.

Just moved to a different modeline and the whole editor feels so much snappier !

#emacs #EmacsGroundup #doomEmacs #doomModeline #lambdaModeline

I had not realised how slow doom-modeline is ! Especially in prog-mode.

Just moved to a different modeline and the whole editor feels so much snappier !

#emacs #EmacsGroundup #doomEmacs #doomModeline #lambdaModeline

I had not realised how slow doom-modeline is ! Especially in prog-mode.

Just moved to a different modeline and the whole editor feels so much snappier !

#emacs #EmacsGroundup #doomEmacs #doomModeline #lambdaModeline

I had not realised how slow doom-modeline is ! Especially in prog-mode.

Just moved to a different modeline and the whole editor feels so much snappier !

#emacs #EmacsGroundup #doomEmacs #doomModeline #lambdaModeline

so as far as I can tell emacs seems to have two ways of making little icons appear to the side of the text area for line-specific notifications: the "margin", which allows anything, and the "fringe", which allows only images and thus only works in GUI emacs, not my preferred terminal / CLI

this is very inconvenient because Doom Emacs comes with two plugins that put stuff to the side of the text, git-gutter that shows what lines have been changed since the last git commit, and flycheck that shows formatting errors, and I want both of those per-line notifications to be on the left side because that's what I'm used to for a long time now and it'll be very hard for me to train myself to look for those on the right side of the window, but on terminal that means putting them both in the margin, but they don't know how to share the margin or anything, i think it's just a variable that you write to? so one overwrites the other and there's nothing I can do about it? so if I have a formatting error I just won't know about it until I make a git commit containing the error???

That's. Not good. And neither of them seem to have an option to like change the background color of the line or something instead of an icon, so I guess that despite all the effort I put into fixing the colors over SSH before, I'm just going to have to switch to GUI emacs and use X11 forwarding for remote machines?

so as far as I can tell emacs seems to have two ways of making little icons appear to the side of the text area for line-specific notifications: the "margin", which allows anything, and the "fringe", which allows only images and thus only works in GUI emacs, not my preferred terminal / CLI

this is very inconvenient because Doom Emacs comes with two plugins that put stuff to the side of the text, git-gutter that shows what lines have been changed since the last git commit, and flycheck that shows formatting errors, and I want both of those per-line notifications to be on the left side because that's what I'm used to for a long time now and it'll be very hard for me to train myself to look for those on the right side of the window, but on terminal that means putting them both in the margin, but they don't know how to share the margin or anything, i think it's just a variable that you write to? so one overwrites the other and there's nothing I can do about it? so if I have a formatting error I just won't know about it until I make a git commit containing the error???

That's. Not good. And neither of them seem to have an option to like change the background color of the line or something instead of an icon, so I guess that despite all the effort I put into fixing the colors over SSH before, I'm just going to have to switch to GUI emacs and use X11 forwarding for remote machines?

so as far as I can tell emacs seems to have two ways of making little icons appear to the side of the text area for line-specific notifications: the "margin", which allows anything, and the "fringe", which allows only images and thus only works in GUI emacs, not my preferred terminal / CLI

this is very inconvenient because Doom Emacs comes with two plugins that put stuff to the side of the text, git-gutter that shows what lines have been changed since the last git commit, and flycheck that shows formatting errors, and I want both of those per-line notifications to be on the left side because that's what I'm used to for a long time now and it'll be very hard for me to train myself to look for those on the right side of the window, but on terminal that means putting them both in the margin, but they don't know how to share the margin or anything, i think it's just a variable that you write to? so one overwrites the other and there's nothing I can do about it? so if I have a formatting error I just won't know about it until I make a git commit containing the error???

That's. Not good. And neither of them seem to have an option to like change the background color of the line or something instead of an icon, so I guess that despite all the effort I put into fixing the colors over SSH before, I'm just going to have to switch to GUI emacs and use X11 forwarding for remote machines?

so as far as I can tell emacs seems to have two ways of making little icons appear to the side of the text area for line-specific notifications: the "margin", which allows anything, and the "fringe", which allows only images and thus only works in GUI emacs, not my preferred terminal / CLI

this is very inconvenient because Doom Emacs comes with two plugins that put stuff to the side of the text, git-gutter that shows what lines have been changed since the last git commit, and flycheck that shows formatting errors, and I want both of those per-line notifications to be on the left side because that's what I'm used to for a long time now and it'll be very hard for me to train myself to look for those on the right side of the window, but on terminal that means putting them both in the margin, but they don't know how to share the margin or anything, i think it's just a variable that you write to? so one overwrites the other and there's nothing I can do about it? so if I have a formatting error I just won't know about it until I make a git commit containing the error???

That's. Not good. And neither of them seem to have an option to like change the background color of the line or something instead of an icon, so I guess that despite all the effort I put into fixing the colors over SSH before, I'm just going to have to switch to GUI emacs and use X11 forwarding for remote machines?

Bash does an intro to #Doomemacs, a nice #vim layer on #emacs ... Great video, brava!

@trevdev @bashbunni

Bash does an intro to #Doomemacs, a nice #vim layer on #emacs ... Great video, brava!

@trevdev @bashbunni

Bash does an intro to #Doomemacs, a nice #vim layer on #emacs ... Great video, brava!

@trevdev @bashbunni

Bash does an intro to #Doomemacs, a nice #vim layer on #emacs ... Great video, brava!

@trevdev @bashbunni

Bash does an intro to #Doomemacs, a nice #vim layer on #emacs ... Great video, brava!

@trevdev @bashbunni

@ballpointcarrot #doomemacs is great! I wouldn't worry about not building everything from scratch. Doom is also optimized in ways that would be nearly impossible for an individual to recreate in a from-vanilla config

@ballpointcarrot #doomemacs is great! I wouldn't worry about not building everything from scratch. Doom is also optimized in ways that would be nearly impossible for an individual to recreate in a from-vanilla config

@ballpointcarrot #doomemacs is great! I wouldn't worry about not building everything from scratch. Doom is also optimized in ways that would be nearly impossible for an individual to recreate in a from-vanilla config

@ballpointcarrot #doomemacs is great! I wouldn't worry about not building everything from scratch. Doom is also optimized in ways that would be nearly impossible for an individual to recreate in a from-vanilla config

@ballpointcarrot #doomemacs is great! I wouldn't worry about not building everything from scratch. Doom is also optimized in ways that would be nearly impossible for an individual to recreate in a from-vanilla config

Had some mounting frustrations with my work installation of #doomemacs . Decided to try wiping it and creating an #emacs config from scratch.

Stopped two hours later, realized that I was biting off way more than I could chew in one night, cleaned the library cache, and reinstalled doom. That's a "I'm on a sabbatical for a month" type of project 🙃 .

Had some mounting frustrations with my work installation of #doomemacs . Decided to try wiping it and creating an #emacs config from scratch.

Stopped two hours later, realized that I was biting off way more than I could chew in one night, cleaned the library cache, and reinstalled doom. That's a "I'm on a sabbatical for a month" type of project 🙃 .

Had some mounting frustrations with my work installation of #doomemacs . Decided to try wiping it and creating an #emacs config from scratch.

Stopped two hours later, realized that I was biting off way more than I could chew in one night, cleaned the library cache, and reinstalled doom. That's a "I'm on a sabbatical for a month" type of project 🙃 .

Had some mounting frustrations with my work installation of #doomemacs . Decided to try wiping it and creating an #emacs config from scratch.

Stopped two hours later, realized that I was biting off way more than I could chew in one night, cleaned the library cache, and reinstalled doom. That's a "I'm on a sabbatical for a month" type of project 🙃 .

Had some mounting frustrations with my work installation of #doomemacs . Decided to try wiping it and creating an #emacs config from scratch.

Stopped two hours later, realized that I was biting off way more than I could chew in one night, cleaned the library cache, and reinstalled doom. That's a "I'm on a sabbatical for a month" type of project 🙃 .

Went back from #doomemacs to my own #emacs configuration. There were just too many unknowns, too little documentation - basically too much magic.

Went back from #doomemacs to my own #emacs configuration. There were just too many unknowns, too little documentation - basically too much magic.

Went back from #doomemacs to my own #emacs configuration. There were just too many unknowns, too little documentation - basically too much magic.

Went back from #doomemacs to my own #emacs configuration. There were just too many unknowns, too little documentation - basically too much magic.

Went back from #doomemacs to my own #emacs configuration. There were just too many unknowns, too little documentation - basically too much magic.

For my #writing i thought that #doomemacs was the right choice, because i thought it will be more easy for a non programmer like me. It was not. I was trying things that i've never understood and it became frustrating.

The best decision i've made was to restart with GNU #emacs following some tutorials. Now i have a simple config that works. And i've learned ... a lot.

I just love emacs

For my #writing i thought that #doomemacs was the right choice, because i thought it will be more easy for a non programmer like me. It was not. I was trying things that i've never understood and it became frustrating.

The best decision i've made was to restart with GNU #emacs following some tutorials. Now i have a simple config that works. And i've learned ... a lot.

I just love emacs

For my #writing i thought that #doomemacs was the right choice, because i thought it will be more easy for a non programmer like me. It was not. I was trying things that i've never understood and it became frustrating.

The best decision i've made was to restart with GNU #emacs following some tutorials. Now i have a simple config that works. And i've learned ... a lot.

I just love emacs

For my #writing i thought that #doomemacs was the right choice, because i thought it will be more easy for a non programmer like me. It was not. I was trying things that i've never understood and it became frustrating.

The best decision i've made was to restart with GNU #emacs following some tutorials. Now i have a simple config that works. And i've learned ... a lot.

I just love emacs

For my #writing i thought that #doomemacs was the right choice, because i thought it will be more easy for a non programmer like me. It was not. I was trying things that i've never understood and it became frustrating.

The best decision i've made was to restart with GNU #emacs following some tutorials. Now i have a simple config that works. And i've learned ... a lot.

I just love emacs

@tylerayoung @katafrakt I am really looking forward to the #Neovim and #DoomEmacs integration \o/

@tylerayoung @katafrakt I am really looking forward to the #Neovim and #DoomEmacs integration \o/

@tylerayoung @katafrakt I am really looking forward to the #Neovim and #DoomEmacs integration \o/

@tylerayoung @katafrakt I am really looking forward to the #Neovim and #DoomEmacs integration \o/

@tylerayoung @katafrakt I am really looking forward to the #Neovim and #DoomEmacs integration \o/

I think #DoomEmacs has thoroughly undone my #Plan9 conditioning.
Or maybe no longer using a #ThinkPad is the actual reason. All the touchpads I use are worse than the Clit Mouse TM. They are still better than having to reach for an actual mouse, but damn, I miss that red dot.

I think #DoomEmacs has thoroughly undone my #Plan9 conditioning.
Or maybe no longer using a #ThinkPad is the actual reason. All the touchpads I use are worse than the Clit Mouse TM. They are still better than having to reach for an actual mouse, but damn, I miss that red dot.

I think #DoomEmacs has thoroughly undone my #Plan9 conditioning.
Or maybe no longer using a #ThinkPad is the actual reason. All the touchpads I use are worse than the Clit Mouse TM. They are still better than having to reach for an actual mouse, but damn, I miss that red dot.

I think #DoomEmacs has thoroughly undone my #Plan9 conditioning.
Or maybe no longer using a #ThinkPad is the actual reason. All the touchpads I use are worse than the Clit Mouse TM. They are still better than having to reach for an actual mouse, but damn, I miss that red dot.

I think #DoomEmacs has thoroughly undone my #Plan9 conditioning.
Or maybe no longer using a #ThinkPad is the actual reason. All the touchpads I use are worse than the Clit Mouse TM. They are still better than having to reach for an actual mouse, but damn, I miss that red dot.

There is a lot going for #Obsidian in terms of UI performance and UX niceties, but one thing keeps pulling me back to #DoomEmacs and #OrgRoam: laser focused keyboard oriented setup out of the box

I can move subtrees around quicker than I can think.

(or I could if #Emacs didn't freeze up for 30 seconds randomly. oh well, can't have it all. any by "it all" i mean "widespread adoption of async UI patterns in your favorite editor".)

There is a lot going for #Obsidian in terms of UI performance and UX niceties, but one thing keeps pulling me back to #DoomEmacs and #OrgRoam: laser focused keyboard oriented setup out of the box

I can move subtrees around quicker than I can think.

(or I could if #Emacs didn't freeze up for 30 seconds randomly. oh well, can't have it all. any by "it all" i mean "widespread adoption of async UI patterns in your favorite editor".)

There is a lot going for #Obsidian in terms of UI performance and UX niceties, but one thing keeps pulling me back to #DoomEmacs and #OrgRoam: laser focused keyboard oriented setup out of the box

I can move subtrees around quicker than I can think.

(or I could if #Emacs didn't freeze up for 30 seconds randomly. oh well, can't have it all. any by "it all" i mean "widespread adoption of async UI patterns in your favorite editor".)

There is a lot going for #Obsidian in terms of UI performance and UX niceties, but one thing keeps pulling me back to #DoomEmacs and #OrgRoam: laser focused keyboard oriented setup out of the box

I can move subtrees around quicker than I can think.

(or I could if #Emacs didn't freeze up for 30 seconds randomly. oh well, can't have it all. any by "it all" i mean "widespread adoption of async UI patterns in your favorite editor".)

There is a lot going for #Obsidian in terms of UI performance and UX niceties, but one thing keeps pulling me back to #DoomEmacs and #OrgRoam: laser focused keyboard oriented setup out of the box

I can move subtrees around quicker than I can think.

(or I could if #Emacs didn't freeze up for 30 seconds randomly. oh well, can't have it all. any by "it all" i mean "widespread adoption of async UI patterns in your favorite editor".)

I have really been wrestling lately with my config.el file for @doomemacs

The issue seems to be that the after! macro does *not* work, and I end up with custom configurations not loading

This manifests with is my dape-configs, so when I relaunch emacs after an update (I use emacsclient) I get... no configs (until I go to config.el and C-x C-e on those blocks)

I think my hacky solution has been to just use use-package dape instead, but how is after! supposed to work?

#emacs #doomemacs