Re: [Emc-developers] Upcoming Sunday, 8 pm (EST, GMT+2) LinuxCNC Videoconference Aw: LinuxCNC Video Conference - call for vote on when this should happen

Hallo Steffen, deine Zeitangabe ist irgendwie widersprüchlich: "The Eastern Time Zone is also known as Eastern Standard Time (EST) falls mostly along the east coast of North America. Its time offset is −5 hours (UTC/GMT -5)" Ich würde da nochmal ne klarstellende Mail nachschieben ;-) Viele Gr

Re: [Emc-developers] Buildbots and Master branch

Thanks Andy! Am 08.04.25 um 12:13 schrieb Greg C: Thank you, Andy! On Apr 8, 2025, at 5:38 AM, andy pugh wrote: On Sat, 5 Apr 2025 at 22:24, wrote: What the heck is up with the Master branch? Seb's buildbot2 has stalled Feb 6 for master in both bookworm and bullseye. It was a combinatio

Re: [Emc-developers] Translation / Docs / po4a changes when renaming a HAL component

Am 03.04.25 um 01:10 schrieb andy pugh: On Sat, 22 Mar 2025 at 19:11, Hans Unzner wrote: This means that some component names should change (for example LUT5 - LUT6) What is the "right" way to handle the changes in the docs and translation infrastructure? Not much to pay atten

Re: [Emc-developers] Translation / Docs / po4a changes when renaming a HAL component

Am 22.03.25 um 09:47 schrieb andy pugh: I am working on expanding the use of 64-bit ints in HAL. This means that some component names should change (for example LUT5 - LUT6) What is the "right" way to handle the changes in the docs and translation infrastructure? Not much to pay attention at

Re: [Emc-developers] Branch 2.9 problem

Sometimes, especially when switching between different branches, "make clean" is not sufficient. "git clean -dxf " cleans it like a fresh clone and is sometimes the better approach. Hans Am 08.12.24 um 11:00 schrieb Nicklas SB Karlsson: Have also had similar problems. Maybe I used make clean

Re: [Emc-developers] Bad charset in gmoccapy po files

Hi, thanks for reporting - fixed now. Am 20.11.24 um 11:32 schrieb Bertho Stultiens: Hi, There are three po files with bad charset definition: - src/po/gmoccapy/gmoccapy.pot - src/po/gmoccapy/ar.po - src/po/gmoccapy/ka.po The Content-Type line specifies charset=CHARSET, which is, well, wrong

Re: [Emc-developers] Bug#1080668: Missing Build-Depends on python3-setuptools

You could try install the dependencies following the instructions from the section "Building LinuxCNC". I did that and built LinuxCNC on Ubuntu 24 and it was straight forward without problems. I only had to install two additional runtime-packages. Am 12.10.24 um 11:16 schrieb theman whosoldthew

Re: [Emc-developers] Tests failing in Sid.

Am 01.09.24 um 19:26 schrieb andy pugh: Does anyone have any ideas about the cause of this? The other distros all seem to be building cleanly in CI. example: https://github.com/LinuxCNC/linuxcnc/actions/runs/10655514653/job/29533123088#step:8:9622 It is this one: https://github.com/LinuxC

Re: [Emc-developers] Broken Buildbot2

Am 22.07.24 um 22:20 schrieb Sebastian Kuzminsky: A recent commit in 2.9 triggered a bug in po4a and repeatedly crashed the buildbot. You can trigger the problem using this process: 1. Start a debian:buster container 2. Check out commit fadb1c28 (current head of 2.9) 3. Install build depende

Re: [Emc-developers] Bug#1079419: linuxcnc-uspace: please migrate from deprecated gtksourceview3 to gtksourceview4 (or 5)

A PR is now open: https://github.com/LinuxCNC/linuxcnc/pull/3083 Am 23.08.24 um 10:14 schrieb Simon McVittie: Package: linuxcnc-uspace Version: 2.9.3-1 Tags: trixie sid upstream Control: block 996689 by -1 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gtksourceview3 was

Re: [Emc-developers] "toggle" component docs.

Yes probably some problems with the encoding of the www macro of groff with output type HTML. But maybe this gets resolved automatically when Petter continues on that one: https://github.com/LinuxCNC/linuxcnc/pull/1376 Am 03.07.24 um 15:03 schrieb andy pugh: Not 100% successful. https://lin

Re: [Emc-developers] Possible 2.9.3 Update

Am 15.03.24 um 21:58 schrieb andy pugh: I have been asked if we can release an update to 2.9. Does anyone have anything nearly-ready that they would like to see in 2.9 before the cutoff? Only a little thing I'd like to finish: #2837 and #2911 Currently I am thinking in terms of next weeken

