You don’t have Parkinson and you probably don’t take that much coffee
Usual espresso from 42mm puck is 18g of coffee beans in, something around 40g of total coffee out. This has 90…150 mg of caffeine. The study focused on people having more than 300 mg daily.
So don’t drink more than 2 cups per day and you’ll be fine.
I drink 3 moka pots each morning and usually one in the afternoon. I don’t have Parkinson’s right now, but for all I know I am pre diagnosis…. I have been getting tingling feelings in my fingers lately
The result in the study is a few percentage points difference in the disease rating scale after 5 years, with relatively large variation in the underlying individual results.
The potential for there to be a mechanism that accelerates progression is a great thing to publish, but the data looks like it is in the "do you want to enjoy coffee for 5 years or go without to maybe avoid speeding it up a little bit" category.
If you use a trailing slash on the source it copies from the directory, if you omit the trailing slash it copies the directory itself. AFAIK this is pretty standard across POSIX tools
Indeed. This is one of the differences between the Unix and the MS/PC/DR-DOS command-line world. In the latter, recognizing empty final pathname components actually did become a way of differentiating such situations. I wrote a set of DOS and OS/2 tools in the 1990s, including COPY and MOVE commands, that had this very behaviour. I wasn't alone.
that's not a cp difference, cp is the granddaddy here
I think trailing / could be a nice way to indicate some meaningful difference, but since autocomplete always sticks it in, just feels like a bad idea to me. I might like it if directory names always had to have a trailing /, but I am less motivated by "convenience of common cases" and much more by "absolute precision/specificity/unambiguity" belt and suspenders.
(kind of unrelated but along the same lines, I toy with the idea of getting rid of . and .. visible in the filesystem, and make them only part of the syntax of paths. then you could have unambiguous multiple links to a directory: ".. is where you came from" and .. in the root is still the root, so chroot works too)
I am only amateur level with scheme but these are common to other scheme implementations. SRFIs are semi-standardized core libraries that work mostly the same in all implementations. I believe the record-type and records generally are one of these SRFIs, and it’s based on a chapter in SICP (several show up as sections of the book where students implement things that would be language feature in a larger env)
All the Lisp implementations seem to have pretty cryptic seeming errors, but it also seems to be very informative to those who know how to parse the call stack and how to expand/dig down in the built in debuggers. This is likely because of the same idea as those record-types, much of the language is built in the same lisp you’re running - so the error messages go a few levels lower level than you would expect. It’s not just a C syntax error type explanation, but rather you get some error about a bad call to a function you’ve never heard of running below that feature we normally associate with being a core function
The issue with Guile's stack traces is that they get truncated beyond I think 80 characters, and frequently leave out stack frames (usually your own functions). Geiser does have a debugger, but it does things differently based on implementation and Guile's specifically is a fancy one that I couldn't get to grips with. Not that I've tried that much, as I believe it's quite new.
There’s no in and out privileges to get ice elsewhere, so the organization coordinates huge ice shipments into the event. All the proceeds from the ice and coffee sales benefit the local schools and students, which is great because that area is doing pretty rough economically
I’ve been wanting to build one of these for awhile. Did you follow a plan/blog or design your own? I already have donor instax and Polaroid bodies not sure what to put it as a back on
reply