#linuxcnc-devel Logs

Jun 06 2022

05:56 AM -!- #linuxcnc-devel mode set to +v by ChanServ
12:53 PM smoe: I somehow keep translating. How do we want to spell ".ini"-file - we have Ini-file, INI-file and ini-file?
01:01 PM cradek: because the file's extension is case sensitive, I think "ini" should always be lower case
01:01 PM cradek: Ini and INI would be different files and they wouldn't work
01:07 PM smoe: @cradek, thanks, I agree. What about a leading dot? We have one for a .exe, too, right?
01:08 PM smoe: This has all some painful roots in MS DOS, but, well, ...
01:11 PM silopolis[m]: Thing is that it's most often used like a noun refenring to `.ini` file*s*
01:13 PM smoe: Yes, and it is presumed that there is only one .ini file - I actually like those backticks.
01:14 PM smoe: .ini file ok with everyone? In German I would have it as .ini-Datei (with a hyphen) but English should go without, right? You see it in all flavors in our documentation, so we can have a free pick.
01:15 PM silopolis[m]: I believe we should refer to 'INI config', unless we are specifically refering to a special `file.ini`
01:16 PM silopolis[m]: smoe: Is that a requirement/limitation ? Can't one have several, ie split config in several ?
01:19 PM smoe: Not a requirement. But the glossary should decide on some sort of reference. And we should not have variants within the same paragraph (which we have now). I once had all occurrences of G-code in the documentation changed. And of LinuxCNC. Personally, I dislike it when such easy fixes of a documentation are not done, but, admittedly, there are more
01:19 PM smoe: important bits to work on.
01:24 PM silopolis[m]: I'm all with with you again !
01:55 PM silopolis[m]: OK so, AFAIU the runtime script (!), it accepts only one INI file as parameter, but supports #INCLUDE statements. So, the 'INI config' can indeed be built out of several files, and should be referenced in a global/generic way.
01:55 PM silopolis[m]: My proposal would be to add an 'INI configuration' entry in the glossary and replace any reference to "INI file(s)" or ".INI" or any other fashion.
02:17 PM silopolis[m]: Also Wikipedia seem to agree with the capitalized notation https://en.wikipedia.org/wiki/INI_file
02:18 PM smoe: Hm. Darn.
02:18 PM smoe: Another one is HAL - all in caps?
02:21 PM silopolis[m]: Yes, and I'd apply the same solution and cure
02:22 PM pcw-home: HAL in all caps makes sense since its an acronym not so sure about INI but I think anything with a "." is referencing a file name and should be .hal or .ini
02:22 PM silopolis[m]: Gonna be another task 😅
02:23 PM CaptHindsight[m]: pcw-home: I can confirm that your VHDL does work in Vivado
02:26 PM silopolis[m]: pcw-home: Indeed, as soon as a specific file name is specified it should turn into `filename.ext`
02:26 PM silopolis[m]: But I think we should remove any ref to specific files that are not common to ALL configs and instead refer to the type of config.
02:32 PM silopolis[m]: Acronyms should in fact be capitalized and "dotted", ie "H.A.L." instead of "HAL", but I believe we have some tradition in IT land to turn them into nouns when they become software(s) component(s), dropping the dots in the process.
02:36 PM pcw-home: CaptHindsight The VHDL should be portable to almost any toolchain (- Xilinx specific hardware support like DPLLs etc)
02:37 PM pcw-home: It was pretty easy to port it to Efinix's toolchain ( main difference was External I/O Tri-state bus definitions )
08:27 PM -!- #linuxcnc-devel mode set to +v by ChanServ
10:24 PM linuxcnc-build: build #6492 of 1402.rip-wheezy-rtpreempt-i386 is complete: Failure [4failed garbage-collect git repo] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1402.rip-wheezy-rtpreempt-i386/builds/6492 blamelist: Peter Wallace <pcw@mesanet.com>
10:59 PM linuxcnc-build: build #8836 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/8836 blamelist: Peter Wallace <pcw@mesanet.com>