HN user
I've made a similar library called bash-term[1], which is similar, but only has functions for lower-level operations, like moving the cursor to the end of the line, etc. It's also cleaner and has almost no global variables.
Glad I could help! It's too bad that my HN post didn't take off.
This is the original post to the one[1] that blew up.
Oh, so _this_ is why I've been getting so many hits...
I was the original creator and the original post[1] was from a day ago. Glad to see it is helpful!
Ctrl+K is often used to perform any kind of action. On Discord, Slack, GitHub, etc. let you perform any action with this hotkey. It's also a generic search, as website searches implemented with Algolia use this by default.
Ctrl+/ is usually used to show all the keyboard shortcuts, or at least the most common ones. Usable on Discord, Slack, VSCode, etc.
This is the kind of stuff I describe in my semantic hotkeys[1] piece. There isn't a really good way to define hotkeys for web apps across websites. In lieu of a browser spec (for now), or a non-normative recommendation, there needs to be convention under no uncertain terms about which keys do what.
We already have Ctrl+K and Ctrl+/, I think it's time to formalize these conventions, and more! There is a gap of semantic interoperability across websites that needs some fixin'.
[1] https://hyperupcall.github.io/blog/posts/semantic-hotkeys/
I'd say bashrc and profile and friends are one of the few examples in which using hardcoded paths is OK. Same with SSH, GPG, and PAM.
But when people are talking about compliance, and hardcoding very few people are talking about those applications - there are hundreds of other applications do the wrong thing, and some scripts hardcode things as a result.
What are you talking about? When people say the "XDG spec", they are usually referring to the XDG Base Directory Specification, but there are other specifications from XDG - are you talking about a different one?
Because the XDG Base Directory Specification does not dictate about how files should be saved - whether in Pictures/, Documents/, or anything else...
yes - not all Linux distros do this
This is excellent!
Over the years, I've been pleased to see that more and more distributions are writing their disk images and the like to the ESP. (Previously, dd'd USB images for distro installing _required_ the creation of a /boot partition)
The logical next step would be to standardize everything through systemd, and ensure all boot images are autodiscoverable and automatically bootable.
It's been somewhat frustrating for distributions to install GRUB, hijacking the previous prioritized boot PE, and have entries for other installed Linux distributions missing.
Thank you - this is a basic prerequisite for any productivity app imo
That sounds amazing - there are some similarities with Amie, but customizable views is something I'm looking forward to try out
Thank you - it's quite unfortunate that there isn't a "free plan"
Just signed up and it seems it is not possible to use this on Linux. Disappointing... Is Linux support planned?
This tool looks quite similar to Amie.so - which I use in conjunction with Todoist - do you have any major differentiating features? It seems like mainly there are more integrations
It seems unfortunate that the free plan is really just a 7 day trial, unless I misunderstood
Hey Ced!! Woahhh, I didn't know this project is sorta its own OS - that's epic
It's pretty cool to see projects like this, Sinerider, and the like being developed, even if I am on the sidelines haha
Safari heavily nerfs PWAs, making their use more questionable. It's possible that they also need more access to the underlying computer.
Thanks, that is quite unfortunate
Cool I see - I override cd, but now I'm pondering if I should change approach. But I guess what I was really asking is how you do it in non-interactive mode?
I'm not sure how you can seriously advocate for ditching 'dd' by calling it "obscure"
Thank you for sharing - I've written my own "version" of asdf in Bash too, and I'm getting to the point where I would like to write some portions in Rust.
Does qwer support per-directory, local versions of plugins? I'm finding that that's difficult to do without shims...
What sort of compatibility issues exist with pyenv and poetry? Curious as I've never mixed the two...
Hmm, yeah I saw that one. Still don't think the motivation is super strong
Yeah I sympathize with you - my goal is for the Linux community to use a system - that is, a well-defined one, not one born arbitrarily out of the (`if (name[0] == ".") file_hidden = true;` code that has since metastasized into an ungodly manifestation of chaos itself. And that good system is the XDG Base Directory Specification. I'm sure as you know, Unix systems in general have a bad history of ad-hoc protocols and conventions, and in the process of correcting for those, somethings going to be disrupted. I've done my part to ensure that a config location that exists will continue to be looked at, but as you mention, it's confusing and increases complexity. I'm sorry, but that is what I'm willing to risk to fix this particular underlying issue.
If you read the parent comment, then you would know that I'm correcting the claim that not using XDG Base Dir Spec is the de-facto standard. It's not, so I'm simply stating that
I asked for an exact phrasing, not for an explanation, because I have already written exactly that under the "Should I do this on macOS?" heading...
Hmm, that's why I said inherent? Because as you mentioned there is a separate macOS directory structure and the system utilities don't follow the specification. Also, the specification is only written for Linux in mind, which is why I said "not inherent for macOS.
Is there an exact phrasing you would prefer?
no I think you're right, that was a typo
Mainly because it's easier to get people on board when we're keeping a few of the super core dotfiles, especially since those are kind of impossible to change - they are hard coded literally everywhere
Admittedly, the ~/.bashrc etc. files should be there too - but I wanted it to look cleaner :P
Thanks for the suggestion - agreed, I'll make that change
Oh right I forgot about those - I set some environment variables so I don't see any of those except for .pki
And in my opinion .ssh and .gnupg are okay since in some contexts, the "XDG variables" haven't been initialized in certain circumstances when using those utilities.
But yeah, I'll have to look into those - maybe there is something I can do to fix that