#linuxcnc-devel Logs

May 07 2022

10:23 AM -!- #linuxcnc-devel mode set to +vvvv by tungsten.libera.chat
11:40 AM linuxcnc-build: build #1953 of 1660.rip-buster-python3 is complete: Failure [4failed configuring] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/1953 blamelist: Hans <hansunzner@gmail.com>, Hans Unzner <hansunzner@gmail.com>
11:41 AM linuxcnc-build: build #2354 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed configuring] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/2354 blamelist: Hans <hansunzner@gmail.com>, Hans Unzner <hansunzner@gmail.com>
11:43 AM silopolis[m]: woops seb_kuzminsky builbot needs latest po4a version 😕
12:07 PM hansu: hi
12:13 PM hansu: Good idea silopolis[m] to format the INSTALL file.
12:13 PM hansu: But .adoc put into someones mind (at least in mine) that it is a file that is part of the documentation that shows up as html and pdf. What do you think if we use .md files for those which are intended to be read as they are, like typically README.md? pere
12:13 PM hansu: Maybe this could be something for the style guide (if I am not the only one who is thinking so)...
12:15 PM silopolis[m]: hansu: ain't no difference between reading raw adoc or md
12:16 PM silopolis[m]: as we selected adoc as formatted text format for the docs, I'm in favour of using it everywhere
12:16 PM silopolis[m]: plus, GH also formats it nicely
12:17 PM pere: whanI believe it is a very bad idea to associate format with expected render format. it is better to use one format everywhere, to increase the chance of those editing remembering the correct format, and to allow cut-n-paste and includes between renderings.
12:18 PM pere: s/wahnI/hansu: I/
12:20 PM hansu: Okay, was just an idea as I associate .adoc files which are a source to be converted into html and pdf and .md are used as they are.
12:24 PM silopolis[m]: md are originally made to be converted too, we just got used to read them raw 🙂
12:24 PM silopolis[m]: hansu: about the callouts
12:24 PM * silopolis[m] uploaded an image: (59KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/ANUDnpCvbEusQceIjRRLCCHx/image.png >
12:26 PM * silopolis[m] uploaded an image: (62KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/YMHJyfaQQCrLqeCFljOPzdfR/image.png >
12:26 PM hansu: What is so special for these callouts? It would be the same result if you just write (1) and so on
12:26 PM silopolis[m]: I prefer the first one
12:27 PM silopolis[m]: Well, not sure, depends how it's converted to docbook too
12:27 PM hansu: then I would change the order, first the numbered items, then the code snippet
12:28 PM silopolis[m]: as far as HTML is concerned, seems to be quite the same
12:34 PM silopolis[m]: <hansu> "then I would change the order..." <- It's a very standard way to document a sequence of commands or chunk of code, found in piles of howtos and books...
12:35 PM * silopolis[m] uploaded an image: (60KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/YvFqHjhVsldebINGUQHhWWCN/image.png >
12:35 PM silopolis[m]: like this ?
12:35 PM hansu: hmm yes but looks ugly
12:37 PM silopolis[m]: because it was nice in the beginning !
12:37 PM hansu: Yours is not bod in general, but the additional (optional) description is being read like normal text after the code block. But it is more like a footnote. Or a small headline could help to separate this.
12:38 PM hansu: *bad
12:41 PM pere: hansu: removal patch rebased.
12:42 PM hansu: toppen!
12:45 PM silopolis[m]: pere, and others btw, can we have your opinion on our formating dilema pls ?
12:46 PM pere: what is the formatting dilema?
12:46 PM silopolis[m]: see pictures above
12:47 PM pere: what is the dilema?
12:49 PM silopolis[m]: I find the first simple callouts version to be slick and clear, but hansu finds it misleading and hugly
12:56 PM JT-Shop: the note would be confusing to a newbee
12:57 PM JT-Shop: You should not that they are building a RIP and not installing emc with that instructions
12:58 PM JT-Shop: I understand it well but a chap taught me this morning that just because you understand it doesn't mean a newbee will
12:58 PM pere: why fix it there, what about rewriting the script to detect csh and reject configure run if so?
12:59 PM JT-Shop: that makes more sense if csh is becoming common, but I've never heard of it
01:00 PM pere: it is/was the default shell on solaris, if I am not mistaken.
01:00 PM pere: It is quite rare these days.
01:00 PM JT-Shop: you can build linuxcnc on solaris?
01:01 PM JT-Shop: I would not even worry about it or confuse newbee's with it
01:02 PM * JT-Shop wanders inside for a nap
01:03 PM pere: JT-Shop: me neither. those running csh these days know what a mess they have stuck their feets into.
01:04 PM pere: <URL: https://www.in-ulm.de/~mascheck/various/whatshell/ > could detect if some bourne shell compatible version is used...
01:09 PM silopolis[m]: Then let's just drop the confusing note !
01:11 PM pere: my rule of thumb is to make sure the source is semantically correct, and leave esthetic improvements out of the source.
01:34 PM * silopolis[m] uploaded an image: (47KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/pkhxrSfrfSJvMFUToecAzZZF/image.png >
01:35 PM silopolis[m]: hansu: is that ok for you ?
01:37 PM silopolis[m]: I'm afraid that we loose semantic formating at docbook stage but...
01:38 PM silopolis[m]: also note that I have in mind to make good use of these callouts in the future...
01:39 PM silopolis[m]: My choice would be to leave it as pushed and remove the note, but you're the commiter...
04:23 PM hansu: Ok, leave it as it is
05:45 PM JT-Shop: pcw-home, is mesaflash ready to flash a 7i96s?
05:49 PM pcw-home: no
05:49 PM JT-Shop: ok, just checking
05:50 PM -!- #linuxcnc-devel mode set to +v by ChanServ
05:51 PM pcw-home: still needs work (reading bin file headers mainly ) I still have to make sure you cant corrupt a 7I96S with an old copy of mesaflash
05:52 PM pcw-home: I'm poking away at it a bit today
05:53 PM pcw-home: the way fallback works and the location of the fallback image are different
05:57 PM JT-Shop: anything I can do to help?
05:58 PM JT-Shop: my Mesa Configuration tool requires the latest version or newer now
06:03 PM pcw-home: Nah I just need to poke around and the header stuff now
06:04 PM pcw-home: (and also play with older versions of mesaflash to make sure they cannot break a 7I96S)
06:04 PM pcw-home: mesaflash was not written in a very safe way originally
06:05 PM pcw-home: a great example of this is the EEPROM size case statements with no error/bail if an unrecognized size was found
06:05 PM JT-Shop: ouch
06:07 PM pcw-home: the case statement falls through and a EEPROM location of 0 ends up being the default (causing pain and suffering with --write)
06:09 PM JT-Shop: I see that, I assume that's in eeprom.c
06:09 PM JT-Shop: no default:
06:09 PM pcw-home: This bit us when we had to upgraded to 32MBit EEPROMS due to availability issues last year
06:10 PM pcw-home: default should be bail out and complain...
06:10 PM JT-Shop: yup
06:11 PM pcw-home: I may poke at that also if i get the header stuff done
06:11 PM JT-Shop: ok, holler if you need another pair of eyes to look
06:13 PM pcw-home: OK need to learn a bit more about fgets now (does it stop on a null or just lf or both?)
06:14 PM JT-Shop: got some San Marzano tomato plants I started from seeds in the deck pots today
06:14 PM JT-Shop: I'll see what I can find out in the morning
06:14 PM Tom_L: end of line or end of file
06:14 PM Tom_L: or n-1
06:15 PM Tom_L: specified by number of characters to read
06:15 PM Tom_L: in C anyway
06:15 PM JT-Shop: mesaflash is C
06:15 PM JT-Shop: The C library function char *fgets(char *str, int n, FILE *stream) reads a line from the specified stream and stores it into the string pointed to by str. It stops when either (n-1) characters are read, the newline character is read, or the end-of-file is reached, whichever comes first.
06:16 PM * Tom_L bets jt is on the same page as i was :)
06:16 PM JT-Shop: lol
06:16 PM JT-Shop: On success, the function returns the same str parameter. If the End-of-File is encountered and no characters have been read, the contents of str remain unchanged and a null pointer is returned.
06:16 PM JT-Shop: If an error occurs, a null pointer is returned.
06:17 PM Tom_L: similar to fread
06:17 PM Tom_L: or fwrite going the other direction
06:18 PM -!- #linuxcnc-devel mode set to +v by ChanServ
06:18 PM Tom_itx: The fgets() function stores the result in string and adds a null character (\0) to the end of the string. The string includes the new-line character, if read. If n is equal to 1, the string is empty.
06:18 PM Tom_L: so it adds the null
06:21 PM * JT-Shop goes inside to check on the potstickers if they have been started or not
06:21 PM Tom_itx: so if you write it back you likely would write out n-1 char
06:21 PM Tom_itx: to exclude the null
06:21 PM Tom_itx: still alot like fread/fwrite
06:23 PM Tom_itx: https://quick-adviser.com/does-fgets-read-null/
06:24 PM Tom_itx: an empty result string = 1 (the added null)
06:38 PM pcw-home: yeah so reads to nl and includes nl in any case
07:18 PM CaptHindsight[m]: https://www.reddit.com/r/specializedtools/comments/ukigox/post_straightener/
10:44 PM Tom_L: fgets is different from fread in that fread _will_ read control, null and high-order characters