Re: [9front] Libaml does not recognize opcode 0x86

[Lucas Francesco <lucas.francesco93@gmail.com>]

This bug report is wrong and your communication skills suck. libaml
does RECOGNIZE opcode 0x86 (NotifyOP, I recommend you to check up
Onotify in optab[]), and that's generally unrelated to battery
handling AFAIK, you may be referring to DefNotify, which is defined
as:  "DefNotify := NotifyOp NotifyObject NotifyValue". There's no
documented need for DefNotify and nobody would implement it because of
some random person just pointing at it without even bringing up an
actual bug.


On Tue, 24 Oct 2023 at 00:54, Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:
>
> On 10/23/23 23:37, Kurt H Maier wrote:
> > On Mon, Oct 23, 2023 at 11:32:20PM -0400, Blue-Maned_Hawk wrote:
> >>> I seen't how that justifies of the problem itself caring, of which to
> >> which your statement in reference to was.
> >
> > You're an idiot, then.
> Rude.
> >                         If your machine is worth supporting, people will
> > care.
> This problem'sn't unique particularly to this machine.  'Tis of the lib.
>   'Tis general.
> >        Sysinfo output is the easiest way to make that determination.
> > Once again, you're not qualified to identify which information is
> > relevant.
> >
> If of this so certain you're, explain why should also you be, no?
> >> If you, as an english speaker, can parse that sentence, it is a valid
> >> english sentence.  Back on topic, that does not clarify.
> >
> > Plenty of valid English sentences are shit.  Most of yours have been.
> >
> 'Tisn't but m'dialect, man.
> >> Ah, i see what you're trying to do there now.  You're not going to succeed
> >> in it.
> >
> > I strongly recommend you return any stolen property as quickly as
> > possible.
> I plead the fifth.