Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: Tag buffer CSS class with buffer name to allow users ability to customize buffer list #1194

Open
khaytsus opened this issue Jun 22, 2021 · 1 comment

Comments

@khaytsus
Copy link

khaytsus commented Jun 22, 2021

In #891 there's a request to hide buffers and it was hinted maybe buffers could have a CSS attribute attached and the user could handle this on their own in CSS.

I could even see users customizing the list to highlight certain buffers differently, but for me primarily to hide server buffers. I currently don't see anything in the CSS that I know how to hide but it's always possible I'm missing something.

Currently the buffer li elements are just li class="buffer" .... but if it were something like like class="buffer irc.servername.#channelname" this custom CSS could hide it.

.irc-servername-#channelname {
display: none !important;
}

Note: the github issue is hiding it for some reason, but the # above has to be escaped with backslash.

@khaytsus
Copy link
Author

With some IRC help, I was able to solve my primary reason for wanting this; hiding server buffers. But if anyone wants to do channel-specific CSS I still think adding the channel buffer name as a class would be useful.

Here's what I did to hide server buffers:

Hides all buffers

.buffer { display: none !important; }

Un-hides channel buffers

.buffer.channel { display: block !important; }

Un-hides the private buffers

.buffer.private { display: block !important; }

And the indent class was originally suggested, channel and private seem more intuitive

.buffer.indent { display: block !important;}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant