SuspiciousScript

I killed D, Hunter of the Dead thinking he was Darriwil. (I know.) I've searched the title question and found completely contradictory answers ranging from "No, none of them" to "only merchants" to "yes, any NPC." What's the correct answer?

I'm currently trying to do a bulk insert of many rows of new data into a set of tables with foreign key relations. (It's a tree-shaped dependency graph, nothing cyclical.) Right now I'm doing this with a query along these lines:

INSERT INTO example_table
VALUES
    ('example', 'data', 1),
    ('more_example', 'data', 2),
    ('even_more', 'example_data', 3),
    [...]

So on and so forth for a large number of rows. Ideally, I'd like to be able to do these inserts in any order (and simultaneously), and only check the foreign keys at the end of the transaction. So far, so good -- the foreign keys are all initially deferred. The problem is what happens when one of the r

According to this source, the reason why quasi- models don't report AIC scores is "because the R Core team (or at least the ones who wrote glm, glmmPQL, etc.) are purists and don’t believe that quasi- models should report a likelihood." I'm interested in understanding this from a theoretical perspective. Given that, to calculate an AIC, all you need is the model's likelihood function, why couldn't an AIC be calculated for a quasi-binomial model? Would the likelihood function not just be parameterized by your model's terms plus Phi?

You can find the link under the "Student" section of Minerva.

So the output I'm getting from swaymsg -t get_workspaces is really confusing me.

{
  "id": 14,
  "type": "workspace",
  "orientation": "horizontal",
  ...
  "rect": {
    "x": 12,
    "y": 42,
    "width": 1576,
    "height": 846
  },
  ...
  "window": null,
  "nodes": [
  ],
  "floating_nodes": [
  ],
  "focus": [
    21
  ],
  ...
},

There is a window open in this workspace -- presumably that the 21 in "focus". So why is "nodes" empty? I get the same result no matter how many windows I open in a workspace; "nodes" remains empty. What's going on?

Is there an elegant way to change the behaviour of <CR>/return while in nvim-telescope buffers to select the highlighted item (i.e. do what return does in normal mode)? I find it kind of clunky to have to exit insert mode just to select the line I want to jump to, for example. I'm sure this could be done in a clunky way via an expression binding, but I'm hoping for a more elegant solution.

I tried via both Homebrew and direct download, and I'm getting roughly 300Kb/s. I'm trying to download the Mac installer from central Canada.

Hi all,

I'm quite confused by the signature of the registerrpc function. A couple parts stick out:

• char *(*procname)(char *): Okay, a pointer to a function that takes one character pointer as an argument and returns a character. Of course, this can't be the signature of every function, so my hunch is that char * is being used as some kind of poor substitute for a void pointer -- but I don't know if this is correct.

• xdrproc_t inproc: I would think this would be a procedure along the lines of xdr_int, but when I pass that as the inproc argument, my function just recieves garbage.

I've tried doing it the way described in this video without any luck. The caps lock button doesn't start to flash faster after being pressed, unlike when I press one of the regular keys.

Need to get that paper.

Hi all,

So I'm working on an emulator of the Space Invaders arcade game for the Intel 8080 processor, and occasionally consulting this tutorial along the way. It mentions a "RAM mirror" at addresses above 0x4000, which I assume to mean a mirror image of the contents in addresses 0x2000–0x3FFF. The tutorial cites this page, however, there's no mention of anything like this in the Intel 8080 Programmers Manual. I'm also a little weary because there are a number of error

I recently (mostly) finished up a Chip 8 emulator, which was my first foray into emulator development. For the main instruction reading loop, I used GCC's computed gotos to do something akin to direct threading, just with an extra level of indirection. (I used the opcodes' leading nibbles to index an array of label addresses.) While this worked really well for Chip 8 and was actually quite easy to work with, I have trouble imagining how it would scale to larger instruction sets, like that of the Intel 8080. What is your preferred technique for interpreting instructions?