|
From: | GNU bug Tracking System |
Subject: | bug#47953: closed (fennel doesn't print version with -v) |
Date: | Sat, 29 Apr 2023 04:46:01 +0000 |
Your message dated Sat, 29 Apr 2023 00:45:45 -0400 (EDT) with message-id <alpine.DEB.2.21.2304290044370.331@marsh.hcoop.net> and subject line Re: bug#47953: fennel doesn't print version with -v has caused the debbugs.gnu.org bug report #47953, regarding fennel doesn't print version with -v to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 47953: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=47953 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: fennel doesn't print version with -v Date: Thu, 22 Apr 2021 10:39:48 -0400 (EDT) User-agent: Alpine 2.21 (DEB 202 2017-01-01) Hi Guix,From the fennel man page:-v, --version Print the version number and exit However, only the long options seems to work: jackhill@alperton ~ [env]$ fennel --version Fennel 0.8.1 on Lua 5.3 jackhill@alperton ~ [env]$ fennel -v runtime error: -v: No such file or directory stack traceback: [C]: in function 'assert' ...tore/lgaycpzwfair15b4m1lvzjim0gv3l0gp-profile/bin/fennel:3630: in function ? [C]: in function 'xpcall' ...tore/lgaycpzwfair15b4m1lvzjim0gv3l0gp-profile/bin/fennel:4036: in function ? [C]: in ?Other short options, like -h, do work. This isn't that annoying a problem, but I wonder if it presents some problem with out fennel package.I'm using Guix commit 58d96474bdc355619890f85bf6095a79074f6ee8 Best, Jack
--- End Message ---
--- Begin Message ---Subject: Re: bug#47953: fennel doesn't print version with -v Date: Sat, 29 Apr 2023 00:45:45 -0400 (EDT) User-agent: Alpine 2.21 (DEB 202 2017-01-01) On Thu, 22 Apr 2021, Jack Hill wrote:This is an upstream bug in fennel. It was fixed today, but not released yet [0]. It seems like a minor annoyance, so I think it's okay to wait until the next release.[0] https://git.sr.ht/~technomancy/fennel/commit/904e3ee165d097411bab599b9378895695629b70And indeed it was fixed, both upstream and in Guix! We just neglected to close this issue, so I'm doing that now, yay!Best, Jack
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |