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)
I mean no harm.
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)
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.
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.
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.)
I spent solid 10min writing an useful answer and then looked up. Now I want my 10mins back.
hint
Just wipe the screen clear from the goo, dummy.