On April 12, 2016 06:47:12 AM Dan MacDonald wrote: > You ask us to erase out config for other, non colour-related changes, right > Tim? Changing colour schemes won't require nuking your config I'd hope!
Should have been clearer on that: You don't need to erase your config if you had not pulled the FIRST of the two commits from yesterday. Simply pull and build. Only erase your config if you had pulled the FIRST commit and now you want to pull the second commit with the newer colours. Then you need to do it because the previous colours would have already been written and now you need the newer colours. > I'm probably v.slow on this one but it was only in the last couple of weeks > I noticed your name is a (highly apt) anagram of realtime :) Yep. I've had to explain it to a few friends ;-) Thanks. Tim. > > On Tue, Apr 12, 2016 at 3:02 AM, Tim E. Real <[email protected]> wrote: > > Hi again. > > > > OK Here's my take on a default colour scheme. > > > > Please erase your ~/.config/MusE.cfg to start from scratch, > > > > to see the proper new starting configuration. > > > > I know, colour everywhere. Meh, well it's just one scheme ;-) > > > > As I say, share your custom colours if you like. > > > > Cheers. > > Tim. > > > > ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
