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

Unable to set different colors for nick modes in input_prompt and input_text in input bar #47

Closed
miggyb opened this Issue Apr 3, 2014 · 6 comments

Comments

Projects
None yet
3 participants
@miggyb
Copy link

miggyb commented Apr 3, 2014

Version: WeeChat 0.4.3 [compiled on Mar 14 2014 17:21:02]
OS: FreeBSD 9.2-RELEASE amd64

I'd like to have everything in the input bar dark gray, except for input text, which should use the default term color. It looks like this is not possible right now.

WeeChat doesn't allow you to choose a color for the nick/user mode displayed in the input bar. The only way to change it appears to be by changing the weechat.bar.input.color_fg option which changes the input_text color as well.

Screenshot showing problem here

There should be an option to change the color of nick modes in the client, in the same way you can change the colors for channel modes. Since the option for channel modes is irc.color.item_channel_modes, it looks like irc.color.item_nick_modes would be a reasonable name for this new option.

@flashcode

This comment has been minimized.

Copy link
Member

flashcode commented Apr 4, 2014

Hi,
Currently WeeChat does not use one color, but many colors for nick prefix (in input and chat), using the option: irc.color.nick_prefixes (which has a different color for op, voice, ...). But this option applies for both chat and input.
If you don't mind, you could disable the display of nick prefix in input, with command: /set irc.look.item_nick_prefix off.
So it's different from the option you mentioned (channel modes), which has only one color.
By the way, it's possible to create such bar item in a script, with a custom color.

@miggyb

This comment has been minimized.

Copy link
Author

miggyb commented Apr 4, 2014

Hello,

Actually, I didn't realize I had nick prefixes off, I turned them on again and yes, they're defined by irc.color.nick_prefixes. This is okay with me.

I'm talking about the user modes, however, like the (i) in my screenshot after miggyb

In one server and channel, for example, I have the following string in my input bar:

[@miggyb(irwxz)]

The user mode, irwxz, shows up as a color defined by weechat.bar.input.color_fg instead of having an option to set it differently. This makes it the same color as the input text in that bar. While scripting is certainly an option, it seems excessive for this situation, since there's already an option to change the color for channel modes via irc.color.item_channel_modes for the status bar.

@flashcode

This comment has been minimized.

Copy link
Member

flashcode commented Apr 4, 2014

Oh OK, I was wrong, you're looking to a color for nick modes.
I'll add such option then.

@miggyb

This comment has been minimized.

Copy link
Author

miggyb commented Apr 4, 2014

Thanks!

@FiXato

This comment has been minimized.

Copy link
Contributor

FiXato commented Apr 4, 2014

I still think that allowing the use of ${color} globally, as described in the old savannah ticket over at https://savannah.nongnu.org/task/?func=detailitem&item_id=12425, would be a cleaner solution. :)

@flashcode

This comment has been minimized.

Copy link
Member

flashcode commented Apr 4, 2014

@FiXato: yes I know, but adding such feature is not so easy, it would conflict with all color options for items, and some items have many colors used, not just one. So not easy, but I'm still thinking about how to implement such feature without breaking existing stuff.

@flashcode flashcode closed this in 982373f Apr 4, 2014

@flashcode flashcode added this to the 1.0 milestone Nov 16, 2014

@flashcode flashcode self-assigned this Nov 16, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.