home.social

Search

1000 results for “nobodyinperson”

  1. @nobodyinperson @realestninja Second on both counts here; #plaintextaccounting is the only way to fly. Any of #beancount, #ledger, or #hledger are decent choices which some tradeoffs for each, but the latter is my choice as well having tried the other two.

  2. Organising my :nixos: code and splitting out sharable things into a separate repo. Here for example is my package for (:forgejo: + :gitannex: support) with a couple of my patches applied:

    gitlab.com/nobodyinperson/yann

    > nix build --refresh gitlab:nobodyinperson/yannix#forgejo-aneksajo
    > result/bin/forgejo -v
    forgejo version 13.0.3-git-annex2 built with go1.25.4 : sqlite, sqlite_unlock_notify

  3. Organising my :nixos: #nix code and splitting out sharable things into a separate repo. Here for example is my package for #forgejoAneksajo (:forgejo: #forgejo + :gitannex: #gitAnnex support) with a couple of my patches applied:

    gitlab.com/nobodyinperson/yann

    > nix build --refresh gitlab:nobodyinperson/yannix#forgejo-aneksajo
    > result/bin/forgejo -v
    forgejo version 13.0.3-git-annex2 built with go1.25.4 : sqlite, sqlite_unlock_notify

  4. Organising my :nixos: #nix code and splitting out sharable things into a separate repo. Here for example is my package for #forgejoAneksajo (:forgejo: #forgejo + :gitannex: #gitAnnex support) with a couple of my patches applied:

    gitlab.com/nobodyinperson/yann

    > nix build --refresh gitlab:nobodyinperson/yannix#forgejo-aneksajo
    > result/bin/forgejo -v
    forgejo version 13.0.3-git-annex2 built with go1.25.4 : sqlite, sqlite_unlock_notify

  5. Organising my :nixos: #nix code and splitting out sharable things into a separate repo. Here for example is my package for #forgejoAneksajo (:forgejo: #forgejo + :gitannex: #gitAnnex support) with a couple of my patches applied:

    gitlab.com/nobodyinperson/yann

    > nix build --refresh gitlab:nobodyinperson/yannix#forgejo-aneksajo
    > result/bin/forgejo -v
    forgejo version 13.0.3-git-annex2 built with go1.25.4 : sqlite, sqlite_unlock_notify

  6. Organising my :nixos: #nix code and splitting out sharable things into a separate repo. Here for example is my package for #forgejoAneksajo (:forgejo: #forgejo + :gitannex: #gitAnnex support) with a couple of my patches applied:

    gitlab.com/nobodyinperson/yann

    > nix build --refresh gitlab:nobodyinperson/yannix#forgejo-aneksajo
    > result/bin/forgejo -v
    forgejo version 13.0.3-git-annex2 built with go1.25.4 : sqlite, sqlite_unlock_notify

  7. My very first programming projects when I started self-teaching around 15 years ago were about accounting. I was unhappy with keeping track of expenses in a physical notebook, and the spreadsheet I made was also very limited. And existing solutions like felt too weird for my use case and its budgeting/forecasting approach was also an especially bad experience. After several funny PHP-based approaches I eventually made simbuto, the simple budgeting tool.

    gitlab.com/nobodyinperson/simb

  8. Looking for a PDF viewer allowing me to specify an arbitrary amount of of rows/columns to view a PDF. tops out at 8. Weirdly, in the source code¹ a maximum of 10 is set. But even recompiling² with it patched to 20 still only 8 are allowed. So there has to be something going on in the background. 🤷

    Any other recommendations? I want to scroll through *many* PDF pages next to each other and also make an overview screenshot (yes pdfnup...)

    ¹invent.kde.org/graphics/okular
    ²gitlab.com/nobodyinperson/nixc

  9. @rasterweb @lemgandi Nice! For organic shapes, #sdfCAD is quite capable as it's sdf-based. One can do pretty cool smoothing with it, stuff you can only dream of in mainstream CAD software.

    gitlab.com/nobodyinperson/sdfc

  10. @rasterweb @lemgandi Nice! For organic shapes, is quite capable as it's sdf-based. One can do pretty cool smoothing with it, stuff you can only dream of in mainstream CAD software.

    gitlab.com/nobodyinperson/sdfc

  11. @rasterweb @lemgandi Nice! For organic shapes, #sdfCAD is quite capable as it's sdf-based. One can do pretty cool smoothing with it, stuff you can only dream of in mainstream CAD software.

    gitlab.com/nobodyinperson/sdfc

  12. @rasterweb @lemgandi Nice! For organic shapes, #sdfCAD is quite capable as it's sdf-based. One can do pretty cool smoothing with it, stuff you can only dream of in mainstream CAD software.

    gitlab.com/nobodyinperson/sdfc

  13. @rasterweb @lemgandi Nice! For organic shapes, #sdfCAD is quite capable as it's sdf-based. One can do pretty cool smoothing with it, stuff you can only dream of in mainstream CAD software.

    gitlab.com/nobodyinperson/sdfc

  14. @nobodyinperson been using it as a #zathura alternative, when I'm forced to use Windows. Works great

  15. @nobodyinperson I have not published with @plosclimate but with @PLOS (#PLOSOne), so can't answer your question directly. However, some experience may transfer from PLOS to PLOS. I wouldn't hesitate to work eight them again. It's open and really multidisciplinary which are two big pluses for me. Only bad experience was the time it took them to fix a table formatting error they've introduced (something like 2 years...) but that was pretty minor.

  16. Had to switch back to base C++ #nix from #lix to package :hledger: #hledger's prebuilt release version, because lix still has an annoying builitins.fetchTarball bug¹ that prevents using tarballs that just contain a bunch of files without an extra single directory at the top level. (As you know, tarballs only EVER contain a top-level directory and never just a bunch of files, right?). In #cppnix it's already fixed.

    ¹git.lix.systems/lix-project/li
    ²github.com/NixOS/nix/pull/1119
    ³gitlab.com/nobodyinperson/nixc

  17. Had to switch back to base C++ from to package :hledger: 's prebuilt release version, because lix still has an annoying builitins.fetchTarball bug¹ that prevents using tarballs that just contain a bunch of files without an extra single directory at the top level. (As you know, tarballs only EVER contain a top-level directory and never just a bunch of files, right?). In it's already fixed.

    ¹git.lix.systems/lix-project/li
    ²github.com/NixOS/nix/pull/11195
    ³gitlab.com/nobodyinperson/nixc

  18. Had to switch back to base C++ #nix from #lix to package :hledger: #hledger's prebuilt release version, because lix still has an annoying builitins.fetchTarball bug¹ that prevents using tarballs that just contain a bunch of files without an extra single directory at the top level. (As you know, tarballs only EVER contain a top-level directory and never just a bunch of files, right?). In #cppnix it's already fixed.

    ¹git.lix.systems/lix-project/li
    ²github.com/NixOS/nix/pull/1119
    ³gitlab.com/nobodyinperson/nixc

  19. Had to switch back to base C++ #nix from #lix to package :hledger: #hledger's prebuilt release version, because lix still has an annoying builitins.fetchTarball bug¹ that prevents using tarballs that just contain a bunch of files without an extra single directory at the top level. (As you know, tarballs only EVER contain a top-level directory and never just a bunch of files, right?). In #cppnix it's already fixed.

    ¹git.lix.systems/lix-project/li
    ²github.com/NixOS/nix/pull/1119
    ³gitlab.com/nobodyinperson/nixc