![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Sorry, i said it was a mersenne prime, then realized it wasnt, so edited it and deleted it. It was a mess
Sorry, i said it was a mersenne prime, then realized it wasnt, so edited it and deleted it. It was a mess
That is what it means. Any detail in the waveform that is not captured by a 48kHz sample rate is due to frequencies that humans can’t hear.
Now my question is, how should I deal with these pacnew files? should I always remove them, always replace them, always read them and decide?
Always read them and decide what to do. However, what to do usually isn’t too remove or replace them, but to update them with the changes instead. Most text editors have a way of looking at a diff of two files. This will highlight the differences and you can decide based on the individual changes (maybe it’s something you purposefully changed, maybe it’s a change to the default). If you use vim
, vimdiff
will do this.
I’d rather not read these things everyday, it’s a bit boring, so I hope there’s a better solution. How do you deal with these?
After you make your decisions on what to do, delete the pacnew
, otherwise you’ll keep getting messages about it. They don’t get updated all that often (except mirrorlist
, I usually just delete that and run reflector
every once in a while).
cd
without arguments takes you to $HOME
, so it’s the same as cd ~
I should really just buy a cable for my xbox 360 controllers
If you’re talking about the official wireless xbox 360 controller, I believe the cable is only used for power, not data.
You have a typo: It should be x86_64
, not x86-64
Ctrl-Shift-N restores closed windows