Re: [Emc-developers] Merge 2.9 to master

Am 31.12.23 um 13:29 schrieb andy pugh: On Sun, 31 Dec 2023 at 12:14, Hans Unzner wrote: You mean via Github by the author of the PR? Not sure if that will work. Better that the person who merges it keep track of it. That assumes that the person who accepts the merge understands the code

Re: [Emc-developers] Merge 2.9 to master

Am 31.12.23 um 13:01 schrieb andy pugh: On Sun, 31 Dec 2023 at 11:50, Hans Unzner wrote: Is it the job of the person who accepts the PR to merge it upstream? Or a secondary task for the Pull Requestor? I think it would be the best if the person who accepts the PR or the persons who makes

Re: [Emc-developers] Merge 2.9 to master

Am 31.12.23 um 12:21 schrieb andy pugh: On Sun, 31 Dec 2023 at 10:58, Hans Unzner wrote: It's been a while since 2.9 was merged to master (almost 3 months). I suppose that's one of the drawbacks of working through pull-requests. Is it the job of the person who accepts the PR t

[Emc-developers] Merge 2.9 to master

It's been a while since 2.9 was merged to master (almost 3 months). Like expected some merge conflicts popped up. So I would please some of the more experienced users to do that merge. Thanks! ___ Emc-developers mailing list Emc-developers@lists.source

Re: [Emc-developers] Linuxcnc 2.10pre with glade

time will.be the right one ;) Thanks a lot Cordialement, Moustapha Elhima *ELMO - machines outils *+33 6 09 99 21 97 Penser à préserver l'environnement avant d'imprimer ce message. Merci Message d'origine ---- De : Hans Unzner Date : 30/12/2023 16:57 (GMT+01:00) À :

Re: [Emc-developers] Linuxcnc 2.10pre with glade

I'm afraid but I think you have to do your modifications once more for LinuxCNC 2.9/2.10. There have been so many changes during the upgrade from Python2 to Python3 and Gtk2 to Gtk3, which make it almost impossible to merge from 2.8, especially the glade file. Also a huge number of deprecated w

Re: [Emc-developers] .po and .pot files in git

Am 17.12.23 um 23:29 schrieb andy pugh: On Sun, 17 Dec 2023 at 21:40, Hans Unzner wrote: If you think the files are generated correctly, you should commit them. They probably are, but how would I tell? Take some random samples maybe? Or you can open a pull request for this

Re: [Emc-developers] .po and .pot files in git

Am 17.12.23 um 22:37 schrieb Hans Unzner: Am 17.12.23 um 11:17 schrieb andy pugh: When I do test builds on my local machine I seem to create new .po and ,pot files. These show up as uncommitted changes in Git, and prevent rebasing etc. What is the right thing to do with these? It seems

Re: [Emc-developers] .po and .pot files in git

Am 17.12.23 um 11:17 schrieb andy pugh: When I do test builds on my local machine I seem to create new .po and ,pot files. These show up as uncommitted changes in Git, and prevent rebasing etc. What is the right thing to do with these? It seems that the target 'pofiles' have been invoked, e

Re: [Emc-developers] 2.9.2

Am 10.12.23 um 01:18 schrieb andy pugh: There are a number of important bug fixes waiting for release (including that I broke run-from-line in Axis. Oops). I plan to make a 2.9.2 release in the next few days. This is largely predicated on me figuring out how to fix the Bullseye builds, which

Re: [Emc-developers] Bug#1056990: src:linuxcnc: fails to migrate to testing for too long: unresolved RC issue

Am 28.11.23 um 16:52 schrieb andy pugh: On Tue, 28 Nov 2023 at 15:45, Steffen Möller wrote: We will not be part of the next Debian release if we do not fix (or otherwise close) the bugs reported against our package. It looks like a simple fix, possibly, as it is just the man3 pages: https

Re: [Emc-developers] Fwd: Upcoming stable (12.2) and oldstable (11.8) point releases

Yes we should use the opportunity and build a debian package from the current 2.9 branch. Am Freitag, 1. September 2023 schrieb andy pugh : > Is this an opportunity to get some bugfixes into the version that we > are distributing? It is fairly broken. > > -- Forwarded message - > F

Re: [Emc-developers] Sorry, I broke the builds.

I think you have to add that file to the po4a config file. Am Montag, 17. Juli 2023 schrieb andy pugh : > It looks like there is more to adding a new manpage than I thought. > > The docs built cleanly on my own system, so I thought I had fixed the problem. > > But: https://github.com/LinuxCNC/linu

Re: [Emc-developers] Merge Conflicts

Am 19.06.23 um 05:01 schrieb Phill Carter via Emc-developers: Could someone with a bit more knowledge of the documents than me please fix the merge conflicts from 2.9 to master. I have broken enough things recently. Cheers, Phill Done ___ Emc-

Re: [Emc-developers] Bookworm

Am 07.06.23 um 17:26 schrieb Sebastian Kuzminsky: On 6/7/23 06:48, andy pugh wrote: Is it a problem that we haven't actually released 2.9 and that it is due to be in Bookworm, which is due to be released very soon indeed? IMO it would have been better if we released 2.9.0 and got it into Bo

Re: [Emc-developers] Bookworm

Yeah we really should build actual deb packages from the current 2.9 branch and upload them to debian. Even though not all "2.9 must fix" issues are resolved, the current 2.9 is much better than that what is currently in debian. Much better in this case means that the majority of sample configs res

Re: [Emc-developers] Pluto Docs

Am 31.05.23 um 19:40 schrieb andy pugh: On Wed, 31 May 2023 at 17:44, Hans Unzner wrote: What speaks against are-adding the removed man pages? There is a section in the "driver" docs for the device in general, it doesn't seem to make all that much sense to make users

Re: [Emc-developers] Pluto Docs

