JATtho

joined 2 years ago
[–] JATtho@lemmy.world 1 points 1 week ago

Two new hobbies to keep me in the reality^tm^.

for the twistedIt's just art and music. Plus a likely revival of old skill.

[–] JATtho@lemmy.world 4 points 2 weeks ago

So this is it. The enshittification has reached slowlorris levels.

[–] JATtho@lemmy.world 2 points 2 weeks ago

I spent solid 10min writing an useful answer and then looked up. Now I want my 10mins back.

hintJust wipe the screen clear from the goo, dummy.

[–] JATtho@lemmy.world 6 points 2 weeks ago

Oh, this is a good one.

[–] JATtho@lemmy.world 5 points 4 weeks ago (1 children)

No mention of KDevelop? ;__;

I like it because it is the pretty much only FOSS graphical IDE where the edit-compile-debug cycle works. I'm been using it for last 10y for C/C++/Python, and it recently gained LSP support. (ported from Kate)

[–] JATtho@lemmy.world 2 points 4 weeks ago

The \EFI\BOOT\BOOTX64.EFI is the only file the UEFI standard says it is required automatically lookup from an EFI system partition. There can many EFI partitions but the UEFI is only required to find a single file per such a partition.

efibootmgr -u can show all bios auto created boot entries (don't touch those, the bios can/will reset them at whim) and the manually created entries that don't launch a BOOTX64.EFI named file.

[–] JATtho@lemmy.world 5 points 1 month ago (2 children)

I intended this an sarcastic example; I think it's worse than putting the main outside of the branch because of the extra indent-level. It does have an upside that the main() doesn't exist if you try import this as an module.

[–] JATtho@lemmy.world 1 points 1 month ago* (last edited 1 month ago)

Btw, ld.so is a symlink to ld-linux-x86-64.so.2 at least on my system. It is an statically linked executable. The ld.so is, in simpler words, an interpreter for the ELF format and you can run it:

ld.so --help

Entry point address: 0x1d780

Which seems to be contained in the only executable ~~section~~ segment of ld.so

LOAD 0x0000000000001000 0x0000000000001000 0x0000000000001000
     0x0000000000028bb5 0x0000000000028bb5  R E    0x1000

Edit: My understanding of this quite shallow; the above is a segment that in this case contains the entirety of the .text section.

[–] JATtho@lemmy.world 18 points 1 month ago (4 children)

I would put my code in a def main(), so that the local names don't escape into the module scope:

if __name__ == '__main__':
    def main():
        print('/s')
    main()

(I didn't see this one yet here.)

[–] JATtho@lemmy.world 4 points 1 month ago

I do this, and I have a "graveyard log" file where I paste my discarded posts and replies.

[–] JATtho@lemmy.world 2 points 2 months ago

Holy hell, thats rough. :D

[–] JATtho@lemmy.world 2 points 2 months ago

True Arch: you write the image to the usb stick yourself, boot it on bare hardware, and don't use archinstall. This is the minimum requirement BTW. If you use archinstall you can only use "btw" in lowercase. /s

 

Me 2023: It will take only a few weeks, right? RIGHT?

A year later: I re-wrote the entire damm plugin. Have a good day.

 

A greentext moment:

Decide to listen sweet sweet psytrance.

Playlist only available on Spotify.

Don't like non-free software. (a fucking 1TB disk full of free)

Try make the account anyway.

Somebody else has registered your email.

Request to recover password.

The request arrived at my mail box. Freaking out. No memory of why, when or how.

Listening sweet sweet psytrance.

(Still freaking out.)

view more: next ›