doomemacs / doomemacs/core

set-popup-rule macro breaks fringe

Open
#6,974 1 comment 0 reactions 0 assignees View on GitHub
is:bug needs-triage
Dominant language
Emacs Lisp
Stars
22.7k
Forks
3.1k
Avg merge
10h 46m
Merged PRs (30d)
4

Description

### I confirm that...

- [X] I have searched the [issue tracker](https://github.com/doomemacs/doomemacs/issues), [documentation](https://docs.doomemacs.org), [FAQ](https://docs.doomemacs.org/-/faq), [Discourse](https://discourse.doomemacs.org), and [Google](https://google.com), in case this issue has already been reported/resolved.

- [X] I have read "[How to Debug Issues](https://doomemacs.org/d/how2debug)", and will use it to provide as much information about this issue as possible.

- [X] The issue can be reproduced on the **latest** available commit of Doom.

- [X] The issue can be reproduced on a stable release of Emacs, such as 27 or 28. *(Doom does not support development builds like 29+ or any version ending in .50 or .9x)*

### Expected behavior

When setting a new popup rule for compilation buffer, I wish for the buffer to display the same as opening compilation buffer and manually moving it to vertical split.
All normal here:
![image](https://user-images.githubusercontent.com/74069206/204777809-6386210d-a752-4014-a7f6-64fa6f9d7946.png)

### Current behavior

But actually, when setting `(set-popup-rule! "^\\*compilation\\*.*$" :side 'right :size 0.5 :slot -1 :modeline t)`, all text in compilation buffer sticks to the side.
![image](https://user-images.githubusercontent.com/74069206/204778191-6d27f0ef-5605-4778-bf31-5b361a6d0a9b.png)

Seems like some internal missing flag in the macro, I couldn't figure out which exactly.
Trying to manually trigger `fringe-mode` doesn't make a difference also. So not sure if it's actually fringe or something else.
A bit pedantic but could be annoying so filing a bug anyway..

### Steps to reproduce

Evaluate above macro call, try to compile anything.

### System Information

https://pastebin.com/bn33aRCD

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.