~toastal

Eastern Thailand

https://toast.al

Pronouns: he/him | เขา​ | ລາວ Pronunciation: [ˈtʰo̞stɫ̩]

I do remote front-end dev & incidental travel.

PureScript | JavaScript | Dhall | Nix | Nickel | OCaml

Wishes for SourceHut: reStructuredText support

Trackers

~toastal/github-less-social

Last active 1 year, 7 months ago

~toastal/purescript-blurhash

Last active 2 years ago

~toastal/sugilite256

Last active 2 years ago

~toastal/purescript-web

Last active 2 years ago

~toastal/purescript-emitters

Last active 2 years ago

~toastal/dhall-webmanifest

Last active 2 years ago

~toastal/dhall-contribute-json

Last active 2 years ago

~toastal/purescript-halogen-donut

Last active 2 years ago

#141 Go version bump? a month ago

Comment by ~toastal on ~delthas/senpai

#141 Go version bump? a month ago

Comment by ~toastal on ~delthas/senpai

Additionally there are some log lines like: github.com/godbus/dbus/v5@v5.1.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod

#141 Go version bump? a month ago

Ticket created by ~toastal on ~delthas/senpai

I’m getting errors trying to bump Nix where dependencies are apparently using features from Go 1.18+, but the go.mod file is set to 1.16. Should the Go version here be set to match? (Not a Go user, just trying to help maintain the project for Nixpkgs)

#131 rm `flake-utils` from flake.nix 5 months ago

Ticket created by ~toastal on ~soywod/pimalaya

If you’re just going to call forEach this can be inline in 1–7 lines of Nix codes & you can remove an entire dependency. Is the project actually testing those platforms? Does the toolset actually support more than Numtide’s default set (such as 32-bit Linux being supported by many compilers)?

#98 Too long JSON breaks CLI calls 6 months ago

Ticket created by ~toastal on ~soywod/pimalaya

If the JSON response for folders is too long, the assumption is that Neovim breaks the response into multiple parts which don’t parse.

E474: ASCII control characters cannot be present inside string: ^@desc":"Extens
ion(\"\\\\HasNoChildren\")"}]

#himalaya-vim

  • Wait for EOF before parsing responses.

#81 Improve datetime format 8 months ago

Comment by ~toastal on ~soywod/pimalaya

That sounds reasonable.

#81 Improve datetime format 8 months ago

Comment by ~toastal on ~soywod/pimalaya

Version is 0.7.1 from Nixpkgs unstable. RFC 3339 to ISO 8601 specifies that you can drop the T which I find to be the bit that brings the most clutter (followed by the time zone offset), but otherwise it is readable. I think in general the user would expect either something universal or tailored to the OS & environment.

#81 Improve datetime format 9 months ago

Ticket created by ~toastal on ~soywod/pimalaya

In both the CLI and Neovim plugins I‘m getting the wrong date. A message sent to me this hour reads 17/05/2023 11:36 for which I expect withLC_TIME=en_DK.UTF-8 (ISO 8601) to be 2023-05-17 18:36. I can live with the UTC time as I keep two clocks in my OS‘s bar, but I cannot do little-endian date formats. They cause me too much confusion and do not match user expectations. My other OS locale flags are en_US.UTF-8 which is middle-endian, and while less preferable than big-endian formats, I have an intuition for it.

#107 How to fix the date format? 1 year, 3 months ago

Comment by ~toastal on ~taiite/senpai

Yes, some option for big endian dates to meet expectations.

#107 How to fix the date format? 1 year, 3 months ago

Comment by ~toastal on ~delthas/senpai

Yes, some option for big endian dates to meet expectations.