Am 31.05.23 um 12:42 schrieb andy pugh: A forum thread ( https://forum.linuxcnc.org/9-installing-linuxcnc/49171-pluto-board-under-linuxcnc-2-8-4#271854 ) has led me to notice that the pluto_p docs are incomplete: http://linuxcnc.org/docs/stable/html/drivers/pluto-p.html They refer to manpage

Re: [Emc-developers] linuxcnc-dev

Am 07.05.23 um 03:01 schrieb andy pugh: I just added a system to create modbus drivers for mesa cards to 2.9 As things stand it doesn't do anything for installed LinuxCNC except add docs. The next step is to add the various scripts and templates to the linuxcnc-dev package, but I am not enti

Re: [Emc-developers] 2.9 release discussion

Am 24.04.23 um 21:12 schrieb andy pugh: On Mon, 24 Apr 2023 at 13:24, Hans Unzner wrote: I didn't have a time slot for that on Sunday unfortunately, but did you guys have 2.9 release discussion? If so, what was the conclusion? We went through all the pull requests and 10% of the i

Re: [Emc-developers] 2.9 release discussion

Am 22.04.23 um 21:03 schrieb andy pugh: We are hoping to dedicate a couple of hours tomorrow to deciding how to release 2.9. The idea would be to discuss it here at Tormach with a link to Zoom for those who are not here. No time set yet, but I would imagine anyone who is in Madison is availab

Re: [Emc-developers] New Modbus driver framework for Mesa UARTS

Am 22.04.23 um 01:12 schrieb andy pugh: On Fri, 21 Apr 2023 at 13:56, Hans Unzner wrote: What exactly do you mean with "inited from the device" resp. how should that happen? If the flag is set, it would read the current state of the registers and set the HAL pin states accordi

Re: [Emc-developers] New Modbus driver framework for Mesa UARTS

Am 21.04.23 um 12:16 schrieb Andy Pugh: On 21 Apr 2023, at 07:02, Hans Unzner wrote: Because, e.g., setting a bit in a holding register you need to read that register, set that bit and write the value back. I am wondering about including a flag that indicates that the HAL pins should

Re: [Emc-developers] New Modbus driver framework for Mesa UARTS

, set that bit and write the value back. Maybe that could be also a general component for handling those masked bits? Then it could be also used for MB2HAL for vfds which don't have a dedicated driver. Am 20.04.23 um 22:55 schrieb andy pugh: On Thu, 20 Apr 2023 at 20:05, Hans Unzner

Re: [Emc-developers] New Modbus driver framework for Mesa UARTS

Hi Andy, this is really a great addition - I already often thought that a modbus driver for the mesa cards is somehow missing. Thanks for that! The docs are quite comprehensive, so no real need to add something. However, some annotations: - The created HAL pins are inputs for some modbus command

Re: [Emc-developers] How to install Linuxcnc Debian Bookworm (Debian 12)

Thanks for sharing that document! I wonder if we should add some parts of that to the LinuxCNC docs, especially "Installing a later kernel" and "Realtek network drivers". What do you think? Hans Am 17.04.23 um 22:46 schrieb Rod Webster: Hi guys, I thought I'd share my installation guide for

Re: [Emc-developers] Translation query on the forum

Am 17.04.23 um 10:05 schrieb andy pugh: https://forum.linuxcnc.org/nativecam/48821-translation#269180 Do we still have documents that instruct people to use poedit? Yes we have (in 4 files). Time to fix that. But the forum's topic is a different one, NativeCam is an external tool for LinuxC

Re: [Emc-developers] new at-pid's Q

Am 01.04.23 um 19:19 schrieb gene heskett: Greetings all; Has anyone written an mdi script to run this autocal pid thing described in the man page? For some reason I've only been able to make it exersize z but once, not very far, Those findings copied into the ini file result in Z huntin

Re: [Emc-developers] Documentation question

Am 10.04.23 um 02:16 schrieb andy pugh: On Sat, 8 Apr 2023 at 08:41, Hans Unzner wrote: You meant "docs/src/man/man3",right? Ok, I added that and it seemed to work, but then deleting the old files led to problems. There are 559 instances of the string "hm2_pktuart_read.3

Re: [Emc-developers] Documentation question

Am 08.04.23 um 01:36 schrieb Sebastian Kuzminsky: On 4/7/23 16:49, andy pugh wrote: I have made some changes to hm2_pktuart and I feel the urge to document them. Currently this feature is (barely) documented in groff/troff in the files: docs/man/man3/hm2_pktuart_read.3hm2 docs/man/man3/hm2

Re: [Emc-developers] Halcompile: .comp filename and module name match

When it's only a warning - can't you just ignore the warning if this comp is only used on your machine? Or do you want to add it to the linuxcnc repo? Am 07.04.23 um 15:09 schrieb andy pugh: I remember some time ago that there was a change made to warn that the filename of the component and th

Re: [Emc-developers] GitHub build fails since last week

Am 31.03.23 um 18:52 schrieb andy pugh: On Fri, 31 Mar 2023 at 17:27, Hans Unzner wrote: This already appeared in 2018, so not sure if this is related: https://www.forum.linuxcnc.org/10-advanced-configuration/34976-compile-problems The last post in that thread looks relevant. https

[Emc-developers] GitHub build fails since last week

Hi, I guess you guys have also noticed that all builds on Github are currently failing. Does anyone has an idea what caused this? Could it be possible that the runners on Github were updated somehow? I wonder if it has something to do with this: checking whether readline license is compatible

Re: [Emc-developers] failing sample configs in 2.9: remap, gmoccapy, qtvcp, and more!

Am 08.03.23 um 21:10 schrieb Sebastian Kuzminsky: On 3/8/23 12:21, Hans Unzner wrote: Am 04.01.23 um 17:19 schrieb Sebastian Kuzminsky: On 1/4/23 05:09, Hans Unzner wrote: However, I have some annotations: - You could mention that the tests need to be run as sudo (at least for it only

Re: [Emc-developers] failing sample configs in 2.9: remap, gmoccapy, qtvcp, and more!

Am 04.01.23 um 17:19 schrieb Sebastian Kuzminsky: On 1/4/23 05:09, Hans Unzner wrote: However, I have some annotations: - You could mention that the tests need to be run as sudo (at least for it only worked so) and need Python >= 3.8 Hmm, I run them as a regular user.  Maybe you j

Re: [Emc-developers] Ran into a intermittent problem with Jog stop.

Am 17.01.23 um 02:44 schrieb gene heskett: If using a wireless keyboard, check the batteries with a voltmeter. Long keydowns may cause a fadeout that does not register as a keyup event. So when it comes time to send the keyup, the batteries are too low. Any battery that's below 1.4 volts p

Re: [Emc-developers] Unable to start LinuxCNC: TypeError: 'NoneType' object is not callable

This sounds like the problem reported here: https://github.com/LinuxCNC/linuxcnc/issues/1599#issuecomment-1364752832 Am 14.01.23 um 07:57 schrieb Alec Ari via Emc-developers: Will give it a shot soon! Thanks! On Friday, January 13, 2023 at 08:40:41 AM UTC, Sebastian Kuzminsky wrote: Does

Re: [Emc-developers] failing sample configs in 2.9: remap, gmoccapy, qtvcp, and more!

Am 04.01.23 um 17:19 schrieb Sebastian Kuzminsky: On 1/4/23 05:09, Hans Unzner wrote: However, I have some annotations: - You could mention that the tests need to be run as sudo (at least for it only worked so) and need Python >= 3.8 Hmm, I run them as a regular user.  Maybe you j

Re: [Emc-developers] failing sample configs in 2.9: remap, gmoccapy, qtvcp, and more!

.vehiclemods.net.au On Wed, 4 Jan 2023 at 22:09, Hans Unzner wrote: Really great, thank you! However, I have some annotations: - You could mention that the tests need to be run as sudo (at least for it only worked so) and need Python >= 3.8 - The stderr file only shows something like &

Re: [Emc-developers] failing sample configs in 2.9: remap, gmoccapy, qtvcp, and more!

Really great, thank you! However, I have some annotations: - You could mention that the tests need to be run as sudo (at least for it only worked so) and need Python >= 3.8 - The stderr file only shows something like "+ su --pty -c 'linuxcnc /usr/share/doc/linuxcnc/examples/sample-configs/sim/g

Re: [Emc-developers] January 2023 Online Meeting

For me Wednesdays doesn't work at all, but It would be ok for me if someone would record it for me. Hans Am 03.01.23 um 17:07 schrieb m...@mattshaver.com: The last online meeting was Monday, November 28, 2022 at 2:00pm Eastern standard Time for about 2 hours. The folks that attended, includin

Re: [Emc-developers] Eye candy is important - Titan got a new German friend - want that reaction for a LinuxCNC controller

Am 04.12.22 um 20:25 schrieb andy pugh: On Sun, 4 Dec 2022 at 11:45, Rod Webster wrote: In recent days, Linuxcnc does not seem to like the Wayland based graphical ... Do not add a root password so the default user can use sudo. ... You might like to disable autologon and the screensaver.

Re: [Emc-developers] Eye candy is important - Titan got a new German friend - want that reaction for a LinuxCNC controller

quot;...) The last two points would fall away when Bookworm is official released. But until then... On Sun, 4 Dec 2022 at 21:08, Hans Unzner wrote: Am 30.11.22 um 19:58 schrieb Rod Webster: I would hazard a guess you could download the debian ISO, install it and linuxcnc-uspace in the same t

Re: [Emc-developers] Eye candy is important - Titan got a new German friend - want that reaction for a LinuxCNC controller

Am 30.11.22 um 19:58 schrieb Rod Webster: It lowers the bar for everyone. Installing a real time kernel and all the dependencies might keep some people from just trying it. And it allows running it as a live system without even needing to install something. @hans, have you ever tried installi

Re: [Emc-developers] pncconf discrepancy between 2.8 and 2.9

Am 30.11.22 um 11:24 schrieb andy pugh: pins.c, hostmot2.h, hostmot2.c, release_notes.txt, hostmot2.9, hm2_eth.9 changelog and VERSION should all be resolved by --ours. For release_notes.txt please accept both changes but in reverse order, so that it look like this -

Re: [Emc-developers] Eye candy is important - Titan got a new German friend - want that reaction for a LinuxCNC controller

Am Di., 29. Nov. 2022 um 23:15 Uhr schrieb andy pugh : > On Tue, 29 Nov 2022 at 20:59, Rod Webster wrote: > > Why would we bother hosting our own ISO on slow servers and put our limited > > resources into building and maintaining said ISO's when the new paradigm > is > > already with us right now

Re: [Emc-developers] Merge Strategy

Am 28.11.22 um 02:44 schrieb Sebastian Kuzminsky: I still think merging upwards is the best way to do this. The main advantage is that git keeps track of what commits need to be propagated to the newer branch, so we'll never leave behind any bugfix commits in older stable branches.  This avo

Re: [Emc-developers] Merge Strategy

I agree that we should stick to "merge up" until we reach an agreement to change this. Hans Am 23.11.22 um 22:42 schrieb Chris Morley: Ya it's always been hard to consistently get answers in our project. It just seems the nature of our group. Thanks for continuing to try. Currently strategy i

Re: [Emc-developers] time delay hal component for lube pump

Good idea to make the lubrication based on the travelled distance. Here you find a solution in Python you could adapt. It saves the accumulated distance in a file and shows some statistics: https://forum.linuxcnc.org/gmoccapy/40709-gmocappy-clock?start=50#203809 Am Do., 24. Nov. 2022 um 10:19 Uhr

Re: [Emc-developers] 2.9-pre1

Both strategies have their pros and cons I think. Without merge up: con: You have to create multiple pull requests to fix one issue --> more work for both developer and reviewer and a bigger mess of PR's pro: No merge conflicts resp. the developer can solve those himself With merge up: pro: On

Re: [Emc-developers] 2.9-pre1

I would say the "degree of making sense" depends on how much the branches are diverged. Currently I think it makes much sense, because 2.9 and master are (almost) identical and the bug fixes for 2.9 are 100% applicable for master. Am Mi., 9. Nov. 2022 um 02:49 Uhr schrieb Chris Morley < chrisinnan

Re: [Emc-developers] 2.9-pre1

Am 08.11.22 um 11:06 schrieb andy pugh: Yesterday I created a new 2.9 branch to stabilise 2.9 for release. The content for 2.9 is not yet finalised (I would quite like to see the Colorlight and Remora drivers in there) but the plan is to work on fixing known bugs and build problems. The main

Re: [Emc-developers] Next LinuxCNC online meeting

I have to re-schedule the meeting to November 7th, 19:00 (20:00 Central Europe time). https://meet.jit.si/LinuxCNC-meeting-november-2022 See you! Hans Am 30.10.22 um 16:35 schrieb Hans Unzner: It figured out that November 6th fits best. So lets do it then at 19:00 UTC (19:00 London time

Re: [Emc-developers] Next LinuxCNC online meeting

Am 30.10.22 um 16:09 schrieb andy pugh: On Sun, 23 Oct 2022 at 19:21, Hans Unzner wrote: Hi! The last online meeting was in august, so time for a follow-up. Some of the dates in the survey have already passed. What was the decision on the date? I waited for some more people to

[Emc-developers] Next LinuxCNC online meeting

Hi! The last online meeting was in august, so time for a follow-up. In short we would like to speak about: * The upcoming 2.0 release * Transfer of features from MachineKit * Documentation: Style guide, po4a migration status, migration to Asciidoctor * Collaboration with industry on tool

Re: [Emc-developers] Time to split 2.9 and master?

Am 01.10.22 um 18:01 schrieb andy pugh: On Sat, 1 Oct 2022 at 16:29, Hans Unzner wrote: Unfortunately this would not work because: - From the pin name you can't draw a conclusion on the function. For example "mb2hal.00.01" could be fnct_06_write_sin

Re: [Emc-developers] Time to split 2.9 and master?

Am 25.09.22 um 19:59 schrieb andy pugh: On Sun, 25 Sept 2022 at 10:57, Hans Unzner wrote: On principle a good idea but I think it's misleading if the INI version number is increased when only something inside a component has changed. Maybe, but it actually serves no other purpose (an

Re: [Emc-developers] Auto-start gscreen on pi4

Am 26.09.22 um 15:41 schrieb Thaddeus Waldner: Hi, Does someone have a quick tutorial on how to auto-start Linuxcnc on a Raspberry Pi 4? I have a script that starts it when I manually run the script, but it fails when called from a systemd service. Thanks, Thaddeus Waldner You can try to

Re: [Emc-developers] [Emc-commit] [LinuxCNC/linuxcnc] 754933: first step to asciidoctor migration:

conf files. So the custom syntax highlighting for the code blocks is not working. And asciidoctor has to be installed on the CI as well. Am Mo., 26. Sept. 2022 um 16:00 Uhr schrieb Jérémie Tarot < silopo...@gmail.com>: > Le sam. 24 sept. 2022 à 15:10, Hans Unzner via Emc

Re: [Emc-developers] Time to split 2.9 and master?

Am 25.09.22 um 19:59 schrieb andy pugh: On Sun, 25 Sept 2022 at 10:57, Hans Unzner wrote: On principle a good idea but I think it's misleading if the INI version number is increased when only something inside a component has changed. Maybe, but it actually serves no other purpose (an

Re: [Emc-developers] Time to split 2.9 and master?

Am 24.09.22 um 16:31 schrieb andy pugh: On Fri, 23 Sept 2022 at 08:46, Hans Unzner wrote: But I have another question: Some time ago I extended MB2HAL and also changed some of the existing pin names to match the structure. So one have to change some pin names when switching to 2.9. I

Re: [Emc-developers] Merging 2.8 into Master

Am 24.09.22 um 16:22 schrieb andy pugh: On Fri, 23 Sept 2022 at 08:14, Hans Unzner wrote: If I do that and use "ours" on all conflicts, I get only three changed files. One only with whitespace changes. git merge -s ours 2.8 git push --dry-run git log -p da99e19495..f0ad48afa1 &

Re: [Emc-developers] Time to split 2.9 and master?

Am 20.09.22 um 22:59 schrieb andy pugh: Is it time to split 2.9 off as a stable-ish branch with a 2.9.0~pre0 tag? I agree. Still at least two things to fix related to Gmoccapy, but can be finished in a 2.9 branch as well. But I have another question: Some time ago I extended MB2HAL and

Re: [Emc-developers] Merging 2.8 into Master

Am 22.09.22 um 23:54 schrieb andy pugh: I just tried to (locally) merge 2.8 into Master. I decided to use the "ours" strategy so that nothing actually changed, all I wanted to do was mark them as merged, without changing anything, Looking at the dry-run patch, though, quite a lot seemed to ch

Re: [Emc-developers] Possible 2.8.4 release this weekend

Am 17.09.22 um 10:39 schrieb andy pugh: I think that the pieces are in place for a 2.8.4 release, mainly to add 7i96S support as one of the few cards currently available) Does anyone have any opinions on this matter? Yes I think so too. Go ahead 👍 And when you update the version number, plea

