ByThePowerOfScience
ByThePowerOfScience
I did the thing I wanted to do by another means, but the global target would still be useful to removing the need for direct ASM usage.
> Can and should be fixed on your end, see [LoliKingdom/MixinBooter@095a6e0](https://github.com/LoliKingdom/MixinBooter/commit/095a6e0d90c887d4a6b75106199f36629b772e98) This isn't the only mod that uses this loader. Every mod that implements this itself has this issue, including...
The reason I made this PR is because the method those mods use was the only way to do it at the time, and while it is obviously outdated now...
Adding to this report: the message displays on ALL read-only files, even library source files inside ZIP archives.
I also forgot to mention, identical cells retrieved from the output side via shift-click are stacked. That's obviously not intended, but it is helpful when defragmenting your system.
Same issue. ``` java.lang.Throwable: IPC failed at com.intellij.openapi.diagnostic.Logger.error(Logger.java:370) at com.almightyalpaca.jetbrains.plugins.discord.plugin.rpc.connection.DiscordIpcConnection$connect$2.invokeSuspend(DiscordIpcConnection.kt:150) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:793) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:697) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:684) ``` IntelliJ IDEA 2023.2.5 (Ultimate Edition) Build #IU-232.10227.8,...
> Run IDEA as an administrator, it solved my problem I'm on Mac, so I guess I'll sudo it. But actually, I just realized that it wouldn't be too hard...
Wait, can you target entire _expressions_ for replacement in `subs`? If so, I should remove that check for a single variable on the lhs.
> I'm not sure how needed this is since `expr.subs(*eq.args)` or expr.subs(*solve(linear, sym, dict=True)`both work, where`eq`is an Equality and`linear`is an equation that is linear in`sym`. Considering that even when looking...
> > Besides, it's a nice convenience factor that doesn't add any overhead, so there's no reason not to imo. > > Unfortunately, I'm generally +0 for these changes because...