I agree that it isn’t very clear. I took a look at the Lua mailing list, and although there isn’t a clear yes or no regarding making changes, portability and avoiding undefined behavior was mentioned, so maybe it’s better to leave it as is. I only found one thread in that mailing list, so it doesn’t look like a common need.
I’m going to try to work around it in the Awesome configuration, or I may build Lua myself with the additional specifiers to test it. I can’t find any other threads related to this in the ports mailing list, so this is probably the best option. > On Jan 22, 2017, at 4:57 PM, Jonathan Gray <j...@jsg.id.au> wrote: > > On Sun, Jan 22, 2017 at 02:53:15AM -0600, Ricky Cintron wrote: >> Hello all, >> >> Apologies if I???m mistaken, but it appears that the Lua packages are built >> with the default conversion specifiers for strftime, which are defined in >> loslib.c (if I searched correctly). Unfortunately these do not include %l, >> %k, %s, %v an %+, which are supported by OpenBSD???s strftime. This leads to >> an error when trying to use %l to format Awesome Window Manager???s panel >> clock. >> >> Would it be possible to begin building the Lua packages with support for >> these conversion specifiers, or has this option already been considered and >> not implemented for a reason? >> >> Thanks. > > lang/lua/5.1 and lang/luajit don't have a whitelist for format options, > lang/lua/5.2 and lang/lua/5.3 do. It isn't clear if the intent is for > LUA_STRFTIMEOPTIONS to be changed to include all of the valid options or > if it is limited to prevent portability problems.