Re: [Emc-developers] [Hosted Weblate] New comment in LinuxCNC/LinuxCNC Documentation

Am 13.09.22 um 16:48 schrieb Steffen Möller via Emc-developers: # Comment added [ smoe](https://hosted.weblate.org/user/smoe/ "Steffen Möller"): [Hosted Weblate](https://hosted.weblate.org) / [LinuxCNC](https://hosted.weblate.org/projects/linuxcnc/) / [LinuxCNC Documentation](https://hosted.

Re: [Emc-developers] docs -> src: chaging ini to INI also in source tree

Am 08.09.22 um 00:13 schrieb andy pugh: On Wed, 7 Sept 2022 at 11:14, Steffen Moeller wrote: Now, it happened that the "linuxcnc -h" output is quoted in the documentation, and that had some "ini" that we could either leave as it is (and be inconsistent within the documentation but consisten

Re: [Emc-developers] next release discussion: Why not make the branch new

Am 23.08.22 um 15:44 schrieb Jérémie Tarot: hey @lcvette o/ Le mar. 23 août 2022 à 15:15, Small Shop Concepts a écrit : on Gitkraken for QtPyvcp we use the GLO Boards which is basically just an item check list with some good formatting, this way it is recorded what has to be fixed and strik

Re: [Emc-developers] next release discussion: Why not make the branch new

I think we all agree that setting a date for the next release is mandatory, but nobody of the candidates has the adequate time for that job. Maybe we could start by picking the issues/tasks we want to have have/do in/for 2.9. We talked about creating a GitHub project

Re: [Emc-developers] Next Linuxcnc Online meeting

I agree that the meeting was not really effective. In my opinion we have to think about the topics we want to discuss in advance and put them on the agenda. And also limit the time. The audio and video is often a problem at those meetings. Maybe we should spend some time to check that before we

Re: [Emc-developers] GTK

Am 09.08.22 um 15:24 schrieb andy pugh: On Tue, 9 Aug 2022 at 13:39, Hans Unzner wrote: Sorry, I don't really got it. What do you mean with 'passing-through a click on the + or - buttons.'? Do you want to react only to a click in text/value area but not to a click on the +

Re: [Emc-developers] GTK

Is this still relevant? Are you talking about the GtkSpinButton? And which signal are you currently using? Maybe you can use the signal 'value-changed'? If you click one of the +/- buttons it would change the value in most cases and would trigger that signal... Am 06.07.22 um 00:30 schrieb

Re: [Emc-developers] [Hosted Weblate] New comment in LinuxCNC/LinuxCNC Documentation

Maybe will restart the program at the following line. --> will continue executing the program at the following line. ? Am Do., 28. Juli 2022 um 11:55 Uhr schrieb Steffen Möller via Emc-developers : > > > # Comment added > > [ smoe](https://hosted.weblate.org/user/smoe/ "Steffen Möller"): [Hosted

Re: [Emc-developers] LinuxCNC documentation is now available on Weblate!

Am 14.06.22 um 23:43 schrieb Greg C: Does https://github.com/LinuxCNC/linuxcnc/pull/1764 fix this for you? Yes, it does. I took liberty to merge it. Thank you for noticing it was out there. -Greg Thanks for testing 😉 /Hans ___ Emc-developer

Re: [Emc-developers] LinuxCNC documentation is now available on Weblate!

Am 14.06.22 um 01:32 schrieb Greg C: Thanks Hans. Are you tracking that the "no-docs" switch is not currently working for building the debian packages? Steps: cd linuxcnc-dev/debian ./configure uspace no-docs cd .. dpkg-buildpackage -b -uc Error: dpkg-buildpackage: error: syntax error in de

Re: [Emc-developers] Fwd: [Hosted Weblate] Hosting request for LinuxCNC (Libre, trial)

Am 14.06.22 um 16:30 schrieb Jérémie Tarot: Le mar. 14 juin 2022 à 16:22, andy pugh a écrit : On Tue, 14 Jun 2022 at 15:03, Jérémie Tarot wrote: * In the README, add the status badge at the top with others and the widget combo under the two translation related paragraphs If you mean th

Re: [Emc-developers] Interfacing to Magnescale scales

Am 14.06.22 um 10:53 schrieb andy pugh: On Tue, 14 Jun 2022 at 09:36, Hans Unzner wrote: If you have direct access to the resolver it would be worth a thought to use a "resolver to digital converter", e.g. something like this: https://www.analog.com/en/parametricsearch/10890#/ Th

Re: [Emc-developers] LinuxCNC documentation is now available on Weblate!

, Jun 11, 2022 at 4:41 PM Hans Unzner wrote: Am 04.06.22 um 12:41 schrieb Greg C: Additionally, I would like to suggest that whether or not the translated documents are built or not should be controlled by a switch/option when you set the option to build for HTML, PDF, or BOTH. Ther

Re: [Emc-developers] Interfacing to Magnescale scales

Am 14.06.22 um 10:13 schrieb andy pugh: On Tue, 14 Jun 2022 at 07:24, Sebastian Kuzminsky wrote: Does anyone know how to interface these position sensors to LinuxCNC? Another option might be to ignore the scales and access the resolvers by connecting to the currently unused resolver outpu

Re: [Emc-developers] LinuxCNC documentation is now available on Weblate!

Am 04.06.22 um 12:41 schrieb Greg C: Additionally, I would like to suggest that whether or not the translated documents are built or not should be controlled by a switch/option when you set the option to build for HTML, PDF, or BOTH. There may be no need for most developers to build the trans

Re: [Emc-developers] buildbot? no updates in about a week now.

Am Do., 9. Juni 2022 um 11:25 Uhr schrieb Sebastian Kuzminsky < s...@highlab.com>: > On 6/9/22 10:42, andy pugh wrote: > > .deb builds are currently failing: > > > > > http://buildbot.linuxcnc.org/buildbot/builders/4041.deb-buster-rtpreempt-amd64/builds/1818 > > debs are failing because the wonder

[Emc-developers] LinuxCNC documentation is now available on Weblate!

Am Samstag, 4. Juni 2022 schrieb Greg C : > Additionally, I would like to suggest that whether or not the translated > documents are built or not should be controlled by a switch/option when you > set the option to build for HTML, PDF, or BOTH. There may be no need for > most developers to build t

[Emc-developers] LinuxCNC documentation is now available on Weblate!

Dear all, the documentation build system of LinuxCNC is now enhanced to support GNU gettext, which in turn is supported by online translation communities. It now uses the po4a system to generate POT and PO files from the English documentation. LinuxCNC is already present in Weblate for the tr

Re: [Emc-developers] OPINION: Setting Cannon's default G64 to something safer

Am Mittwoch, 1. Juni 2022 schrieb Chris Morley : > Forum discussion here: > https://forum.linuxcnc.org/20-g-code/46023-simple-rectangle-has-a-radius-on-all-edges-strange?start=0 > > Gist: > Often users are surprised by linuxcnc's corner rounding with the default setting of G64. > I suggested we set

Re: [Emc-developers] Fwd: [Emc-commit] [LinuxCNC/linuxcnc] 240dfc: docs: User M-Codes - fix typo

This will go into master on the next merge from 2.8 to master I think. Am Do., 5. Mai 2022 um 12:27 Uhr schrieb Jérémie Tarot : > @andy Do you want me to prepare this for master for after translation sync > merge ? > > -- Forwarded message - > De : andypugh via Emc-commit > Date:

Re: [Emc-developers] Fix for Groff subsection in HTML

Am Mittwoch, 4. Mai 2022 schrieb Jérémie Tarot : > Isn't an adoc file a better man page? 😉 You compare apples with bananas ;-) Do you mean man pages vs. HTML/PDF-docs or Groff vs. AsciiDoc? ___ Emc-developers mailing list Emc-developers@lists.sourceforg

Re: [Emc-developers] Fix for Groff subsection in HTML

Am 04.05.22 um 22:25 schrieb Jérémie Tarot: Le mer. 4 mai 2022 à 21:58, Hans Unzner a écrit : Am 04.05.22 um 20:53 schrieb andy pugh: On Wed, 4 May 2022 at 19:26, Hans Unzner wrote: My plan is to generate the HTML man pages directly from the adoc man pages, when we made the switchover

Re: [Emc-developers] Fix for Groff subsection in HTML

Am 04.05.22 um 22:04 schrieb andy pugh: On Wed, 4 May 2022 at 20:58, Hans Unzner wrote: Sure, but *backward-compatibility*. If we replace all Groff formatting in the .comp files by AsciiDoc, we should adapt halcomp that it understands both Actually, that's probably the easy way.

  1   2   >