73
Yea, the drying out of the skin with the alcohol reduces the amount of blood, but there is always going to be some. Cutting straight across is a very good way to avoid future issues as well.
Yep, pretty sure you are right.
Execute the previous command as root
Fun fact if you are using bash, !! will evaluate to the previous command, so if you miss sudo on some long command, you can also just do sudo !!.
alias clip='xclip -selection clipboard'
When you pipe to this, for example ls | clip, it will stick the output of the command ran into the clipboard without needing to manually copy the output.
Yea, .ml had defederated with it, but any instance can if they want.
Go to a doctor.
I am not a doctor. You should not do anything I describe herein and should consult a medical professional.
I fixed them myself a few times on each foot, trialing and erroring until I found a solution that since using it, has worked well for me in every case.
Note in less extreme cases, you can try to cut a little V in the middle-end of the nail. In my cases, it was much too bad for this to work.
I sanitize the toe and an x-acto knife with a new blade (pointed tip, triangular in shape) that has been cleaned of any foreign substances (such as the oil they sometimes come covered in) with 99% isopropyl and begin cutting a straight, vertical line on the side of the nail that has the issue, as close to the edge as I find reasonable. I go very slow and as light as I can, tracing that line over and over, as I don't want an x-acto knife plunging into my toe itself. Eventually I make my way through the nail, but the nail is still connected under the cuticle. From this point onward, every day, I unravel cotton balls into strips and wet them thoroughly with alcohol, and then secure a strip or thick, folded pad to my toe with medical tape. The cotton should be very wet, but not dripping wet.
I found that regular bandaids were not effective due to adhesion issues and because they lack the ability to hold enough alcohol in their padding. Each day the skin around the nail will begin to die a little bit and dry out. I use sanitized forceps and the sanitized x-acto to cut a bit more and to pull on the edge of the nail each day (in an up and out fashion and occasionally away from the toe), but try not to force it too much. Eventually the nail breaks and comes off. Where it was dug into the flesh of the toe, there will be a small hole. At this time I sanitize the entire toe and the wound with alcohol. Finally, and the most important part of this process - I do the same process as previously described with the cotton, alcohol, and tape to bandage the toe every day, or twice per day as needed until the nail grows back in correctly. If this is not done, it is likely it will grow back ingrown and you will be at step 1 again.
In my experience, I had to keep it santized with alcohol and very dry. I found that taping it up wet with products such as polysporin prevented healing and would result in the nail becoming ingrown when it grew back in, as well as causing pain and increased inflamation. Using alcohol, day to day the pain lessened and it was able to grow back in normally each time. Needless to say as well, but you want to stay off of that foot as much as possible as walking on it during this process can lead to inflammation.
This process has taken me anywhere between 3 days to 2 weeks depending on how badly ingrown it was.
When it gets fixed it is great, there is almost instant relief from the pain.
Not always true, instances can defederate lemvotes so that it doesn't function I believe.
Okay, well to balance that anecdotal information with some more, let me put some of those bad points listed in context with what my experience has been on Debian 12 Stable with an RTX 3090.
- Proton is great, and is really impressive, but you still must download several versions to expect running everything you want, and you must do trial and errors to find the most efficient version for you (fortunately, ProtonDB helps a lot)
Somewhat true, but protonDB is so accurate that I think I have only had to trial and error 1 or 2 games ever. Downloading multiple proton versions isn't a big problem as they aren't too large, and I have only ever needed either the latest stable release, or the experimental release. As far as actual game compatibility goes, when I moved to Linux I looked up every game in my steam library in proton DB to see what I was working with. The result was that:
95 of my games ran natively on Linux. 31 of my games were rated platinum. 73 of my games were rated gold. 12 were rated silver. 3 were rated as bronze. 3 were noted as unplayable.
- Nvidia drivers greatly improved recently, that's true, but you still have to download the latest beta drivers to run games through gamescope, and they are not on the official pacman repo, so they won't upgrade automatically.
You have to add 1 repository for the drivers and then it upgrades when you upgrade as normal. This is like a 2 step process of editing a text file and then running one command. I have never had to use gamescope.
- Now, let's talk about performance. Yeah, I have an Nvidia card. Yeah, I know it's bad for Linux. But that's what I got, and I bought it very recently, so I won't buy an AMD card for Linux now. When you talk with Linux users, they will always say that performance in games is way better than in Windows. Maybe that's true in some games, but I'm afraid that's only the case for AMD users. With an Nvidia card, the best you can get is the same performances as in Windows. And that is when you're lucky. Then, if you want shiny things like HDR, or DLSS frame generation, you MUST use gamescope, and it will have a cost in terms of performances. And you will need trials and errors to get everything you want.
Performance on some games is better through proton and this is true even with my NVIDIA card. This is largely because where you lose performance on emulation, typically you are making up for it in leaps and bounds because Linux is not running 1000 telemetry processes and stuff in the background like Windows does. I have only played one game where the performance was noticeably worse. I don't use gamescope at all. As far as I'm aware DLSS/HDR work fine (running armored core VI on ultra graphics for example looks and runs great and the settings seem to be enabled). As I said before, I only ever had to trial and error 1 or 2 games.
- That said, don't expect other shiny things like RTX HDR in desktop, frame gen out of games that natively support it, DLDSR, and many other things like that, to work in Linux. In fact, everything that is available through the Nvidia App or the Nvidia Control Panel won't be available in Linux. You must be aware of that, because that's very cool features you'll likely never (or in a very distant future maybe) see on Linux. You won't be able to use Lossless Scaling neither, and there is no equivalent in Linux - even in gamescope, at least for now (but maybe that'll come, I don't despair of seeing this happen in the future).
Parts of this statement are just straight up not true. When installing the drivers, you also install the NVIDIA Settings application which does not contain all settings from the NVIDIA control panel, but a subset of them. RTX HDR in the desktop for example does work, but it is just dependent on the window manager. Here is another reddit thread stating as much. I assume the OP of the thread you linked doesn't really know what they are doing. If you want a windows-like experience you probably would be using plasma. Also I'm pretty sure lossless scaling has been a feature in protonGE since 2021, so if you really needed it for a game, you would just install that proton version and use its FSR feature there. I mean, this is stuff that comes back top link when I google for "Lossless scaling linux NVIDIA". The OP really doesn't seem too dedicated to looking up their problems.
- Hardware compatibility too, while very good, and even more so with Arch based distros of what I heard, is still a work in progress. For example, I didn't found out how to make Dual Sense haptics work in The Last of Us Part II Remastered. Everything works, even adaptative triggers, but haptics won't work. I know it has to do with the impossibility for the game to find the gamepad's sound device, and there is many workarounds. I tried ALL of it, but still, it doesn't work. That took me several hours to try it, and that's what finally made me give up on Linux for gaming for now.
My PS5 controller including its haptics work natively on debian. I didn't even have to install any drivers or software for it to work. I just plugged in and started playing. I think it just has to be wired for haptics, or whatever you are using for wireless needs to be capable of supporting the controller and its haptics.
So pretty much all of these issues seem to be related to the OP not really investigating their issues well, or not understanding where to go to change settings, or not understanding how their package manager works.
I'm using an Nvidia card on Debian with 0 issues myself and the driver installation was really easy. I'm curious what source you read stating that they are worse, by how much, and in what way. Do you have a link I can read? Thanks.
Can you give some more details on the redlib instance and it's usage for doing as much? I am in the same boat as you and would much prefer being able to have some kind of redirect if I have to look at content under some reddit link.
Thanks.
Pre-made tools have reproducible and known functionality that has been tested whereas LLM's when generating this across 100 different users may come up with 100 different untested results in which someone who doesn't know programming won't really know what complete result to expect from the code it generates.
In short, pre made tools don't require programming knowledge because someone has handled all of this for you previously, but LLM's do require programming knowledge to make sure what it made is going to work safely and correctly.
13
Hello all,
If this is not the right community for this question, I would be happy to be redirected elsewhere, so just let me know.
I recently configured my terminal emulator to an aesthetic that I like (custom font, coloring, shell prompt, etc) and it has made me wonder about customization in gnome.
One of the biggest things that I wish I could change in gnome is the grey-ness of the application view.
In this screenshot, you can see the familiar application view. In between the organizing folders, the desktops, and the dock, there is just so much nothing.
I am wondering if it is possible to customize this relatively easily. I would much prefer an image of my own choosing in place of this, or at least a different color from time to time.
Is anyone aware if this is configurable? I can't seem to find an extension for this, or any real information on how you would do such a thing.
Thanks
view more: next ›
Economy doesn't benefit you presently unfortunately.
Somehow before shit really hit the fan I was able to land a non developer role at a software company which only asks you to come in twice a week. Looking to move into development at the company, but from the outside software Dev roles are super flooded with applicants right now.
Whatever you do, your chances for remote work are better if you get in with a small company of 10 to 20 people.