You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Italic, bold, and underlined keywords will still trigger their associated factoids (the entire response is formatted like the trigger), but colored keywords do not.
My hunch was that the control characters are stripped out and saved for use when outputting the tidbit, but the foreground color digits (and optional comma + background color digits) following the color control characters are not saved. So when Bucket reuses the color control characters, they end up being "no color" (^C without a color following it resets to default).
Testing revealed that Bucket is indeed stripping out the color control character (\x03) but it is not reused when sending the tidbit. However, the fact is matched including the color control digits, and it probably should not be. (I added an alias from 05test to test in my instance after sending \x0305test, or "test" in maroon/brown, failed to trigger test; it did trigger the alias.)
The fix for this is removing the specified color digits following the control character when control codes are stripped out.
The text was updated successfully, but these errors were encountered:
Italic, bold, and underlined keywords will still trigger their associated
factoids (the entire response is formatted like the trigger), but colored
keywords do not.
My hunch was that the control characters are stripped out and saved for
use when outputting the tidbit, but the foreground color digits (and
optional comma + background color digits) following the color control
characters are not saved. So when Bucket reuses the color control
characters, they end up being "no color" (^C without a color following it
resets to default).
Testing revealed that Bucket is indeed stripping out the color control
character (\x03) but it is not reused when sending the tidbit. However,
the fact is matched including the color control digits, and it probably
should not be. (I added an alias from 05test to test in my instance after
sending \x0305test, or "test" in maroon/brown, failed to trigger test; it
did trigger the alias.)
The fix for this is removing the specified color digits following the
control character when control codes are stripped out.
Italic, bold, and underlined keywords will still trigger their associated factoids (the entire response is formatted like the trigger), but colored keywords do not.
My hunch was that the control characters are stripped out and saved for use when outputting the tidbit, but the foreground color digits (and optional comma + background color digits) following the color control characters are not saved. So when Bucket reuses the color control characters, they end up being "no color" (
^C
without a color following it resets to default).Testing revealed that Bucket is indeed stripping out the color control character (
\x03
) but it is not reused when sending the tidbit. However, the fact is matched including the color control digits, and it probably should not be. (I added an alias from05test
totest
in my instance after sending\x0305test
, or "test" in maroon/brown, failed to triggertest
; it did trigger the alias.)The fix for this is removing the specified color digits following the control character when control codes are stripped out.
The text was updated successfully, but these errors were encountered: