- ALACRITTY CHANGE FONT SIZE INSTALL
- ALACRITTY CHANGE FONT SIZE PASSWORD
- ALACRITTY CHANGE FONT SIZE FREE
ALACRITTY CHANGE FONT SIZE INSTALL
I know that running sudo npm install -g is really bad practice but is using npm as a user which has write access to your main shell configuration file almost as bad just with a few extra steps in between, or am I lacking an understanding of how user permissions/shell configuration/npm works? Obviously I do trust most of the programs that I install to not be malicious, however, I do use npm as a package manager for my own projects which is commonly accepted to be a vector for malware due to the sheer number of dependencies each module and it's dependencies can have.
ALACRITTY CHANGE FONT SIZE PASSWORD
I'm concerned that a malicious program that I install on the user level could then trick me into somehow giving up my sudo password through this method. In malicious hands this could probably be used to edit aliases or append a directory of the attackers choosing to the beginning of the $PATH. Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767ĮDP1 connected primary (normal left inverted right x axis y axis)ĭP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 700mm x 390mmġ920x1080 144.00 + 120.00* 119.88 120.00 60.00 50.00 59.My understanding of user permissions is that any process spawned by my user will then have read/write permissions to this file. Scaling RGB by 0.66 from Rgb Īgain, I'm totally happy currently building against an older commit, but it sounds like the current behavior is not what's intended, so I'm submitting this information as a bug report.
If you have any more questions, please let me know.Ĭonfiguration loaded from /home/rlue/.config/alacritty/alacritty.ymlįinished initializing glyph cache in 0.099498874 If you like proper DPI scaling between your monitors, the proper way to 'fix' big font sizes is to reduce the font size in the config. This is how DPI is supposed to work even though a lot of applications on Linux don't make use of DPI (which is why the workaround I've mentioned before exists). If you have two screens where you previously didn't use any DPI and they are now both properly recognized as 2.0 DPI, then the font size should be doubled now. This is fixed with the #1403 PR and you might be able to make things work better by running that. However there currently is no resizing when an Alacritty window changes the screen, so if it's scaled up on one screen and you move it to another where the scaling is 1.0, it will be way too big. Due to rounding this will never be 100% accurate, but it should be about the same size. The goal is to have the same size on both monitors, not in pixels, but in millimeters. All bug reports are very much appreciated and I'm happy to follow through and help whenever I can.
ALACRITTY CHANGE FONT SIZE FREE
However feel free to ask more questions if you need help to get this working.Īlso don't worry about sounding like a dick, you do not. I'm going to close it since it's not an actual issue with Alacritty (or the way this works is intentional). I could see that in the future it might be possible to override the DPI for all platforms in the Alacritty config, but since you're using X11 what is in place already should be fine to do the job for you. You could also export this in your shell's profile file or create an alias to make this permanent.
This will set a fixed DPI value of 1.0 for all your displays and should restore the behavior you've had previously. Another option which is only available on X11 is to start Alacritty with the environment flag WINIT_HIDPI_FACTOR=1.0 alacritty. If you switch the font size to 8 you should get the same size you've had before the DPI change. Now there are two possible solutions you have to solve this problem right now. So the font size you've specified (13) is in pt, which means that no matter the size or resolution of the display you open Alacritty on it will always be the same size (in mm).
This behavior is intentional since the latest version of the windowing library will always automatically use DPR. So if you change master to the font size 22, it's will probably give you the same font size. However on the master branch you can see that the device_pixel_ratio (short dpr) is 1.6666666, so your font size 13 is scaled by 1.66666 (21.67). I've looked at the device_pixel_ratio of the second output and it's 1.0, so there's no scaling. I didn't notice it since in your -vvv log you posted the master first and the working branch second.
0 kommentar(er)
