« first day (2493 days earlier)      last day (2509 days later) » 

3:38 AM
New close reason added:
14
Q: New "No Research" close reason?

TetsujinFrom some brief comments in AD Chat, it appears we currently have one spare slot for a new close reason. I would like to propose a 'zero research' type reason - though I'm open to suggestions on the precise wording. grgarside mentioned that he already has a standard comment he uses for 'no rese...

 
 
5 hours later…
8:11 AM
@bmike That's great! I think it's a good way deal with a lot of the questions we get here. :)
 
8:29 AM
@grgarside Hey, thanks for answering the question on JXA.
I am just wetting my feet here, could you recommend some resources I could look into for javascript automation?
 
8:44 AM
@Vinny Hi, I answered the question purely using my knowledge of JavaScript rather than anything specific to JXA. Are you familiar with JavaScript and looking for JXA resources, or would JavaScript resources be a priority first?
 
9:17 AM
@ grgarside Hey. I am learning Javascript on Codacademy right now. JXA doesn't seem to have much resources
 
9:48 AM
@Monomeeth thank @patrix too as he did most of the work to get it ready to roll
 
10:12 AM
@bmike Ah, well, I was thanking both of you really! :) Thanks @patrix for your efforts, and thanks @Tetsujin for initiating the conversation on Meta. Good job everyone! :)
 
Agreed. I’m grateful for your moderation duties here and @Tetsujin and George and a few others that really keep this place improving.
2
 
 
7 hours later…
5:07 PM
Nice one chaps :)
Do we need to add the defining 'this is what we did' answer so there's one that can get the shiny tick-mark, or is it good enough as it stands?
Ugh - what do we do with this situation? apple.stackexchange.com/questions/286939/…
tbh, the new close-hammer ability still surprises me when it happens.
 
5:23 PM
hmm.. forget that, he binned the dupe & added to the original as a comment :/
 
 
1 hour later…
6:52 PM
Hi @grgarside! In this question apple.stackexchange.com/questions/203082/… , you suggested to run killall with these options: -HUP, could you please tell me what these options do? the man page for killall doesn't provide the answer. (I'm just being genuinely curious)
 
@Tetsujin Close as a duplicate and add a comment, as you did
 
@patrix fantastic! thank you
 
@Vinny Apologies for the delay (the space between the at and the username breaks the ping), here's a few resources I use:
@AntonK The link from patrix is spot on, but referring specifically to the Dock process, -HUP should cause a restart of the process. The launch daemon responsible for the Dock should restart the process anyway, so including -HUP is not required, but this took a while in older versions of macOS. That answer is quite old, feel free to omit nowadays.
@Tetsujin It's only taken 3 years! /s
Aug 29 '14 at 20:17, by George Garside
> Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results.
:38141768 Just fyi, you can edit your last comment immediately by pressing the up key, or by clicking the arrow on the left of the message and choosing edit.
 
7:24 PM
@grgarside thank you! I was using killall without any flags, and when I saw your answer, I thought I was missing out on something the whole time. Thank you again!
 

« first day (2493 days earlier)      last day (2509 days later) »