00:00:07 <Eksell> Unstable branch on CRAWL.XTAHUA.COM updated to: 0.22-a0-252-gcace5d2 (34)
00:56:51 -!- amalloy_ is now known as amalloy
02:00:10 -!- KittyTac_ is now known as KittyTac
03:11:56 <Rotatell> Unstable branch on crawl.beRotato.org updated to: 0.22-a0-252-gcace5d2 (34)
05:39:43 -!- amalloy is now known as amalloy_
07:24:09 -!- Dracunos_ is now known as Dracunos
12:55:09 <shmup> any gnu make wizards around?
12:55:17 <shmup> this is going to be completely off topic for this chan heh
12:57:01 <|amethyst> I see you're in ##workingset; no help there?
12:57:13 <shmup> nah crickets but i'm being impatient as heck
12:57:22 <|amethyst> I'm not a GNU make wizard by any means, but might as well ask
12:57:23 <shmup> it's only been ~10 minutes since i asked heh
12:57:33 <shmup> ok so...
12:57:42 <shmup> http://ix.io/R1q/make
12:58:09 <shmup> it is my understanding, based on line 16/17, that the package.json and yarn.lock are prereqs, and make will check their modification time and if it's newer.. it will run `yarn install`
12:58:18 <shmup> except, it is _always_ running yarn install. that's the problem :)
12:59:20 <shmup> (package.json and yarn.lock are certainly untouched for a while now, i verified it's not actually updating them every time yarn install is ran)
12:59:51 <|amethyst> is node_modules's modification timestamp actually changing?
13:00:07 <|amethyst> since it's a directory, that would only happen if something is being created/deleted *directly* beneath it
13:00:58 <shmup> http://ix.io/R2n
13:01:04 <shmup> not that i couldn't have just said "nah it's not" heh
13:02:24 <|amethyst> well, there's your problem
13:02:38 <|amethyst> you'll need to find some file that you know yarn install will touch
13:02:48 <shmup> oh, huh. i wonder if it's because.. okay.. sec.
13:03:06 <shmup> ok. removing node_modules and doing a make fixed it.
13:03:16 <shmup> i see that by running yarn install myself, originally, caused this problem.
13:03:26 <|amethyst> well
13:03:45 <|amethyst> that made it work once
13:04:02 <|amethyst> well, twice probably
13:04:18 <shmup> hm. so if i modify package.json it should work, but only one more time right?
13:04:29 <|amethyst> well, modifying it will work either way
13:05:13 <shmup> heh, ok.. it's running every time again.
13:06:06 <|amethyst> right, because you're saying "run this if the inputs are newer than this directory"
13:06:18 <|amethyst> and the directory isn't getting any newer when you run the rule
13:06:37 <shmup> yeah that does make total sense
13:06:38 <|amethyst> probably there is some file beneath the directory that is touched every time you do yarn install
13:06:48 <|amethyst> so you'd use that as the target, rather than node_modules
13:07:21 <|amethyst> or
13:07:21 <|amethyst> you have the rule do that
13:07:28 <|amethyst> ran_yarn_install: package.json yarn.lock
13:07:36 <|amethyst> yarn install
13:07:42 <|amethyst> touch ran_yarn_install
13:07:57 <|amethyst> so now you have a file that indicates the last time you executed that rule
13:08:05 <|amethyst> and that file is your target
13:08:15 <shmup> yeah, that might be the only way to go? there isn't anything being modified in node_modules on a yarn install, when there is nothing to do
13:08:27 <shmup> i don't like that i'm _adding_ elements like the touched file, but might be the only way right now
13:08:31 <shmup> maybe a lightbulb will go off
13:08:52 <|amethyst> hm
13:08:53 <|amethyst> well
13:08:57 <|amethyst> you could touch the directory :)
13:09:05 <|amethyst> then the directory itself is your timestamp file
13:09:05 <shmup> lol
13:09:53 <|amethyst> I'm not even sure that is a hack
13:09:56 <shmup> wow
13:10:02 <shmup> that is perfect..
13:10:51 <|amethyst> now, that does mean that if you modify the directory by hand, make will think it's up-to-date
13:11:31 <shmup> i'm okay with that, i think? you should never be doing that, so..
13:11:36 <|amethyst> so you'd have to be sure to touch the .json or .lock file if you do something manual to the dir
13:11:39 <|amethyst> yeah
13:11:51 <|amethyst> it's not much different from touching an executable directly
13:12:01 <|amethyst> the only difference is that it's a little easier to do that to a directory
13:12:39 <shmup> so this got a lot of attention right: https://news.ycombinator.com/item?id=16483889  within his blog post he links a gist that i boiled down/removed like one thing (he uses flow) and here's where i'm at.
13:12:51 <shmup> i'm curious if his too doesn't run `yarn install` everytime. i asked in the gist, appending an edit with your suggestion. curious what he'll reply with
13:13:29 <|amethyst> Sorry, I've disabled "JavaScript" in my browser
13:13:37 <|amethyst> Not the language, just the word
13:13:42 <|amethyst> /s
13:14:18 <shmup> haha, no /s needed, I know you assist on webtiles :P
13:14:44 <|amethyst> I still know nothing of the javascript ecosystem
13:14:48 <|amethyst> or very little
13:15:19 <|amethyst> "web" is one of those words where if you add it in front of "programmer", you take a pay cut :P
13:15:31 <|amethyst> (not that I get paid to be a programmer, or would want to)
13:15:54 <shmup> haha, yeah.. in hindsight i should have explored other options and just programmed as a hobby
13:16:17 <shmup> i just rotated from "full stack" to "frontend engineer" and the only reason i didn't see a paycut is i finally snagged a remote gig in nyc
13:17:14 <|amethyst> I probably have taken a paycut over what I could have been making as a programmer with 15 or whatever years of professional experience
13:17:58 <shmup> you're probably still doing fine, past a certain point it's whatever unless you're just mega greedy
13:19:24 <|amethyst> oh, yeah, I'm still doing well for myself, particularly since I live in a low-cost-of-living part of the US
13:20:29 <|amethyst> (and don't have kids)
13:20:55 <shmup> same and same!
13:42:22 -!- amalloy_ is now known as amalloy
16:07:52 <KamiKatze> !burn
16:07:53 <KamiKatze> ??burn
16:07:54 <Sequell> burn ~ turn[1/1]: different arbitrary unit of not-time
16:08:30 <KamiKatze> ??burn spellbooks
16:08:31 <Sequell> burn books[1/3]: Trog invocation that gives piety (2) and creates a cloud of flame. Each book in LOS extends the duration of the clouds. Won't burn manuals.
16:08:49 <KamiKatze> ??burn spellbooks[2
16:08:49 <Sequell> burn books[2/3]: Useful for blocking off corridors (like Conjure Flame), but also for actively hurting monsters while you fight them in melee, as books can be burned even if monsters are standing on them.
16:09:01 <KamiKatze> ??burn spellbooks[3
16:09:01 <Sequell> burn books[3/3]: Don't forget that you can throw a book then ignite it, not just drop it. Saves precious turns!
16:09:37 <KamiKatze> hmm... will the damage will increased if I staple books in one tile?
16:11:05 <amalloy> ??flame cloud
16:11:05 <Sequell> clouds[1/7]: Flame, freezing vapour, mephitic ({mephitic cloud}; AKA noxious fumes or stinking), poison, black/grey/purple/blue smoke, steam, foul pestilence ({miasma}), mist (swamp water), and occasionally bugginess. Of these, the smokes and mist are harmless, and they plus steam can block LOS as per {scroll of fog}. Also, there's the {book of clouds}.
16:11:34 <amalloy> ??clouds[2
16:11:34 <Sequell> cloud damage[1/2]: fire/forest fire/cold/holy flames/acid/negative energy: 10-32 dam if player, 6-21 dam if monster. ghostly flame: 4-18 dam. rain: 0-9 dam if 'fiery'. meph: 0-3 dam. poison: 0-10 dam. miasma: 0-12 dam. storm: 40-131 dam if player, 24-87 dam if monster. Average of 3 rolls (excp. poison/miasma/rain), Apply resistance, then apply AC, then multiply by auts/10 spent.
16:12:14 <amalloy> KamiKatze: notably, burning books does no more than create a flame cloud, and all flame clouds are indistinguishable
16:12:41 <KamiKatze> check. somehow it makes sense.
16:45:16 <gammafunk> do forest fires have their own cloud type?
16:45:20 <gammafunk> I seem to recall that being the case
16:47:55 <amalloy> they are different somehow, yeah. not sure if that difference is "a tree tile with a fire on it" or "a special cloud indicating a tree is on fire here"
16:48:09 <amalloy> otherwise using cloud of flame near a tree could start a forest fire
16:49:10 <gammafunk> I want to say it was done through the cloud type
16:50:22 <gammafunk> my guess is it's not "special cloud indicating a tree is on fire here" but just "a special cloud that ignites trees that are adjacent to it"
16:51:05 <gammafunk> so it starts from a tree but can spread to tiles where there aren't trees, maybe it also spreads
17:12:33 -!- gresshopper is now known as gressup
18:20:36 <aidanh> yeah, that's correct; there's a special cloud type for spreading flames
20:29:41 -!- amalloy is now known as amalloy_
20:44:54 -!- KittyTac is now known as KittyTac|Away
20:47:09 -!- amalloy_ is now known as amalloy
21:05:07 -!- KittyTac|Away is now known as KittyTac
22:12:51 <gammafunk> aidanh: I think I found another weird redraw bug
22:13:03 <gammafunk> not sure if this is related to heavenly storm
22:13:22 <gammafunk> but if I do ctrl-x and hit the hotkey for the stairs in LOS
22:14:56 <gammafunk> then the cursor seems to move the position and it seems I'm back in the LOS with x-v targeting
22:15:01 <gammafunk> but the screen hasn't redrawn
22:15:08 <gammafunk> it still shows the ctrl-x list
23:35:53 <aidanh> gammafunk: this is on master? I can't reproduce this
23:37:40 <aidanh> ctrl-x, stair hotkey switches to x-mode with the cursor on the stairs, but I don't see any redraw issues
23:39:05 <aidanh> oh, it's console only