You are not logged in.
Hello,
Since I updated my system today (some minutes ago), whenever I start bash (login on tty, terminal emulator) it prompts me this warning:
Warning: top-level configuration of `color` is deprecated. Configure color use under `ui`. See documentation for more info.
It doesn't seem harmful at all but it quite annoys me since I have no idea where it comes from. Can anybody help me find out where it comes from?
Thank you guys
Last edited by kaslusimoes (2015-04-10 19:03:18)
Offline
can you post your bashrc so we can take a look ?
Offline
This is happening to me to. Here's a link to my dotfiles (including bashrc):
https://github.com/jdahm/dotfiles
I'm not doing much with color except a few escape sequences for the prompt and standard dircolors. This seems to happen in every terminal, so it's probably indeed a bash issue.
Thanks for taking a look.
Offline
Do both of you use beets?
The colors used in the terminal interface are now configurable via the new config option colors, nested under the option ui. (Also, the color config option has been moved from top-level to under ui. Beets will respect the old color setting, but will warn the user with a deprecation message.)
https://github.com/sampsyo/beets/releases
The color option was previously a top-level configuration. This is still respected, but a deprecation message will be shown until your top-level color configuration has been nested under ui.
...
ui:
color: yes
colors:
text_success: green
text_warning: yellow
text_error: red
text_highlight: red
text_highlight_minor: lightgray
action_default: turquoise
action: blue
Offline
@coyote3007: It happens even when my .bashrc script isn't loaded (I have separate .bashrc and .bash_profile files, with the second one just loading Xorg when I'm logged on tty1)
@SirMyztiq: Yes, I do happen to use beets! This is exactly what I needed. Thank you very much
Offline
Wouldn't it be better to show the message when starting beets instead of every time a new bash session is started? How can this be intended behaviour?
Offline
@pulp: Indeed it would've been better. It got me crazy since I couldn't know where it came from! I don't even autostart beets nor anything similar for it to warn me out of nowhere. Gladly here an Arch community there is always someone aware of these changes willing to help
Offline
FYI, this was caused by automatic sourcing of "beet completion" upon every new shell, introduced there: https://projects.archlinux.org/svntogit … 75d0ef4083
It has now been removed. The issue is currently being discussed there: https://github.com/sampsyo/beets/issues/1414
Offline
Thank you for the feedback @Laugarhraun
Offline
Hello,
Since I updated my system today (some minutes ago), whenever I start bash (login on tty, terminal emulator) it prompts me this warning:Warning: top-level configuration of `color` is deprecated. Configure color use under `ui`. See documentation for more info.
It doesn't seem harmful at all but it quite annoys me since I have no idea where it comes from. Can anybody help me find out where it comes from?
Thank you guys
Hey, sorry about that. I didn't experience this behavior, bash didn't throw any warnings when I enabled beet completion so I thought I was good to go. I just got a tip on how to only load the completion when one asks for it and built a new package [1], bash shouldn't print this every time you load a shell (in any case, you should probably fix your configuration to not trigger that message). Could you please test it and check if it works for you?
[1] http://pkgbuild.com/~alucryd/beets-1.3. … pkg.tar.xz
Last edited by Alucryd (2015-04-14 07:44:15)
The bird of Hermes is my name, eating my wings to make me tame.
Offline
@Alucryd: It seems fine both with the deprecated syntax on the config file and with the corrected one
Offline
Thx for testing, just pushed it in [community].
The bird of Hermes is my name, eating my wings to make me tame.
Offline