Suggestion: make unsupported functionality no-op about crossterm

[TimonPost]

Hello, thanks for the feedback. It is the right behaviour that it does not work for windows. Windows does not support bold / itlalic ... font. I agree that it can be frustrating to change the code for diffrent plarforms.
I'll take it in consideration but am not sure if I should leave the calls empty for windows because than user may think that the function call does not work. And how should I tell the users that these function calls are not working for windows. Maybe I can do it with the commend above the function call or an custom attribute.

If you want to use the bold feature for only unix why not do the folowing:

``

#[cfg(unix)]
  println!("{}", paint("Bold text").bold());

#[cfg(windows)]
  println!("{}", paint("Bold text"));

With this sollution only the unix systems are going to use the bold() call. I will think about it, I'll let you know when I have made an choice.

[Rukenshia]

Yeah that's what I'll do I guess, thanks for the suggestion. A bit weird to have two calls everywhere but that sounds like a reasonable trade-off as I also understand the other PoV.
Thanks!

[TimonPost]

That is the normal way of doing it in rust, it is weird I agree to have two calls. And my crate is handling most of the crossplatform operations on the background. I should defenately find another way. of doing this. Also you can use an if stament to check on witch platform you are working. Check this for more info. It seems more nice if you use that in your code to my opinion. The nice thing about using attribute is that if you compile your code for unix/linux than all the code that has an cfg[windows] attribute will not be compiled, and the other way arrount.