palordrolap @ palordrolap @kbin.social

Some middle-aged guy on the Internet; Seen a lot of it and occasionally reg

---

Read more

Posts

0

Comments

434

Joined

2 yr. ago

The KP prefix means it ought to be part of the number pad (literally Key Pad), not the regular keyboard. If there is a keyboard with such a key, I didn't turn it up with a quick Internet search. (In fact a search now turns up my mention of it in this thread via a Lemmy instance. There can't be much information about it out there if even Google is reduced to linking my comments(!))

By comparison, there's apparently a rare Brazilian number pad layout that has a dedicated comma key, which is almost certain to be KPComma.

I did see a couple of layouts that put a copy of the +/= key on the keypad instead of the regular +. Maybe that's what ends up with the MinPlus key code despite the name being "wrong".

KPInsert is the 0 key on the number pad. Since you mention an Fn key, I'm guessing you either have a slim keyboard or a laptop of some sort. That means wouldn't have a number pad or its 0 key. At least not without it being enabled through, well, the Fn key or something like that, if some keys do double duty.

Curiously, upon checking my own system, the Insert keycode seems to be 110 not 118, but this might vary from keyboard to keyboard and system to system. Might be worth double-checking your own system anyway.

118 is associated with KPMinPlus for me, whatever that is. Pretty sure whatever keypad key that is, I don't have one. (It's not KPPlus or KPMinus, which are what you probably think they are. There's also a KPComma entry, and I definitely don't have a comma on my keypad. Perhaps some other keyboards do, what with it being the decimal separator in some countries.)

Because they're lazy and need to get better jobs. Don't come at us with your woke logic. -- Conservative HQ

(The trouble with making an ironic comment like this is that conservatives won't see what's wrong with it, and non-cons might think I'm conservative.)

A couple of options present themselves.

1. If you're willing to forego the key combination and can live with an alternative, you might want to check if your system supports the Compose key. It might not be bound by default, but it's often put on Scroll Lock, or, if you have a non-US keyboard, to Shift+AltGr.

Once the Compose feature is activated, certain sequences of keypresses can be, well, composed into a new character. Various "obvious" combinations are usually supported by default.

e.g to get "≠" I hit Shift+AltGr, let them go and then type "/" followed by "=" (no quotes). It also works with the slash and equals in the other order. Some compositions only work in one order, but most work either way. Other symbols that are very much not on my UK keyboard include ä, é, ß, ¤, °, ±, ², etc. (Shift+AltGr followed by "a, 'e, ss, ox, oo and ^2 respectively).

1. Check if your window manager has a keyboard configuration tool that allows the running of commands on certain key combinations. I use Cinnamon which has this.

You could then set up Ctrl+Shift+0 (probably not 1 and 0 at the same time though) to run a command like sleep 0.5; xdotool type "≠".

You'd need to install xdotool if you don't already have it installed, and you'd have to get ≠ for the command itself from the Character Map or copying it from another source to avoid the Catch-22 there.

What are the odds that muons are more sensitive to neutrino interaction and this is what the scientists are seeing? Muons are pretty massive, after all, and neutrinos are literally everywhere. Obligatory: "billions of neutrinos pass through you every second".

Muons are leptons like neutrinos and their electron cousins, and we already know that electrons can be boosted by the occasional neutrino interaction. A free muon in a magnetic field has nowhere to be boosted to, so, coupled with a hypothetically higher chance of interacting with a neutrino, I'd expect something to happen when it does, though not exactly what.

I figure we don't already use muons in neutrino detectors because they don't last very long (about a second) before decaying, and the only way to get them to last longer is to accelerate them to a decent fraction of the speed of light. That way, from our reference frame they can last minutes or more. That's going to be energy-hungry compared to the passive detectors we have.

i.e. the passive detectors which take advantage of the aforementioned electron / atom interaction.

Things like this happen at least once a year in my home town. There was even a rumour that there might be a clandestine team of people for hire, kind of a pyromaniac version of the A-Team.

Whether or not that's true, a few years back a then-recently-sold building had some pyromaniacs pay a visit, but they were careless and were seen and reported by people in neighbouring buildings.

The building survived virtually unscathed. And it has sat unused by the purchaser and undoubtedly watched by nearby buildings' CCTV since then.

There have been others fires elsewhere since then (I can think of a tyre yard that went up for suspicious reasons), but nothing in particularly well populated areas that I can recall.

Channelling my father here, but the lessons learned (but not fixed) after Beeching gutted the railways will be learned again here only too late.

That is, once you get rid of the minor bus routes, you'll realise that quite a few people were using those to get to the major bus routes, and now some of the major bus routes are as little used as the minor ones were.

And so you repeat. Close the minor ones. More minor ones. Confused face. Close the minor ones. Customers are complaining they can't get anywhere. Profits aren't rising. Angry face.

Soon you're left with only the buses that run the straightest routes to the closest nearby major places and all you can say is "nothing we can do, it's too expensive to run anything else."

If you wanted to say what I said without using a genericised trademark, how would you say it?

Nice username by the way.

Makes up for the lack of painful conscience stabs the guy has I suppose.

Can't say I fully understand his position on this, but I'd still rather have him running Brazil than the other guy.

"The world needs a new system of global governance." Let me counter that part with "any long term system of governance inevitably becomes corrupt (assuming it wasn't corrupt to begin with)."

It may be true that the (subjectively) important UN countries' support of Ukraine in the conflict might not be for reasons that are completely aligned with those of Ukraine itself, but the fact Ukraine is being supported has - shall we say: ironically - prevented the governance of that country from being replaced by a more corrupt one.

Of course, pro-Russia folks will have the opposite opinion there.

which commandname will tell you if there's a command already by that name on your system without having to run anything.

This only finds things in places stored in the $PATH environment variable, though.

You could query your package manager to see what packages for your distribution might contain the command name, but 1) that will also turn up support files and the like and 2) Not all distros have the same commands, especially once you get beyond the core Unix/Linux command set.

