sorted by: new top controversial old
Can I ignore flatpak indefinitely? in c/linux@lemmy.ml
[–] 6 points 1 year ago

So far I have also completely ignored them. From what I understand they technically allow you to install old versions of software, potentially having multiple at the same time. This could come in a clutch when working with stuff like Godot or Blender where constantly upgrading to the latest version would cause issues on bigger projects. This is the only thing I can see myself using them for, at least in the near future.

  • permalink
  • fedilink
  • source
    •
    Tip: sudoedit often overlooked as an alternative to sudo vim in c/linux@lemmy.ml
    [–] 2 points 2 years ago*

    Meanwhile, a reverse vim enjoyer like myself, using micro to edit any file running as my user. If it requires root to write, it will simply elevate the permissions for that operation when I press Ctrl+S, asking for password if needed.

    Same idea with VSCodium, but via GUI polkit prompt.

    Life is good when you don't hjkl ^_^

  • permalink
  • fedilink
  • source
    •
    Tell one thing that you miss after switching from another OS to Linux. in c/linux@lemmy.ml
    [–] 16 points 2 years ago

    I honestly loved some of the default Windows apps, like Notepad, Paint and believe it or not, the default file manager. I find that most file explorers on Linux can't strike a good balance between simplicity and the amount of features.

    Thankfully (or not, if you use Windows) they started enshittifying each and every one of them, so there's nothing to miss any more.

  • permalink
  • fedilink
  • source
    •
    Give Up GitHub - Software Freedom Conservancy in c/foss@beehaw.org
    We don't need more Wayland Compositors in c/linux@lemmy.ml
    Wayland support for the 565 release series in c/linux@lemmy.ml
    [–] 5 points 2 years ago (2 children)

    reluctantly accepting the standard that was developed without them

    Not with everything, Nvidia stood still on explicit sync, in that case it were the idiots at Freedesktop that were massively blocking Wayland's progress, trying to force an inferior technology, which Nvidia did not want to implement.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • This Week in Plasma: Everything You Wanted and More in c/linux@lemmy.ml
    This week in Plasma: all screens, all the time in c/linux@lemmy.ml
    Zed on Linux is out! in c/linux@lemmy.ml
    Libadwaita: Splitting GTK and Design Language in c/linux@lemmy.ml
    42 key points of the secret #EUGoingDark surveillance plan for the new EU Commission in c/privacy@lemmy.ml
    It's time to move to Linux - YouTube in c/linux@lemmy.ml
    1
    Lazy Lua - Extended standard library for Lua >=5.1 (gitlab.com)
    submitted 3 years ago* (last edited 3 years ago) by [M] to c/lua@programming.dev
    comment fedilink
     

    Lazy is a library that extends the standard Lua library.
    It exposes function modules such as math, string, table, etc.

    It's aimed to fill the gaps of Lua's standard libraries by providing functions such as math.round to round numbers, string.trim to remove leading and trailing white spaces from a string and many many many more.

    One important feature of Lazy is that the require path of modules is automatically resolved, which allows you to require the lazy library from virtually anywhere.
    For example the lazy folder may be located in the root of your project or any sub-directory. More so, upon setting your LUA_PATH correctly, lazy can be required anywhere from your PC without having to import it into your project. Please refer to the GitLab page for more information .

    Example usage:

    local lazy = require "lazy"

lazy.math.round(1234.5678, 2) --> 1234.57
lazy.os.capture("pwd") --> /home/name/projects/lua/lazy
lazy.string.split("Lua is amazing!", " ") --> { "Lua", "is", "amazing!" }
lazy.table.append({ "A" }, { "B" }, { "C" }, { "D" }) --> { "A", "B", "C", "D" }

    Contributions and requests are welcome :P

    2
    Community Rules and Guidelines (programming.dev)
    submitted 3 years ago* (last edited 3 years ago) by [M] to c/lua@programming.dev
    comment fedilink
     

    All the rules from this Lemmy instance apply.
    Additionally, please try to follow these community-specific rules:

    Rules

    1. Posts must relate to Lua

    All posts must be related to the Lua programming language.
    This also includes related and derivative projects, such as Luau or MoonScript.

    2. Use descriptive titles

    Your title should in short describe the contents. That applies to all kinds of posts, no matter whether you're showcasing a project, discussing a feature or asking for help.

    Examples of bad titles:

    • please help!
      ^ Doesn't provide any information about the post
    • How to rotate SENT?
      ^ Should also information about API and ideally expand SENT which is a rather niche acronym
    • request.lua
      ^ Could provide a short description of the library

    Examples of good titles:

    • [Help] Lua errors when using string.format with the %p flag
    • How to rotate a Scripted Entity in Garry's Mod when spawned?
    • request.lua - Lua >=5.1 library to simplify HTTP requests

    Please note that there are no strict rules related to tagging posts (eg. including [Help] or [Roblox] in the title), but they are very welcome nonetheless.

    3. Provide reproduction code

    When asking for help, you should provide a reproduction code whenever applicable. This doesn't mean that you should copy and paste your whole project or script into the post, in fact the opposite. Try to isolate the issue you're facing on your own and only include the code needed to reproduce it.

    A screenshot or image of the code is never valid. Additionally the code should be provided using the following Markdown syntax:

    ```lua
<your code goes here>
```

    4. Information about environment

    When asking for help, and ideally releasing a project, you should include as much information as possible about the target environment.
    Most important thing is the Lua API in use, that means the video game, game engine, framework, library, etc.
    Other information such as Lua version, environment variables, operating system, etc. may be useful as well.

    Posts not following the rules may be deleted without prior notice.
    Repeated offenders may be issued a warning and banned.

    If you do not agree with the rules or statements made here, please discuss your issue in the comment section, I'm sure something can be done about it.

    Moderation

    If you want to help and moderate this community, please message leave a comment under this post or contact me in any other way.

    view more: next ›