Skip to content

Conversation

@pyrmont
Copy link
Contributor

@pyrmont pyrmont commented Jan 16, 2026

As explained in the docstring to nfnl.core/rand:

You must have a random seed set before running this: (math.randomseed (os.time))

At present, Conjure does not do this and as a result the sponsor message is not selecting a random sponsor (unless the user happens to call math.randomseed within their Neovim environment).

This commit adds the call recommended in the docstring.

As explained in the docstring to `nfnl.core/rand`:

> You must have a random seed set before running this:
> `(math.randomseed (os.time))`

At present, Conjure does not do this and as a result the sponsor message
is not selecting a random sponsor (unless the user happens to call
`math.randomseed` within their Neovim environment).

This commit adds the call recommended in the docstring.
@Olical
Copy link
Owner

Olical commented Jan 16, 2026

I've thought about this a few times, my only concern is what if someone wants to set their own random seed for some other thing, I worry this will conflict or need configuring. But maybe until that happens, we just do this and see if there's any issues. I'll take a look and merge over this weekend, thank you!

Copy link
Owner

@Olical Olical left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I'm okay with it, if people have issues with other tools we can always add config for this, but I suspect it's fine.

@Olical Olical merged commit 1c0af54 into Olical:main Jan 18, 2026
6 checks passed
@pyrmont pyrmont deleted the bugfix.random-sponsor branch January 18, 2026 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants