Console:
here here 2 here 3 here 4 here 4a here 4bMe:
Haha! I got you!
ah yes, counting from 2, because as everyone knows “” is one
You put in that first “here” thinking it’ll be the only one.
that’s always how it is.
And eventually it becomes second nature. lol
background: red; goes harder imo
background: #f0f
Me: “Is
buggera term that denotes a bugged state?
Senior: “No. That’s just what I have it print to show if something has failed.”I like to call pair-programming sessions (for bugs) “bebuggery sessions” at work and people haven’t complained yet.
Printing Butt is fun and all, but if I’m at the point of logging nonsense, it is usually a stronger word.
Often we use
outline : red 1px solid;, that’s clean!
i’m more of a
background-color:red;guy myselfMy problem is that I do
red,blue,greenthen can’t think of any more clearly visible colours.I often use magenta, pink, cyan and purple, too
Purple, yellow, pink, light blue, …
Damn, this looks handy. Thanks for sharing
My pleasure! Though I’m gonna be honest, I mostly use console.debug(). 😇
Wow, and here I was trying to set breakpoints using the devtools debugger and faffing around with sourcemaps.
Wish I knew about this 10 years ago!
Is it too late?! Are you still webdevvving? 😃
when doing headless shell scripting i debug with
notify-sendi3wm having urgency cues was the single greatest thing any DE/WM has ever done.
Could you please point me to docs about this or keywords i should search with? This sounds interesting, but a quick search with i3 and urgency cues gave me nothing.
i believe they’re referred to in documentation as “urgency hints” it should be in the user guide. heres the guide just do a ctrl f for urgency, it should pop some stuff up. It’s also a default config option for the base file.
Thank you, i’ll take a look!
the user guide while rather terse and not verbose, is still incredibly detailed, and often includes a good bit of information to get you where you need to be.
deleted by creator
