All the movement commands I know work the same in the terminal on a default install of macOS as it does in the terminal on various Linux distros I use.
Ctrl+A to go to beginning of line
Ctrl+E to go to end of line
Esc, B to jump cursor one word backwards
Esc, F to jump cursor one word forward
Ctrl+W to delete backwards until beginning of word
And so on
Both in current versions of macOS where zsh is the default shell, and in older versions of macOS where bash was the default shell.
Am I misunderstanding what you are referring to by shell motions?
Yea, but ctrl + arrows to move cursor between ‘words’ don’t work, especially sad when SSH’ing in from linux. It works fine when using terminal on macOS - you just use command + arrows.
The DuckDB website has the following to say about the name:
> Why call it DuckDB?
> Ducks are amazing animals. They can fly, walk and swim. They can also live off pretty much everything. They are quite resilient to environmental challenges. A duck's song will bring people back from the dead and inspires database research. They are thus the perfect mascot for a versatile and resilient data management system.
Never thought about that. Always wrote it all uppercase because that’s what camera maker Canon consistently does from what I’ve seen.
If I search for Canon raw on Google the Canon owned websites that I see writes it all uppercase; RAW.
One of their pages that I find even makes note of that:
> The letters RAW do not stand for anything – it's just a convention that RAW is usually written in capital letters – and the names of RAW files from Canon cameras do not end in .RAW.
I'd expect a cause is that most camera makers are Japanese, and it's not uncommon in Japan to uppercase words written in Latin alphabet for aesthetic reasons
Perhaps the combination of that and the old .raw filename extensions on old filesystem implementations where everything appears uppercase (since camera firmware is slower to catch up, this persisted for years even though contemporary OS already had no such limitation) made it stick.
If I have three email addresses petethecoolone@gmail.com, joemama69@gmail.com, and michael.j.smith@gmail.com, are those “fake” as well, then? An email address doesn’t have to reflect your real name.
How about when I use iCloud Hide My Email to generate a unique email address when I create a new account somewhere? Is that a “fake” email address as well?
Or do they mean hacked email accounts that belonged to someone else? But then calling them “fake” email addresses still seems weird wording.
A "fake" e-mail address is one that is not clearly tied to your real identity, citizen. There is no reason to use such non-identifying addresses unless you have something to hide. Comply, for the children.
I still don't really think this counts as fake emails, since it has legitimate use cases, but I suppose if their backend couldn't tell the difference and a single person used sub-addressing to sign up multiple times that you could argue that these are fake-ish.
Maybe a "fake" email address in their terms is an impossibly invalid one, unowned one that cannot be verified, or a disposable verifiable one? I'm not sure.
Fun fact: Gmail address prefixes can optionally intercalate a period between any letters. All accounts though must be remain unique after normalizing case and removing all periods.
a.bc@ = ab.c@ = a.b.c@ = abc@, but only one of these can be registered.
Which "spec"? Many specifications exist and not every MTA, mailbox, nor email client understands the latest and every implementation is guaranteed to have quirks, but here are the most common: RFCs 822, 2822, 4952, 5336, 6530. There is no the spec. Subaddressing isn't standardized, but there was a half-hearted RFC on that with too many extra features. How email user parts are interpreted is up to the MTA, mailbox, or email client. Plus subaddressing informally as a hack has existed since at least 2005 according to my rusty memory. It's, therefore, a de facto standard. Use it where possible to track down leaks of personal information, but it's likely to bite with some gotchas. I used to maintain a @{{name}}.name domain and email server where all emails went to a single catchall account without setup or subaddressing needed to disambiguate which source email correspondence was from.
> Dots are somewhat common as optional these days but not universal.
What’s the point of constraining oneself to what is in the OS package manager? I like to keep my dependencies up to date. The versions in the OS package manager are much older.
And let’s say you constrain yourself to your OS package manager. What about the people on different distros? Their package managers are unlikely to have the exact same versions of your deps that your OS has.
> What’s the point of constraining oneself to what is in the OS package manager? I like to keep my dependencies up to date. The versions in the OS package manager are much older.
I favor stability and the stripping of unwanted features (e.g. telemetry) by my OS vendor over cutting edge software. If I really need that I install it into /usr/local, that it what this is for after all.
> And let’s say you constrain yourself to your OS package manager. What about the people on different distros? Their package managers are unlikely to have the exact same versions of your deps that your OS has.
This is a reason to select the OS. Software shouldn't require exact versions, but should stick to stable interfaces.
Anyway also going to note that "police police police police" turns into
Accountability. Integrity. Synergy.
In today’s fast-paced ecosystem, it’s not just about enforcement—it’s about strategic oversight.
I’m thrilled to share how we’re leveraging cross-functional governance to ensure every stakeholder is aligned. It’s about building a culture of compliance and driving impact through consistent monitoring.
Who else is prioritizing high-level security protocols this quarter? Let’s connect!
Note that "police police police police" is a grammatically valid sentence, with multiple different parsings, one of which we could rephrase as "the people who keep a watchful eye on what the police are doing, keep a watchful eye on what the police are doing" -- that is, the police police are policing the police -- so it's even true.
Technically it is a a possible infinite sentence, as it can mean both "terrible" and "bottom", hence the sentence would be "terrible terrible terrible terrible bottom", which is colloquially valid.
This is a poor understanding of set theory and an even worse one of LLMs. Notice this output here:
>Accountability. Integrity. Synergy.
is not really grammatical either. The "grammar" is the logic internal to the reference relations of the given signs, but the "inner" of the text is always given by the supplement (the next token prediction) which is demanded by such a total coherency, but which also erases and puts it into question since such a supplement itself demands its own. What is given is the always incomplete text itself, which is always open to its own re-signification, and thus its own possibility of a new grammar, of every possible prompt.
yeah, I was being facetious, which seemed to me very in keeping with the subject and main post. I don't expect an LLM to output a grammatically correct sentence or require grammatically correct input.
reply