• 0 Posts
  • 15 Comments
Joined 8 months ago
cake
Cake day: November 21st, 2023

help-circle
  • Ekky@sopuli.xyztoAnimemes@ani.social:D‎
    link
    fedilink
    English
    arrow-up
    9
    ·
    14 days ago

    You can fix that by setting “User Settings->APP SETTINGS->Chat->Automatically convert emoticons in your messages to emoji” to “OFF”

    You can still make emojis with “:smile:”, but why would you? ¯\_(ツ)_/¯




  • People who rely too heavily on autocorrect do already now cause misunderstandings by writing something they did not intend to.

    I had a friend during uni who was dyslectic, and while the words in his messages were written proper you still had to guess the context from the randomly thrown together words he presented you with.

    Now that we can correct not only a single word or roughly the structure of a sentence, but instead fabricate whole paragraphs and articles by providing a single sentence, I imagine we will see a stark increase in low-quality content, accidental false information, and easily preventable misunderstandings - More than we already have.







  • Sure, I can tell you what little i know. The best, but probably also toughest, place to start is likely the ArchLinux forums.

    Wine handles the lifting. Proton, Glorious Eggroll (GE), etc. can be seen as content packs, packing some additional tools and dependencies commonly found in gaming. There exist a lot of other “flavours” of Wine, all with their own specialization, though pure Wine is usually fine for most non-gaming and non-Peripheral (flashing hardware) cases.

    The most usefull terms I’ve come across when tinkering are:

    • Runner: Location of the specific wine installation. Isn’t actually named “runner”.
    • Prefix: Location of the Wine-OS-layer in which the magic will happen. Don’t use the default when tinkering, and clear it when wanting to make a clean attempt.
    • wine: Usually found in <runner>/bin/wine. It’s the default way to start executables using wine.
    • wineconsole: Found next to wine, opens the executable in a cmd-like console usefull for running .bat files.
    • winecfg: Also found next to wine, default configurator for wine, handles dlls, registry, and general settings.
    • winetricks: A configuration tool which provides an easy way to install the most well-known dependencies and just functions as a nice “more powerful winecfg”.
    • Once Wine is running, C:\\ will be the prefix, and Z:\\ is your Linux computer. You can usually install/run things outside the prefix C:\\, but sometimes it just won’t work, so better try moving it inside if it just don’t wanna.

    Running an exe, be it the program you want to get running or a dependency, in the terminal looks something like:

    WINEPREFIX="/path/to/my/prefix" "/path/to/runner/bin/wine" "/path/to/executable.exe"

    And the neat part is, that to run wine using, say, Proton-GE, you’d just go:

    WINEPREFIX="/path/to/my/prefix" "/home/$USER/.local/share/Steam/compatibilitytools.d/GE-Proton8-25/files/bin/wine" "/path/to/executable.exe"

    If you want to just use your default WINE installation, you’d leave out the runner part, and just go:

    WINEPREFIX="/path/to/my/prefix" "/path/to/executable.exe"

    Now, that’s all good and dandy, but who in their right mind uses the terminal anymore?

    Bottles, Playonlinux, Lutris, Heroic, and now Steam too (kinda) are launchers which pack some quality of life tools to make creating, running, and tinkering with Wine easier. What launcher you prefer is totally up to you, as they all come with their own ups and downs. Like I stated before, I like Lutris’ Wine runtime packs, but their interface confused me the first time I tried it, so probably not great for starters.

    Heroic is nice to look at and simplistic, It doesn’t have a whole bunch of customization options, but it has easy-to-access shortcuts to winetricks and winecfg.

    I’ve tried Bottles, and while they provide some appreciated commonly-used dependencies and their user interface is pleasant to look at, they make it unnecessarily difficult to properly tinker with Wine, and for some reason they have to hide and rename everything? Bottles is probably fine for most people, especially for beginners who don’t plan on diving far, but I just couldn’t get comfortable with it.

    If you’re tinkering with WINE (or even Proton) using Steam, you’ll probably have a bad time, but they do provide a good collection of games which work out-of-the-box. Not useful for much else wine-related, besides providing Proton and a massive boost to Wine.

    At last: Wine logs are weird. I’ll need to learn to read them at some point, but they are so filled with errors and warnings that just naturally exist but don’t attribute to your specific problem that they are borderline useless if you’re not 100% familiar with them. And don’t expect two computers to run an executable the same way just because they use the same Wine runner and Prefix. Wine’s no virtual box.

    If anyone knows more, or if I said something factually wrong, then please feel free to correct me.

    == Regarding SketchUp ==

    I’m not sure how far you got and I’m not sure about your skill level, so please excuse me if you already got this far, but according to WineHQ you’ll need to run a rather lengthy command to get it working. By szilveszter:

    Thanks for the comments and help. The program can be installed and used as follows: (1) Installation All selectable languages must be enabled. Even so, an ‘invalid handle’ message is generated, but the installation is completed. (2) Starting the program with NVIDIA graphics processor: __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia WINEPREFIX="/DATA/prg/sketchup_2023" WINEESYNC=1 WINEARCH="win64" /opt/wine-staging/bin/wine64 "/DATA/prg/sketchup_2023/drive_c/Program Files/SketchUp/SketchUp 2023/SketchUp.exe" /DisableRubyAPI

    So in other words:

    1. Download Wine-staging (this can be its own can of worms).
    2. Install by first creating the prefix directory, and the running:

    $ WINEPREFIX="/home/$USER/<mysketchupwineprefix>" "</path/to/wine-staging-runner/bin/wine>" "</path/to/sketchup_setup.exe>"

    Please change the <example> text, and respect the instructions of szilveszter, errors are to be expected.

    1. Run the executable using their command, but change /opt/wine-staging/bin/wine64 to where your wine-staging runner is located, and "/DATA/prg/sketchup_2023/drive_c/Program Files/SketchUp/SketchUp 2023/SketchUp.exe" to where you decided to install sketchup. Wine-staging might already be included in regular wine, so with some luck you might be able to use your computers default runner.

    As per szilveszter’s instructions, I think it’s wise to install Sketchup inside the prefix.

    Also, it appears to be only mostly working, so expect errors and limitations. :(



  • +1

    I personally started by playing around with Ubuntu, but it just didn’t feel intuitive coming from windows.

    Went over to Mint, and was very happy,especially with drivers and gaming. I even fully removed my windows installation during this period. Having gained a better understanding of Linux, I have now moved on again.

    The only real drawback of Mint is not natively supporting KDE Plasma (as they did before). And yes, you can just install it yourself, but I wouldn’t recommend a beginner who barely knows how to install Linux to attempt such an endevour.

    One word of advice to OP: don’t wait till you can’t use Windows anymore. Start by dual booting and getting a hang of Linux, but with windows at the ready for any tasks you cannot yet do/feel comfortable doing on Linux. As you get a better hold of Linux, you should naturally begin to use Windows less.

    The worst thing someone can do, is to jump OS without any backup or safety net. Learning to use Windows took a long time, getting a hang of new concepts and getting used to an alien environment. Now, already having a hang of “computers” (Windows), we have digital needs and expectations (E-Mail, gaming, etc.) which will need fulfilling, but many seem to forget that a different OS means different ways of doing our daily tasks and different challenges to handle.

    And yes, “different”, because Windows definitely also comes with it’s own unique challenges, you just don’t see them as much when having gotten used to them.


  • We just had a “once every 100-years” storm surge last fall. Many islands in the southern Danish archipelago were not properly prepared and saw their dikes flood (including my birthplace, and yes, I know others have so much worse conditions, but we are/were rather well protected here in the Baltic sea). There was some damage, not least to some endangered species habitats that the Copenhagen zoo was keeping, and many islands will have to seek an exception with the cultural preserverance agency to be allowed to repair their dikes.

    On the bright side, the flood has seen to the fire and flood equipment being checked, meaning that we now have proper portable flood pumps. Even though they at first sent pumps too large to be loaded onto the ferry. Derp. :)

    Hopefully this will not repeat for another 100 years, but many of us islanders are not so sure with global warming, so we might have to evacuate and give up the smaller islands within my lifetime if such floods become a common occurance.

    And of course we could just replace our 200+ year old dirt and stone dikes and less old water locks with modern concrete and steel dikes, but I think we’ll have a hard time convincing the state to put in the required resources for a <10 people community. Even Ærø, one of the larger islands with a population of ~6000, has had problems with dike maintenance.

    I guess my advice would be the normal stuff: keep some bottled water and long term food that can be eaten cold, keep a battery bank for your phone, blankets and a bucket, know how to get to your rooftop when in the attic (will hopefully never be necessary in the baltic sea), have a good pair of waders and a good flashlight. And of course, know how to quickly contact any other inhabitants in your local area if necessary.