overview for orsetto

Data save rule by orsetto in c/196

[-] orsetto@lemmy.dbzer0.com 15 points 7 hours ago

This topic has been pinned, so it's probably important

72

Reject vim return to emacs (lemmy.dbzer0.com)

submitted 2 months ago by orsetto@lemmy.dbzer0.com to c/linuxmemes@lemmy.world

14 comments fedilink

If you have typed an <ESC> by mistake, you can get rid of it with a C-g.

quoting the emacs tutorial. made me giggle

Asking for donations in Plasma by orsetto in c/linux@lemmy.ml

[-] orsetto@lemmy.dbzer0.com 32 points 2 months ago

Not an ad. No one is trying to sell you anything.

(If you get the notification) you're already using their product.

How to create a bootable Linux USB drive by orsetto in c/linux@lemmy.ml

[-] orsetto@lemmy.dbzer0.com 9 points 6 months ago

I don't remember where, but i read that this method only works because linux distributors "abuse" the ISO format to allow this. If I remember right, it's not possible to use this ISOs on regular disks

Of course the command you provided is right and it's what I use, it's just a fun fact

Linux error starter pack by orsetto in c/linuxmemes@lemmy.world

[-] orsetto@lemmy.dbzer0.com 131 points 7 months ago

I'd like to add this one:

Uhhuh. NMI received for unknown reason 31 on CPU 3.
Dazed and confused, but trying to continue

I get this one like once a week and it always makes me laugh. One day I'll investigate

What is the /opt directory? by orsetto in c/linux@lemmy.ml

[-] orsetto@lemmy.dbzer0.com 12 points 8 months ago

I think it refers to applications that do not respect the standard directories like /usr/bin, /usr/share/man, /etc

acab rule by orsetto in c/196

[-] orsetto@lemmy.dbzer0.com 39 points 9 months ago

That's what a fed in your position would say.

People who can don't get mad and just go with the flow, how do you do it? by orsetto in c/asklemmy@lemmy.ml

[-] orsetto@lemmy.dbzer0.com 99 points 10 months ago

Happened to me too. Best thing is going to therapy.

This might be caused by bigger problems with your family or work. Or it might just be accumulated stress unrelated to anything in particular.

Therapy helps either way

10

Node.js segmentation fault does not happen on different envirnment (lemmy.dbzer0.com)

submitted 10 months ago* (last edited 10 months ago) by orsetto@lemmy.dbzer0.com to c/programming@programming.dev

4 comments fedilink

Hi. I'm working on a project that compiles Rust code to WASM, and uses WASI in Node.js to execute it. After some development, I encountered a segmentation fault happening in the wasi.start() function. Considering that I'm kinda new to Node I was only able to understand that it was happening after the call to the exported WASM method returned.

This happened almost two months ago, and while I thought about reporting this to the node devs (WASI's also experimental), I was going to move soon and a lot has gone on.

Yesterday I tried to reproduce the bug on my laptop (that is not my usual development environment, which I don't have access to right now) but I wasn't able to.

I had to start fresh and install all the necessary tools from zero, so my theory is that there was something wrong in the previous environment. I'm also on Gentoo now, while I was running Arch previously.

Unfortunately I don't have the means to check on other environments. I tried to reproduce the old environment, installing the same versions of node and rust, with no luck. I also tested this with the latest versions and everything works fine.

This situation is upsetting. I don't know what's changed that caused the problem to "disappear", so i feel uncomfortable considering this solved. What would be the best approach in this situation?

EDIT: I also just tested it on Debian live, and I still wasn't able to reproduce the segfault

Aint no Tolerance Paradox round here by orsetto in c/memes@lemmy.ml