KDE has settings for shadows but they don't show on maximized windows (I have the maximize window gaps script installed). I'm wondering if there are any scripts that produce their own shadows.

KDE has settings for shadows but they don't show on maximized windows (I have the maximize window gaps script installed). I'm wondering if there are any scripts that produce their own shadows.

I recently switched from Code Saver to my own Iosevka configuration, and at first I found it to look great in Neovide but too narrow in my terminal, especially with FFmpeg output. I thought maybe it was due to font rendering differences, like spacing or character widths. But then I took a screenshot with the font sizes set the same in both apps, and overlaid a word in one app to another ... and the text is rendered the same.

FFmpeg output for reference:

[out#0/mp4 @ 0x600000f14000] video:232962KiB audio:395KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 0.017517% frame= 1519 fps= 36 q=-1.0 Lsize= 233398KiB time=00:00:25.53 bitrate=74882.4kbits/s speed=0.606x [libx264 @ 0x15a0062a0] frame I:18 Avg QP: 5.27 size:441876 [libx264 @ 0x15a0062a0] frame P:622 Avg QP: 8.04 size:264060 [libx264 @ 0x15a0062a0] frame B:879 Avg QP: 9.91 size: 75488

I recently switched from Code Saver to my own Iosevka configuration, and at first I found it to look great in Neovide but too narrow in my terminal, especially with FFmpeg output. I thought maybe it was due to font rendering differences, like spacing or character widths. But then I took a screenshot with the font sizes set the same in both apps, and overlaid a word in one app to another ... and the text is rendered the same.

FFmpeg output for reference:

[out#0/mp4 @ 0x600000f14000] video:232962KiB audio:395KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 0.017517% frame= 1519 fps= 36 q=-1.0 Lsize= 233398KiB time=00:00:25.53 bitrate=74882.4kbits/s speed=0.606x [libx264 @ 0x15a0062a0] frame I:18 Avg QP: 5.27 size:441876 [libx264 @ 0x15a0062a0] frame P:622 Avg QP: 8.04 size:264060 [libx264 @ 0x15a0062a0] frame B:879 Avg QP: 9.91 size: 75488

I recently switched from Code Saver to my own Iosevka configuration, and at first I found it to look great in Neovide but too narrow in my terminal, especially with FFmpeg output. I thought maybe it was due to font rendering differences, like spacing or character widths. But then I took a screenshot with the font sizes set the same in both apps, and overlaid a word in one app to another ... and the text is rendered the same.

FFmpeg output for reference:

[out#0/mp4 @ 0x600000f14000] video:232962KiB audio:395KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 0.017517% frame= 1519 fps= 36 q=-1.0 Lsize= 233398KiB time=00:00:25.53 bitrate=74882.4kbits/s speed=0.606x [libx264 @ 0x15a0062a0] frame I:18 Avg QP: 5.27 size:441876 [libx264 @ 0x15a0062a0] frame P:622 Avg QP: 8.04 size:264060 [libx264 @ 0x15a0062a0] frame B:879 Avg QP: 9.91 size: 75488

I recently switched from Code Saver to my own Iosevka configuration, and at first I found it to look great in Neovide (a Neovim GUI) but too narrow in my terminal, especially with FFmpeg output. I thought maybe it was due to font rendering differences, like spacing or character widths. But then I took a screenshot with the font sizes set the same in both apps, and overlaid a word in one app to another ... and the text is rendered the same.

FFmpeg output for reference:

[out#0/mp4 @ 0x600000f14000] video:232962KiB audio:395KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 0.017517% frame= 1519 fps= 36 q=-1.0 Lsize= 233398KiB time=00:00:25.53 bitrate=74882.4kbits/s speed=0.606x [libx264 @ 0x15a0062a0] frame I:18 Avg QP: 5.27 size:441876 [libx264 @ 0x15a0062a0] frame P:622 Avg QP: 8.04 size:264060 [libx264 @ 0x15a0062a0] frame B:879 Avg QP: 9.91 size: 75488

Crossposted from https://www.reddit.com/r/firefox/comments/1jd5nlk/convert_chrome_extension_to_firefox_addon/

There are a number of FF versions and forks that this will work with, but I used FF Beta (I've also confirmed it to work with FF Nightly & Iceraven. Conversely, it did not work for Mull and iirc, it cannot be done using FF Standard Release/Stable)

• Step 1 - have the CRX file for the Chrome extension handy. There are countless Chrome extensions and FF add-ons that will extract it for you.

• Step 2 - install the CRX Installer add-on (or get the XPI file by whatever means) →Extensions→Click CRX Installer→click "Browse"→ select the CRX file*, which should result in the creation of an XPI file.

• Step 3 - go to Settings→About Firefox Beta (or Nightly, Iceraven, etc)→Tap the logo at the top of the "About" section until you see a toast message saying "Debug Menu enabled" (I think 5 taps)

• Step 4 - navigate to "about:config" → search "xpinstall.signatures.required" →tap "Toggle" so that it displays "False" (make sure there's no whitespace; copy exactly what's between the quotation marks or the search won't return the corresponding flag)

• Step 5 - go back to the main Settings screen, and now under the Advanced section, after "Extensions" you should see "Install extension from file"→give that a tap tap taparoo (Happy Gilmore reference to lighten the mood 🤡)→select the previously created XPI file

• Step 6 = PROFIT!

💰💰💰

* I may have actually selected the .zip file converted from the extension CRX, but "conversion" in this case simply entails renaming the CRX file (i.e., change ".crx" to ".zip"). I doubt it makes a difference.

Edit - IDK why the link preview displays an add-on called WhatFont. The only hyperlink is for CRX Installer and I confirmed it redirects to its corresponding add-on store page ¯\_(ツ)_/¯

Edit 2 - I forgot to mention that this process will work to convert most extensions into properly functioning FF add-ons, but there will be the occasional outlier that doesn't function as well (or possibly at all) as a FF add-on due to differences in API calls. There are 1-2 that aren't available to both browsers and if the Chrome extension depends on one, functionality may suffer. Also, because FF is more permissive than Chrome in this regard, performing the conversion the other way around (from add-on→extension) is more likely to fail or result in a dysfunctional extension. Fortunately, due to there being a billion extensions in the CWS, most FF add-ons are already available to install.

Edit 3 - for a more automated approach, check out this handy tool created for the same purpose by u/hypeserver

Crossposted from https://www.reddit.com/r/firefox/comments/1jd5nlk/convert_chrome_extension_to_firefox_addon/

There are a number of FF versions and forks that this will work with, but I used FF Beta (I've also confirmed it to work with FF Nightly & Iceraven. Conversely, it did not work for Mull and iirc, it cannot be done using FF Standard Release/Stable)

• Step 1 - have the CRX file for the Chrome extension handy. There are countless Chrome extensions and FF add-ons that will extract it for you.

• Step 2 - install the CRX Installer add-on (or get the XPI file by whatever means) →Extensions→Click CRX Installer→click "Browse"→ select the CRX file*, which should result in the creation of an XPI file.

• Step 3 - go to Settings→About Firefox Beta (or Nightly, Iceraven, etc)→Tap the logo at the top of the "About" section until you see a toast message saying "Debug Menu enabled" (I think 5 taps)

• Step 4 - navigate to "about:config" → search "xpinstall.signatures.required" →tap "Toggle" so that it displays "False" (make sure there's no whitespace; copy exactly what's between the quotation marks or the search won't return the corresponding flag)

• Step 5 - go back to the main Settings screen, and now under the Advanced section, after "Extensions" you should see "Install extension from file"→give that a tap tap taparoo (Happy Gilmore reference to lighten the mood 🤡)→select the previously created XPI file

• Step 6 = PROFIT!

💰💰💰

* I may have actually selected the .zip file converted from the extension CRX, but "conversion" in this case simply entails renaming the CRX file (i.e., change ".crx" to ".zip"). I doubt it makes a difference.

Edit - IDK why the link preview displays an add-on called WhatFont. The only hyperlink is for CRX Installer and I confirmed it redirects to its corresponding add-on store page ¯\_(ツ)_/¯

Edit 2 - I forgot to mention that this process will work to convert most extensions into properly functioning FF add-ons, but there will be the occasional outlier that doesn't function as well (or possibly at all) as a FF add-on due to differences in API calls. There are 1-2 that aren't available to both browsers and if the Chrome extension depends on one, functionality may suffer. Also, because FF is more permissive than Chrome in this regard, performing the conversion the other way around (from add-on→extension) is more likely to fail or result in a dysfunctional extension. Fortunately, due to there being a billion extensions in the CWS, most FF add-ons are already available to install.

Edit 3 - for a more automated approach, check out this handy tool created for the same purpose by u/hypeserver

Crossposted from https://www.reddit.com/r/firefox/comments/1jd5nlk/convert_chrome_extension_to_firefox_addon/

There are a number of FF versions and forks that this will work with, but I used FF Beta (I've also confirmed it to work with FF Nightly & Iceraven. Conversely, it did not work for Mull and iirc, it cannot be done using FF Standard Release/Stable)

• Step 1 - have the CRX file for the Chrome extension handy. There are countless Chrome extensions and FF add-ons that will extract it for you.

• Step 2 - install the CRX Installer add-on (or get the XPI file by whatever means) →Extensions→Click CRX Installer→click "Browse"→ select the CRX file*, which should result in the creation of an XPI file.

• Step 3 - go to Settings→About Firefox Beta (or Nightly, Iceraven, etc)→Tap the logo at the top of the "About" section until you see a toast message saying "Debug Menu enabled" (I think 5 taps)

• Step 4 - navigate to "about:config" → search "xpinstall.signatures.required" →tap "Toggle" so that it displays "False" (make sure there's no whitespace; copy exactly what's between the quotation marks or the search won't return the corresponding flag)

• Step 5 - go back to the main Settings screen, and now under the Advanced section, after "Extensions" you should see "Install extension from file"→give that a tap tap taparoo (Happy Gilmore reference to lighten the mood 🤡)→select the previously created XPI file

• Step 6 = PROFIT!

💰💰💰

* I may have actually selected the .zip file converted from the extension CRX, but "conversion" in this case simply entails renaming the CRX file (i.e., change ".crx" to ".zip"). I doubt it makes a difference.

Edit - IDK why the link preview displays an add-on called WhatFont. The only hyperlink is for CRX Installer and I confirmed it redirects to its corresponding add-on store page ¯\_(ツ)_/¯

Edit 2 - I forgot to mention that this process will work to convert most extensions into properly functioning FF add-ons, but there will be the occasional outlier that doesn't function as well (or possibly at all) as a FF add-on due to differences in API calls. There are 1-2 that aren't available to both browsers and if the Chrome extension depends on one, functionality may suffer. Also, because FF is more permissive than Chrome in this regard, performing the conversion the other way around (from add-on→extension) is more likely to fail or result in a dysfunctional extension. Fortunately, due to there being a billion extensions in the CWS, most FF add-ons are already available to install.

Edit 3 - for a more automated approach, check out this handy tool created for the same purpose by u/hypeserver

I thought I couldn't post to https://sh.itjust.works/ for days when I could before. I kept getting this error "Language not supported" and found that changing it from English to "Unsupported" makes the submission go through.

Any ideas for why that is?

!

The Linux Ship of Theseus

Crossposted from: https://lemmy.ml/post/27387345

1. pick any distro and install it.
2. Then, without installing another distro over the top of it, slowly convert it into another distro by replacing package managers, installed packages, and configurations.

• System must be usable and fully native to the new distro (all old packages replaced with new ones).
• No flatpaks, avoid snaps where physically possible, native packages only.

Difficulties:

• Easy: pick two similar distros, such as Ubuntu and Debian or Manjaro and Arch and go from the base to the derivative.
• Medium: Same as easy but go from the derivative to the base.
• Hard: Pick two disparate distros like Debian and Artix and go from one to the other.
• Nightmare: Make a self-compiled distro your target.

Clarifications

• chroot, dd, debootstrap, and partition editors that allow you to install the new system in an empty container or blanket-overwrite the old system go against the spirit of this challenge.
• These are very useful and valid tools under a normal context and I strongly recommend learning them.
• You can use them if you prefer, but The ship of Theseus was replaced one board at a time. We are trying to avoid dropping a new ship in the harbor and tugging the old one out.
• It may however be a good idea to use them to test out the target system in a safe environment as you perform the migration back in the real root, so you have a reference to go by.

The Linux Ship of Theseus

Crossposted from: https://lemmy.ml/post/27387345

1. pick any distro and install it.
2. Then, without installing another distro over the top of it, slowly convert it into another distro by replacing package managers, installed packages, and configurations.

• System must be usable and fully native to the new distro (all old packages replaced with new ones).
• No flatpaks, avoid snaps where physically possible, native packages only.

Difficulties:

• Easy: pick two similar distros, such as Ubuntu and Debian or Manjaro and Arch and go from the base to the derivative.
• Medium: Same as easy but go from the derivative to the base.
• Hard: Pick two disparate distros like Debian and Artix and go from one to the other.
• Nightmare: Make a self-compiled distro your target.

Clarifications

• chroot, dd, debootstrap, and partition editors that allow you to install the new system in an empty container or blanket-overwrite the old system go against the spirit of this challenge.
• These are very useful and valid tools under a normal context and I strongly recommend learning them.
• You can use them if you prefer, but The ship of Theseus was replaced one board at a time. We are trying to avoid dropping a new ship in the harbor and tugging the old one out.
• It may however be a good idea to use them to test out the target system in a safe environment as you perform the migration back in the real root, so you have a reference to go by.

The Linux Ship of Theseus

Crossposted from: https://lemmy.ml/post/27387345

1. pick any distro and install it.
2. Then, without installing another distro over the top of it, slowly convert it into another distro by replacing package managers, installed packages, and configurations.

• System must be usable and fully native to the new distro (all old packages replaced with new ones).
• No flatpaks, avoid snaps where physically possible, native packages only.

Difficulties:

• Easy: pick two similar distros, such as Ubuntu and Debian or Manjaro and Arch and go from the base to the derivative.
• Medium: Same as easy but go from the derivative to the base.
• Hard: Pick two disparate distros like Debian and Artix and go from one to the other.
• Nightmare: Make a self-compiled distro your target.

Clarifications

• chroot, dd, debootstrap, and partition editors that allow you to install the new system in an empty container or blanket-overwrite the old system go against the spirit of this challenge.
• These are very useful and valid tools under a normal context and I strongly recommend learning them.
• You can use them if you prefer, but The ship of Theseus was replaced one board at a time. We are trying to avoid dropping a new ship in the harbor and tugging the old one out.
• It may however be a good idea to use them to test out the target system in a safe environment as you perform the migration back in the real root, so you have a reference to go by.

3 years ago I needed a new computer and decided on an 16 inch M1 Macbook Pro, but did lots of overthinking about if I wanted to stick to it. I tried Asahi Linux didn't have any reasons at the time to use linux over macOS (but there was always the chance I might later), the build quality is 2nd to none, none of my Windows laptops lasted more than a few years.

3 years later, I've really been itching to switch to Linux. Two of several reasons: because its DEs are more customizable, it has better documented accessibility APIs if you want to make keyboard navigation software. I reinstalled Asahi Linux and really tried to make it my daily driver, but the lacks of apps would require me to dual boot: Photoshop and Roblox.

I researching again for computers closest to Macbook Pros but none of them come close to its build quality. I think it would be best for me to make my own desktop PC for linux. I don't think I'd fare well with another windows laptop brand.

3 years ago I needed a new computer and decided on an 16 inch M1 Macbook Pro, but did lots of overthinking about if I wanted to stick to it. I tried Asahi Linux didn't have any reasons at the time to use linux over macOS (but there was always the chance I might later), the build quality is 2nd to none, none of my Windows laptops lasted more than a few years.

3 years later, I've really been itching to switch to Linux. Two of several reasons: because its DEs are more customizable, it has better documented accessibility APIs if you want to make keyboard navigation software. I reinstalled Asahi Linux and really tried to make it my daily driver, but the lacks of apps would require me to dual boot: Photoshop and Roblox.

I researching again for computers closest to Macbook Pros but none of them come close to its build quality. I think it would be best for me to make my own desktop PC for linux. I don't think I'd fare well with another windows laptop brand.