Now try opening js interpreter and doing the same.
Also, try 0.1+0.2 in python interpreter.
This is really nice
But I have a habit to :w every 5 seconds, so I can't really use it
Well, in a plain text editor you are usually not expected to write strictly correct code (e.g. semicolons), it's just used for explaining your thought process while working on an algorithm. You can look at it as solving a problem on a white board
Fair enough. I've only created a visualization tool, I haven't gathered statistics.
Why? The purpose of this project was for me to see which keys I press more often so I know which fingers get stressed, and it exactly what the project does
Thank you for clarification!
I don't really understand how can specific programs map the Meta key as something. Isn't it the job of the driver to map key-presses to input events (which are then passed to display server by evdev)?
I thought it meant the same, Meta/Super/Windows
I saw these used in documentation interchangeably
I'm using a tiling window manager and neovim as my main editor, so I have to use hot-keys quite a lot As for the caps, I have it remapped to control
Keyboard shortcuts visualization
cross-posted from: https://programming.dev/post/18098231
> Have you ever wondered if your keyboard shortcuts are set up optimally? Well, I did, so I decided to visualize it with a heat-map. > > It proved to me that I rely on my left pinky too much, so I'll try to rework my shortcuts. > > You can check out the project here, currently it only works on Linux.
Keyboard shortcuts visualization
Have you ever wondered if your keyboard shortcuts are set up optimally? Well, I did, so I decided to visualize it with a heat-map.
It proved to me that I rely on my left pinky too much, so I'll try to rework my shortcuts.
You can check out the project here, currently it only works on Linux.
Ubuntu disk space usage after upgrade from 20.04 to 22.04
Hello, everyone. Recently I finally decided to update my system, and right after the update ran into a problem: before update baobab showed ~22 GB avaliable space, and after the update it went down to around 8.
Here's some info, that might be relevant:
df output: ``` Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 788700 1976 786724 1% /run /dev/nvme0n1p8 53050368 48246568 4054792 93% / tmpfs 3943496 0 3943496 0% /dev/shm tmpfs 5120 4 5116 1% /run/lock /dev/nvme0n1p8 53050368 48246568 4054792 93% /home /dev/nvme0n1p7 998060 133944 795304 15% /boot /dev/nvme0n1p1 364544 89768 274776 25% /boot/efi tmpfs 788696 104 788592 1% /run/user/1000
```
du -h / shows 23G, du -h /home — 13G. Overall I have 54.3G disk space, so (23+13)/54 doesn't add up to 93%
sudo lsof | grep deleted | wc -l shows 8433 deleted files that are still in use.
I also tried booting with liveUSB and running 'check' on partition via GParted.
I did some research online:
- https://forum.manjaro.org/t/baobab-shows-14gb-less-usage-where-is-the-rest/109527 - seems like a similar problem, but does not address huge du/df difference, also doesn't provide solution for me
- https://unix.stackexchange.com/questions/414417/du-not-accounting-for-space-shown-by-df helped me understend difference between du/dh, so I provided output of lsof as suggested.
- a lot of other stackoverflow posts, all having similar answers, that didn't help me
I tried some methods to locate what consumes all the space, but couldn't figure it out. Also, the problem seems to be getting worse (right now baobab shows only ~5GB avaliable space). Can you help me find the source of the problem (and ideally also help me solve it :) )?
Is it safe to move unallocated partition past Windows Recovery Image?
Hello. I have Windows - Ubuntu dual boot and I'm trying to move space from Windows to Ubuntu. I've already freed space from the Windows side
I'm pretty sure that I've read online that it can be dangerous to move the unallocated partition, because next boot to windows can corrupt my Ubuntu system. Is it true? Also, when I'm trying to move the unallocated partition, there's no option to "move/resize", so I swap them with the next following partition one by one. Is it the right way to do it?