e.g. on a system with apt, I can run apt contains commandname and get a list of everything containing "commandname"

Another user suggested prefixing with my_, but you might consider using your initials, a short form of your username or some other identifier instead. e.g. Everyone is "me/my" to themselves, but fewer people share your initials.

Also, a suffix might actually be a marginally better choice depending on your tab-completion preferences.

There's precedent for some actual "official" commands using a .suffix style, especially when multiple packages have their own version of a particular command, or a minor variant. On my computer I have things such as uncompress.real, vim.tiny, lzip.plzip and telnet.netkit, for example.

Something like scriptname.arcslime would fit right in, whether or not scriptname is a thing in its own right or not.

Technically on the cusp of Gen X / Millennial. Been on the Internet a looong time, but I still don't know all the memes.

Having now web-searched that name, I am now aware of the copypasta.

Edit: Was not aware of the Torovoltos copypasta when I wrote the below.

That sounds more Greek than Russian.

"Lën Nikolaevitch Torpravi(tel)sky" would be a Russified calque of Torvalds' name, although that has at least a couple of issues with it. (1: The first word is literally "Linen". Same root, but no personal name developed from that root in Russian that I can see. 2: No-one has either surname.)

That's the thing, see. A bullet. It is known he was murdered.

Somewhere in the Kremlin someone is thinking that this was entirely without style. So blunt. Barbarous. When a man falls from a window it is ... an accident.

Meanwhile, somewhere in Ukraine, someone is thinking "Style be damned, this was a message."

They will continue to disagree about which method is best regardless of specific situation and intended subtlety until one of them is shot or falls out of a window.

1. Close dconf editor.
2. Backup /home/yourusername/.config/dconf/user file just in case things break later.
3. In a terminal: gsettings reset org.cinnamon.desktop.default-applications.terminal exec-arg
4. Open dconf editor and see if the exec-arg entry is now visible.

If not:

1. Close dconf again.
2. Terminal: gsettings set org.cinnamon.desktop.default-applications.terminal exec-arg "--"
3. Open dconf editor and see if the exec-arg entry is now visible. Maybe it doesn't show up if there's nothing in it (which is strange, but I guess possible).

Also "--" is usually a safe command line thing because it means "end of arguments" for most commands.

You can try:

1. Terminal: gsettings get org.cinnamon.desktop.default-applications.terminal exec-arg

...to see if the entry has the double dash or not, whether or not it shows up in the dconf editor.

Further things:

Uninstalling and reinstalling the dconf editor might be worth a try.

The gsettings command should be usable to set exec-arg regardless of what the dconf editor says.

Restore that backup if things do go screwy. I can't see any obvious reason why they would, but I can't explain the dconf editor's behaviour either.

V2 be like: "WHAT did you say about my mother? F... you, Earth man."

Mission control: "Dude you don't have a mother it was a typo. Dude. Talk to me."

seen

Mission control: "Dude."

seen

Mission control: "C'mon man."

This message could not be sent. V2 may have blocked your number

fortune cookie -s | cowsay_random | xmessage -xrm "*message.scrollVertical: Never" -buttons "" -nearmouse -bg gray -fg black -font 7x13bold -file -

Requires that fortune be installed along with the eponymous cookie fortunes set (these usually come with the default install).

cowsay_random is not installed fully working by default but can usually be found among the files installed with cowsay. (The #! header might need to be updated to use python2 instead of just python as I found out when testing this)

xmessage is a seriously old program but it works just fine. The command line supplied pops up the output of the preceding commands near where the mouse is on the screen. The -file - bit is necessary to read the pipeline.

See the man page for xmessage if any of the other options aren't too clear.

Your further mission is to arrange for this to trigger somehow or another, be that at random or when some other event occurs.

Caveats: 1) No idea if this works on Wayland. 2) No ANSI colour code support, so no lolcat. Figure out a way to use an xtermor something if that's what you want.

Go to Customer Services and vehemently [object Object]

What's the result of gsettings list-keys org.cinnamon.desktop.default-applications.terminal in a terminal?

Also try gsettings list-keys org.gnome.desktop.default-applications.terminal in case your system uses the GNOME setting(s) instead.

If either show exec-arg but the equivalent isn't showing up in the dconf editor, you could try changing the list-keys to reset. Make sure you back up your dconf before doing this on the off-chance it's corrupted and this makes it worse.

Likewise gsettings has a set subcommand that changes values. Similar "have a backup" caveats apply. (I'm not expecting that it is corrupt, but better safe than sorry).

Worst case scenario here is that you have to create a [shell/Perl/Python/etc.] script (assuming that will work) or C executable (almost guaranteed to work, but a pain) that execs the necessary command with the required arguments and then give the name of that to the exec key in the dconf.

Had a quick look in my own dconf and there's an entry called exec-arg (same path) with the description "Exec Arguments". That looks like the place to add the options.

(Not sure how to go about adding this if it's not there though. Editing a value and modifying an underlying schema are a bit different in difficulty, especially if the path is deprecated or not supported by the version of Cinnamon in use.)

The issue I'm not sure about. Perhaps there's $@ / $1 / %s / %1 or similar parameter support, but I'd have to root around the Internet or source code to know for sure.