Keir Starmer set to reject EU overtures to join revamped bloc as 'non-starter'
palordrolap @ palordrolap @kbin.social Posts 0Comments 434Joined 2 yr. ago
palordrolap @ palordrolap @kbin.social
Posts
0
Comments
434
Joined
2 yr. ago
Centauri Prime probably.
Then you feed {12,12,12} to the API and it turns it into 1970-01-01T12:12:12UTC
Those of us for whom CBT didn't work, are glad for those it did.
And if you've only ever been on the supply side, I'd say that I'd like to see your opinion once you've been through whatever it is that causes the need for it in the first place, but I wouldn't wish that on anyone.
"Didn't work" is a gross oversimplification of course. Helpful techniques can be learned, but CBT is not the cure-all some people think it is.
Yeah, I was thinking of old 8-bit computers that did the same ignore-after-second-char thing. Most people didn't bother typing the extra characters though because 1) those characters took up valuable memory and 2) if you accidentally put a keyword in the middle of your longer name, the tokeniser would see it and assume it was a keyword.
e.g. Calling your variable FORGET seemed like a good idea until you got a syntax error because FOR and GET are both keywords. FO it is, then. Or just F.
COLOR was cursed too; OR is usually a keyword, even if COLOR itself isn't. British English COLOUR might save you here, but you're still losing those four extra bytes.
I was mostly poking (heh) fun at myself, (also) a member of the generation I spoke about. Very much not a professional, but I do code a little, and know about the non-triviality of naming things.
Also also, for reasons I won't go into, my phone is still a flip phone.
U nd to rembr tht mny snr devs grw up prgrmng on old hrdwr tht ddn't hv mch mmry & oftn th lang ony allwd shrt var nms anywy. Also thy wr th gen of txtspk fr smlr rsns.
Yngr snr devs pckd up bd hbts frm tht gen.
And here's a sentence that's not squashed to cleanse your palettes / give a sigh of relief because I figure if I need a break from typing like that, you need a break from reading it.
Nmng thngs s hrd.
On the one hand, I definitely have that underlying desire to propagate my genes, but on the other, I can barely look after myself right now. What hope do I have of looking after a child? Or their mother, who I assume would also be involved somehow.
Heck, I don't even have pets because I'm concerned I'll inadvertently forget or mistreat them.
Also, ADHD to the left of me, mental illness to the right, here I am, stuck with a bad combination of brain genes. I'm not sure I want to risk passing this on.
Right now, the kindest I can be to the next generation is not to allow it to happen.
As for other men who are probably less atypical than my situation, there are plenty of things that can be done to support the next generation even if they don't get to make part of it.
Not every cell-line in an organism makes it to the final stage, but if they weren't there in the first place, the organism wouldn't make it to the final stage either. This analogy works for people (cells) in a society (the organism) too.
And last but not least: Men have a slight edge over women in that the ability to procreate doesn't really go away. Sure, it's not ideal for the kid if their father dies of old age before they're fully grown, or can't help out for some age-related reason, but similar things can happen with younger dads too.
Try using the full path to the jupyterexecutable in your script rather than just its short name. That way $PATH shouldn't matter either way.
That is, unless the jupyter executable or something it calls relies on something being set in $PATH as well. Still worth a try.
When the right-wing party moves so far right that the left-wing party now stands where the right wing party once stood, it's time for everyone to do a little soul searchi...
hahaha no! fuck that! profits! profits are all that matters! hahaha. bow to your corporate masters! dance, peasant dance! or die! we don't care! we have all the money! hahahaha!
If you want to time travel a bit, OpenWindows / OpenLook was very clean.
How clean? Literally nothing on the desktop.
Everything was accessed through an easily (re)configurable context menu.
By default there would have been absolute necessities on there but precious little else. It was up to the user to edit the config to add programs to it. Kind of like a forerunner of the Quick Launch toolbar or the Dock.
That said, I seem to recall it was possible to put launcher icons on the desktop too, although that is also where programs minimised to in icon form (Windows 3 used to do that too), so maybe I'm wrong about that.
Gonna guess that a font was in use when the installer tried to overwrite it with a new version, so it got marked for replacement at the next available time, which is usually a reboot.
But it might have been the case that the deletion request was just taking a long time, or else something decided a reboot wasn't needed, eventually pulling the rug out from under the font.
Sure, the new font might have been written to the old filename, but the inode will have changed and any programs looking at the old inode will end up reading garbage (maybe being stopped from doing so by the kernel) or being confused because the file there is marked as deleted now.
Presto, no font-o. [][][][][][][][]
harassing political dissidents
Mm-hm. There are good bots and bad bots. This being a subjective categorisation, and Uncle Elon wanting very much to be friends with Uncle Jinping, these bots are undoubtedly most welcome on the platform.
"Nothing to see here. Move along."
That's the thing. There is no title bar. The title bar, if forced to exist, would go above both of those sections.
GNOME apps seem to have been headed in this direction for a while.
If I open gnome-disks, for example, the title bar is kind of odd because it doesn't show the name of the program at all. It only shows the size of the currently selected disk, and underneath that in a smaller text subheading is the actual device pathname of the disk. How many other programs do you know that have a subheading under the window title in the title bar?
This feels like an early decision to do something different with that part of the window.
Further along in the evolution is the dconf-editor which no longer shows any kind of title bar at all. The window manager shows that the window title is "dconf Editor" but there's nothing on the window itself that says that.
Earlier versions of each definitely had a standard title bar (I remember dconf-editor having one fairly clearly, because the new interface seemed strange at first), but not any more.
There's also that desktop web browsers generally request that their title bar not be shown. Given that everyone has at least one browser window open, it would be almost foolish to assume there's been no influence from that design choice.
Depending on system, something like locate/mlocate might be installed, and is almost certainly available if the following seems like a good idea.
Tools/daemons like them are quicker for finding files - basically because they index all files except those in specified places. (Or potentially only those in specified places depending on tool/configuration.)
That way, rather than find -name 'some_wildcard_string', it's instead locate 'partial_filename_match or locate --regex 'some_regex_string'.
As for speed: locate / | wc -c returned 565035, the count of files currently indexed by mlocate on my computer, in 0.3 seconds. Quite a bit quicker than find! (locate / literally returns any file with a / in the full pathname, which basically means every single file in its DB).
Your use of "multiline" is not obvious to me.
Most multiline features are available, such as having multiple commands between if, elsif, else and fi is definitely possible (ditto similar constructs), and it's possible to extend commands over an explicit carriage return if the end of line is quoted with a backslash.
If you're talking about having Python-like whitespace-only indentation to specify the level of code, I'm not sure there is a shell like that, but if this is what you mean and you confirm, someone who knows better might be able to point us in that direction.
If you're seeking multiline comments, unfortunately most shells don't have this, but there are definitely ways to fool the shell into skipping portions of text. You would be better off with an editor that can insert a # at the beginning of multiple lines however, since that will guarantee that the shell won't accidentally try to process something in that comment block.
See also: The shell's own times command (where available), and/or the external command time, which is the fore-runner of all of these.
Those won't run a command a number of times or provide a pretty table like Perl's benchmarker will, but if you want to roll your own, those would be the place to start.
(I'm a big fan of Perl, but know that not everyone's ready for it yet!)
Going to assume Americans left them behind.
Nah. They need their skivvies. There's no way they'll get other men to do those things for them, and they'll be damned if they'll do it themselves.
See also: LUnix
(Actually not a joke despite a name that might at first arouse suspicion.)
Maybe the voters. The party itself is doing its best to sideline anyone who's actually red and instead promote its centrists and blue-thinkers.
Tangentially, there's profit and there's greed. A lot of profit-hatred is, or has evolved out of, profiteer-hatred.