Menu
▾
▴
emc-developers — Developer specific. For issues of interest to users see emc-users list (below)
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(29) |
Dec
(16) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(2) |
Feb
(6) |
Mar
(2) |
Apr
|
May
(3) |
Jun
(1) |
Jul
(32) |
Aug
(15) |
Sep
(5) |
Oct
(5) |
Nov
|
Dec
(1) |
| 2002 |
Jan
(12) |
Feb
|
Mar
(6) |
Apr
(1) |
May
(5) |
Jun
(1) |
Jul
(3) |
Aug
(3) |
Sep
(4) |
Oct
(2) |
Nov
(19) |
Dec
(14) |
| 2003 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(56) |
Jun
(41) |
Jul
(324) |
Aug
(46) |
Sep
(123) |
Oct
(62) |
Nov
(53) |
Dec
(102) |
| 2004 |
Jan
(84) |
Feb
(67) |
Mar
(8) |
Apr
(68) |
May
(52) |
Jun
(119) |
Jul
(19) |
Aug
(43) |
Sep
(51) |
Oct
(189) |
Nov
(74) |
Dec
(67) |
| 2005 |
Jan
(43) |
Feb
(43) |
Mar
(139) |
Apr
(20) |
May
(56) |
Jun
(160) |
Jul
(94) |
Aug
(91) |
Sep
(53) |
Oct
(79) |
Nov
(198) |
Dec
(106) |
| 2006 |
Jan
(103) |
Feb
(116) |
Mar
(135) |
Apr
(97) |
May
(72) |
Jun
(49) |
Jul
(51) |
Aug
(45) |
Sep
(67) |
Oct
(91) |
Nov
(51) |
Dec
(81) |
| 2007 |
Jan
(100) |
Feb
(57) |
Mar
(72) |
Apr
(81) |
May
(49) |
Jun
(13) |
Jul
(5) |
Aug
(32) |
Sep
(37) |
Oct
(42) |
Nov
(84) |
Dec
(41) |
| 2008 |
Jan
(32) |
Feb
(45) |
Mar
(68) |
Apr
(91) |
May
(38) |
Jun
(50) |
Jul
(83) |
Aug
(52) |
Sep
(108) |
Oct
(84) |
Nov
(125) |
Dec
(99) |
| 2009 |
Jan
(166) |
Feb
(188) |
Mar
(129) |
Apr
(88) |
May
(88) |
Jun
(117) |
Jul
(112) |
Aug
(82) |
Sep
(32) |
Oct
(79) |
Nov
(68) |
Dec
(71) |
| 2010 |
Jan
(49) |
Feb
(65) |
Mar
(113) |
Apr
(63) |
May
(71) |
Jun
(107) |
Jul
(59) |
Aug
(113) |
Sep
(103) |
Oct
(86) |
Nov
(132) |
Dec
(144) |
| 2011 |
Jan
(124) |
Feb
(67) |
Mar
(114) |
Apr
(134) |
May
(81) |
Jun
(120) |
Jul
(137) |
Aug
(83) |
Sep
(143) |
Oct
(165) |
Nov
(288) |
Dec
(137) |
| 2012 |
Jan
(337) |
Feb
(135) |
Mar
(159) |
Apr
(278) |
May
(358) |
Jun
(110) |
Jul
(77) |
Aug
(522) |
Sep
(301) |
Oct
(312) |
Nov
(319) |
Dec
(344) |
| 2013 |
Jan
(216) |
Feb
(318) |
Mar
(196) |
Apr
(61) |
May
(369) |
Jun
(387) |
Jul
(338) |
Aug
(308) |
Sep
(247) |
Oct
(168) |
Nov
(335) |
Dec
(347) |
| 2014 |
Jan
(322) |
Feb
(157) |
Mar
(414) |
Apr
(244) |
May
(152) |
Jun
(189) |
Jul
(152) |
Aug
(138) |
Sep
(108) |
Oct
(113) |
Nov
(65) |
Dec
(60) |
| 2015 |
Jan
(97) |
Feb
(65) |
Mar
(109) |
Apr
(132) |
May
(153) |
Jun
(103) |
Jul
(117) |
Aug
(186) |
Sep
(113) |
Oct
(143) |
Nov
(115) |
Dec
(221) |
| 2016 |
Jan
(157) |
Feb
(113) |
Mar
(145) |
Apr
(10) |
May
(95) |
Jun
(93) |
Jul
(159) |
Aug
(53) |
Sep
(94) |
Oct
(213) |
Nov
(88) |
Dec
(112) |
| 2017 |
Jan
(124) |
Feb
(59) |
Mar
(82) |
Apr
(101) |
May
(27) |
Jun
(78) |
Jul
(144) |
Aug
(52) |
Sep
(48) |
Oct
(35) |
Nov
(63) |
Dec
(43) |
| 2018 |
Jan
(38) |
Feb
(26) |
Mar
(63) |
Apr
(21) |
May
(75) |
Jun
(70) |
Jul
(72) |
Aug
(41) |
Sep
(84) |
Oct
(102) |
Nov
(28) |
Dec
(60) |
| 2019 |
Jan
(13) |
Feb
(92) |
Mar
(141) |
Apr
(25) |
May
(138) |
Jun
(95) |
Jul
(121) |
Aug
(75) |
Sep
(32) |
Oct
(43) |
Nov
(122) |
Dec
(64) |
| 2020 |
Jan
(54) |
Feb
(84) |
Mar
(239) |
Apr
(492) |
May
(182) |
Jun
(139) |
Jul
(126) |
Aug
(165) |
Sep
(162) |
Oct
(74) |
Nov
(108) |
Dec
(12) |
| 2021 |
Jan
(59) |
Feb
(61) |
Mar
(22) |
Apr
(129) |
May
(97) |
Jun
(108) |
Jul
(96) |
Aug
(59) |
Sep
(36) |
Oct
(105) |
Nov
(46) |
Dec
(17) |
| 2022 |
Jan
(67) |
Feb
(111) |
Mar
(104) |
Apr
(168) |
May
(58) |
Jun
(172) |
Jul
(118) |
Aug
(114) |
Sep
(177) |
Oct
(66) |
Nov
(208) |
Dec
(196) |
| 2023 |
Jan
(99) |
Feb
(47) |
Mar
(53) |
Apr
(93) |
May
(70) |
Jun
(33) |
Jul
(45) |
Aug
(54) |
Sep
(89) |
Oct
(127) |
Nov
(41) |
Dec
(102) |
| 2024 |
Jan
(38) |
Feb
(53) |
Mar
(78) |
Apr
(25) |
May
(26) |
Jun
(21) |
Jul
(56) |
Aug
(10) |
Sep
(65) |
Oct
(45) |
Nov
(38) |
Dec
(37) |
| 2025 |
Jan
(78) |
Feb
(17) |
Mar
(47) |
Apr
(45) |
May
(6) |
Jun
(33) |
Jul
(68) |
Aug
(49) |
Sep
(28) |
Oct
(69) |
Nov
(70) |
Dec
|
|
From: rodw <ro...@ve...> - 2025-11-25 01:33:24
|
>As far as i can see it isn't finding random typos in the code, it is >finding them in the changelog.gz files of the debian packages Yes but the changelog content is coming from other files containing the purported spelling error so the fix is to locate the files containing the suggested typo (and exclude binary files like SVG somehow) On 2025-11-25 11:29, rodw <ro...@ve...> wrote: > On further investigation, lintian is finding EMTpy in the .SVG file which is part of a very long encoded string. This is definitely not an error. > > > > On 2025-11-25 11:20, rodw <ro...@ve...> wrote: > > It is possible to locate the source of the error using grep but when the error is in a .svg file I'm not sure of a solution in that case. > > > > rod@penguin:~/linuxcnc-dev$ grep -r -i -l "consistancy" ./ > > ./share/qtvcp/screens/qtplasmac/versions.html > > rod@penguin:~/linuxcnc-dev$ grep -r -i -l "emtpy" ./ > > ./configs/sim/gmoccapy/lathe_configs/LatheMacro.svg > > > > Can the build script be modified so it does not fail on lintian warnings? > > > > > > Perhaps a script could process the lintian warnings and list the source files (and possibly replace the incorrect word. > > > > Rod > > > > On 2025-11-25 10:53, Stuart Stevenson <st...@gm...> wrote: > > > As long as the misspelling is consistent where ever it is used then no > > > error will be genderated. > > > > > > Addressee is the intended audience. > > > If you are not the addressee then my consent is not given for you to read > > > this email furthermore it is my wish you would close this without saving or > > > reading, and cease and desist from saving or opening my private > > > correspondence. > > > Thank you for honoring my wish. > > > > > > > > > > > > On Mon, Nov 24, 2025 at 4:30 PM andy pugh <bod...@gm...> wrote: > > > > > > > On Mon, 24 Nov 2025 at 10:33, andy pugh <bod...@gm...> wrote: > > > > > > > > > > Buildbot builds are currently failing Lintian on typos in the changelog. > > > > > http://buildbot2.highlab.com/buildbot/#/builders/2/builds/2394 > > > > > > > > Well, I am baffled now, as the spelling errors are the same in all > > > > packages. But I can't find the typos mentioned anywhere in the > > > > codebase (not even after unzipping the changelog.gz files that are > > > > referenced) > > > > > > > > W: linuxcnc-uspace: spelling-error-in-changelog appearence appearance > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog conection connection > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog consistancy > > > > consistency [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog consistant consistent > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog controler controller > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog depricated deprecated > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog disapearing > > > > disappearing [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog doesnt doesn't > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog dont don't > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog embeded embedded > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog emtpy empty > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog erronous erroneous > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog exapmles examples > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog exeption exception > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog extention extension > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog fuction function > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog funciton function > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog interal internal > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog interpeter interpreter > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog keybord keyboard > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog lintain lintian > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog mantained maintained > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog mispelled misspelled > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog paramater parameter > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog paremeters parameters > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog pin pin (duplicate > > > > word) pin [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog supress suppress > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog surpress suppress > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog tempararily > > > > temporarily [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog temparary temporary > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog travese traverse > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > W: linuxcnc-uspace: spelling-error-in-changelog unsued unused > > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > > > > > > > > > -- > > > > atp > > > > "A motorcycle is a bicycle with a pandemonium attachment and is > > > > designed for the especial use of mechanical geniuses, daredevils and > > > > lunatics." > > > > — George Fitch, Atlanta Constitution Newspaper, 1912 > > > > > > > > > > > > _______________________________________________ > > > > Emc-developers mailing list > > > > Emc...@li... > > > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > > > > > > > > > _______________________________________________ > > > Emc-developers mailing list > > > Emc...@li... > > > https://lists.sourceforge.net/lists/listinfo/emc-developers |
|
From: rodw <ro...@ve...> - 2025-11-25 01:29:20
|
On further investigation, lintian is finding EMTpy in the .SVG file which is part of a very long encoded string. This is definitely not an error. On 2025-11-25 11:20, rodw <ro...@ve...> wrote: > It is possible to locate the source of the error using grep but when the error is in a .svg file I'm not sure of a solution in that case. > > rod@penguin:~/linuxcnc-dev$ grep -r -i -l "consistancy" ./ > ./share/qtvcp/screens/qtplasmac/versions.html > rod@penguin:~/linuxcnc-dev$ grep -r -i -l "emtpy" ./ > ./configs/sim/gmoccapy/lathe_configs/LatheMacro.svg > > Can the build script be modified so it does not fail on lintian warnings? > > > Perhaps a script could process the lintian warnings and list the source files (and possibly replace the incorrect word. > > Rod > > On 2025-11-25 10:53, Stuart Stevenson <st...@gm...> wrote: > > As long as the misspelling is consistent where ever it is used then no > > error will be genderated. > > > > Addressee is the intended audience. > > If you are not the addressee then my consent is not given for you to read > > this email furthermore it is my wish you would close this without saving or > > reading, and cease and desist from saving or opening my private > > correspondence. > > Thank you for honoring my wish. > > > > > > > > On Mon, Nov 24, 2025 at 4:30 PM andy pugh <bod...@gm...> wrote: > > > > > On Mon, 24 Nov 2025 at 10:33, andy pugh <bod...@gm...> wrote: > > > > > > > > Buildbot builds are currently failing Lintian on typos in the changelog. > > > > http://buildbot2.highlab.com/buildbot/#/builders/2/builds/2394 > > > > > > Well, I am baffled now, as the spelling errors are the same in all > > > packages. But I can't find the typos mentioned anywhere in the > > > codebase (not even after unzipping the changelog.gz files that are > > > referenced) > > > > > > W: linuxcnc-uspace: spelling-error-in-changelog appearence appearance > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog conection connection > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog consistancy > > > consistency [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog consistant consistent > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog controler controller > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog depricated deprecated > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog disapearing > > > disappearing [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog doesnt doesn't > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog dont don't > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog embeded embedded > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog emtpy empty > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog erronous erroneous > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog exapmles examples > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog exeption exception > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog extention extension > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog fuction function > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog funciton function > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog interal internal > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog interpeter interpreter > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog keybord keyboard > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog lintain lintian > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog mantained maintained > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog mispelled misspelled > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog paramater parameter > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog paremeters parameters > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog pin pin (duplicate > > > word) pin [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog supress suppress > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog surpress suppress > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog tempararily > > > temporarily [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog temparary temporary > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog travese traverse > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > W: linuxcnc-uspace: spelling-error-in-changelog unsued unused > > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > > > > > > -- > > > atp > > > "A motorcycle is a bicycle with a pandemonium attachment and is > > > designed for the especial use of mechanical geniuses, daredevils and > > > lunatics." > > > — George Fitch, Atlanta Constitution Newspaper, 1912 > > > > > > > > > _______________________________________________ > > > Emc-developers mailing list > > > Emc...@li... > > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > > > > > > _______________________________________________ > > Emc-developers mailing list > > Emc...@li... > > https://lists.sourceforge.net/lists/listinfo/emc-developers |
|
From: andy p. <bod...@gm...> - 2025-11-25 01:28:24
|
On Tue, 25 Nov 2025 at 01:23, rodw <ro...@ve...> wrote: > > It is possible to locate the source of the error using grep but when the error is in a .svg file I'm not sure of a solution in that case. The error is "spelling-error-in-changelog" and it gives the path (in the debian folder) to the file where the problem is: [usr/share/doc/linuxcnc-uspace/changelog.gz] As far as i can see it isn't finding random typos in the code, it is finding them in the changelog.gz files of the debian packages -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 |
|
From: rodw <ro...@ve...> - 2025-11-25 01:20:48
|
It is possible to locate the source of the error using grep but when the error is in a .svg file I'm not sure of a solution in that case. rod@penguin:~/linuxcnc-dev$ grep -r -i -l "consistancy" ./ ./share/qtvcp/screens/qtplasmac/versions.html rod@penguin:~/linuxcnc-dev$ grep -r -i -l "emtpy" ./ ./configs/sim/gmoccapy/lathe_configs/LatheMacro.svg Can the build script be modified so it does not fail on lintian warnings? Perhaps a script could process the lintian warnings and list the source files (and possibly replace the incorrect word. Rod On 2025-11-25 10:53, Stuart Stevenson <st...@gm...> wrote: > As long as the misspelling is consistent where ever it is used then no > error will be genderated. > > Addressee is the intended audience. > If you are not the addressee then my consent is not given for you to read > this email furthermore it is my wish you would close this without saving or > reading, and cease and desist from saving or opening my private > correspondence. > Thank you for honoring my wish. > > > > On Mon, Nov 24, 2025 at 4:30 PM andy pugh <bod...@gm...> wrote: > > > On Mon, 24 Nov 2025 at 10:33, andy pugh <bod...@gm...> wrote: > > > > > > Buildbot builds are currently failing Lintian on typos in the changelog. > > > http://buildbot2.highlab.com/buildbot/#/builders/2/builds/2394 > > > > Well, I am baffled now, as the spelling errors are the same in all > > packages. But I can't find the typos mentioned anywhere in the > > codebase (not even after unzipping the changelog.gz files that are > > referenced) > > > > W: linuxcnc-uspace: spelling-error-in-changelog appearence appearance > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog conection connection > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog consistancy > > consistency [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog consistant consistent > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog controler controller > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog depricated deprecated > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog disapearing > > disappearing [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog doesnt doesn't > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog dont don't > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog embeded embedded > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog emtpy empty > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog erronous erroneous > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog exapmles examples > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog exeption exception > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog extention extension > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog fuction function > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog funciton function > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog interal internal > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog interpeter interpreter > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog keybord keyboard > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog lintain lintian > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog mantained maintained > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog mispelled misspelled > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog paramater parameter > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog paremeters parameters > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog pin pin (duplicate > > word) pin [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog supress suppress > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog surpress suppress > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog tempararily > > temporarily [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog temparary temporary > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog travese traverse > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > W: linuxcnc-uspace: spelling-error-in-changelog unsued unused > > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > > > > -- > > atp > > "A motorcycle is a bicycle with a pandemonium attachment and is > > designed for the especial use of mechanical geniuses, daredevils and > > lunatics." > > — George Fitch, Atlanta Constitution Newspaper, 1912 > > > > > > _______________________________________________ > > Emc-developers mailing list > > Emc...@li... > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > > > _______________________________________________ > Emc-developers mailing list > Emc...@li... > https://lists.sourceforge.net/lists/listinfo/emc-developers |
|
From: Stuart S. <st...@gm...> - 2025-11-25 00:52:21
|
As long as the misspelling is consistent where ever it is used then no error will be genderated. Addressee is the intended audience. If you are not the addressee then my consent is not given for you to read this email furthermore it is my wish you would close this without saving or reading, and cease and desist from saving or opening my private correspondence. Thank you for honoring my wish. On Mon, Nov 24, 2025 at 4:30 PM andy pugh <bod...@gm...> wrote: > On Mon, 24 Nov 2025 at 10:33, andy pugh <bod...@gm...> wrote: > > > > Buildbot builds are currently failing Lintian on typos in the changelog. > > http://buildbot2.highlab.com/buildbot/#/builders/2/builds/2394 > > Well, I am baffled now, as the spelling errors are the same in all > packages. But I can't find the typos mentioned anywhere in the > codebase (not even after unzipping the changelog.gz files that are > referenced) > > W: linuxcnc-uspace: spelling-error-in-changelog appearence appearance > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog conection connection > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog consistancy > consistency [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog consistant consistent > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog controler controller > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog depricated deprecated > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog disapearing > disappearing [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog doesnt doesn't > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog dont don't > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog embeded embedded > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog emtpy empty > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog erronous erroneous > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog exapmles examples > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog exeption exception > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog extention extension > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog fuction function > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog funciton function > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog interal internal > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog interpeter interpreter > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog keybord keyboard > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog lintain lintian > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog mantained maintained > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog mispelled misspelled > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog paramater parameter > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog paremeters parameters > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog pin pin (duplicate > word) pin [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog supress suppress > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog surpress suppress > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog tempararily > temporarily [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog temparary temporary > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog travese traverse > [usr/share/doc/linuxcnc-uspace/changelog.gz] > W: linuxcnc-uspace: spelling-error-in-changelog unsued unused > [usr/share/doc/linuxcnc-uspace/changelog.gz] > > > -- > atp > "A motorcycle is a bicycle with a pandemonium attachment and is > designed for the especial use of mechanical geniuses, daredevils and > lunatics." > — George Fitch, Atlanta Constitution Newspaper, 1912 > > > _______________________________________________ > Emc-developers mailing list > Emc...@li... > https://lists.sourceforge.net/lists/listinfo/emc-developers > |
|
From: andy p. <bod...@gm...> - 2025-11-24 22:26:45
|
On Mon, 24 Nov 2025 at 10:33, andy pugh <bod...@gm...> wrote: > > Buildbot builds are currently failing Lintian on typos in the changelog. > http://buildbot2.highlab.com/buildbot/#/builders/2/builds/2394 Well, I am baffled now, as the spelling errors are the same in all packages. But I can't find the typos mentioned anywhere in the codebase (not even after unzipping the changelog.gz files that are referenced) W: linuxcnc-uspace: spelling-error-in-changelog appearence appearance [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog conection connection [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog consistancy consistency [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog consistant consistent [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog controler controller [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog depricated deprecated [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog disapearing disappearing [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog doesnt doesn't [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog dont don't [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog embeded embedded [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog emtpy empty [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog erronous erroneous [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog exapmles examples [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog exeption exception [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog extention extension [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog fuction function [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog funciton function [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog interal internal [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog interpeter interpreter [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog keybord keyboard [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog lintain lintian [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog mantained maintained [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog mispelled misspelled [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog paramater parameter [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog paremeters parameters [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog pin pin (duplicate word) pin [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog supress suppress [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog surpress suppress [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog tempararily temporarily [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog temparary temporary [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog travese traverse [usr/share/doc/linuxcnc-uspace/changelog.gz] W: linuxcnc-uspace: spelling-error-in-changelog unsued unused [usr/share/doc/linuxcnc-uspace/changelog.gz] -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 |
|
From: andy p. <bod...@gm...> - 2025-11-24 10:34:01
|
Buildbot builds are currently failing Lintian on typos in the changelog. http://buildbot2.highlab.com/buildbot/#/builders/2/builds/2394 The problem here is that the changelog was generated from commit messages, and has inherited errors from there. Should I correct the errors in the changelog? Or would it be better to add something to lintian-overrides? -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 |
|
From: andy p. <bod...@gm...> - 2025-11-23 19:51:16
|
http://www.linuxcnc.org/iso/linuxcnc_2.9.7-amd64.hybrid.iso It doesn't work on my (slightly dodgy) N100DC board (graphics glitches) It only seems to have the right splash-screen in BIOS mode. (not UEFI) -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 |
|
From: Steffen M. <ste...@gm...> - 2025-11-23 14:49:23
|
> Gesendet: Donnerstag, 13. November 2025 um 01:04 > Von: "Steffen Möller via Emc-developers" <emc...@li...> > An: rm...@un..., emc...@li... > CC: "Steffen Möller" <ste...@gm...> > Betreff: [Emc-developers] Another Video Meetup on Sunday the 23rd of November, 20:00 GMT+1 (CET) > > > Hello, > > we had a good experience last Sunday with this "Big Blue Button" instance > > https://greenlight.bbb.uni-rostock.de/b/ste-c4d-brs-3k6 > Access code: 869782 > Date: November 23rd, 2025 > https://www.timeanddate.com/time/zones/cet > 20:00 > > and agreed to reuse that room two weeks later again. For the agenda > it was suggested to jointly go through the issues. > > @Robert, yes, please be the moderator of this upcoming one. Technically, > this one has now worked without a glitch. Since also Open Source, it seems > unwise to go back to what we had before, but let us test how well this > now scales. > > Best, > Steffen > > > _______________________________________________ > Emc-developers mailing list > Emc...@li... > https://lists.sourceforge.net/lists/listinfo/emc-developers > |
|
From: gene h. <ghe...@sh...> - 2025-11-22 00:34:27
|
On 11/21/25 16:47, Hans Unzner wrote:
> With that CSS I get a white background with 20 pt font size (though it
> needs some fine tuning to not affect other applications hat much):
>
> notebook*,box*{
> background-color: white;
> font-size: 20;
> }
>
> Hans
>
> Am 21.11.25 um 19:18 schrieb gene heskett:
>>
>>
>> On 11/20/25 16:05, andy pugh wrote:
>>> On Thu, 20 Nov 2025 at 20:10, gene heskett <ghe...@sh...>
>>> wrote:
>>>
>>>> Is there a way to A; get rid of the very low contrast and
>>>> B: force the use of a larger font such that I can still
>>>> read it when it does not have "focus"?
>>> You could experiment with the high contrast styles in the desktop
>>> manager, though that doesn't seem to have much effect on halmeter.
>> I have added that dir and css file which didn't exist, getting
>> a fixed black background which helps a bit but the text size
>> of 20 doesn't make it bigger. I've not tried larger values. I will
>> when next at the machines own keyboard. Currently I am
>> attempting to reconfigure it back to 3 axis for doing some
>> simple EDM. I have the hardware to make the edm feed
>> automatic, winding my own transformer to measure the
>> sparking activity & making that an analogue voltage to
>> present to a 7i76D analogue input pin. If I am successful, you
>> will get schematics that could be used W-EDM machine.
>>>
That would be quite a bit better, but how did you get it?, and I note
the selection frame has focus, while the halmeter display is still the
low contrast no focus & greyed out state although the text is bigger.
I've now tried font-size: up to 40; with no effect.
>>
>> Cheers, Gene Heskett, CET.
>
>
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers
Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Don't poison our oceans, interdict drugs at the src.
|
|
From: gene h. <ghe...@sh...> - 2025-11-22 00:23:20
|
On 11/21/25 16:47, Hans Unzner wrote:
> With that CSS I get a white background with 20 pt font size (though it
> needs some fine tuning to not affect other applications hat much):
>
> notebook*,box*{
> background-color: white;
> font-size: 20;
> }
> this:
notebooK*,box* {
background-color: black;
font-size: 40;
}
gets me a black border, a bright white background inside that border and
greyed out text I cannot read unless it has focus, at the normal text
font size.
Several questions result, Hans:
1: Where can I find the Document describing how to use this css stuff?
2: And where can I find the file I need to set and make chattr +i,
everytime I use nano to remotely edit something like this, I loose the
keyboard repeat globally, a PITA that takes me half an hour to find and
fix with the bookworms hiding of everything important
3: Spectacle, the screen shot taker, doesn't work on screens logged into
other machines. So I can't even try to show you what I see.
> Hans
>
> Am 21.11.25 um 19:18 schrieb gene heskett:
>>
>>
>> On 11/20/25 16:05, andy pugh wrote:
>>> On Thu, 20 Nov 2025 at 20:10, gene heskett <ghe...@sh...>
>>> wrote:
>>>
>>>> Is there a way to A; get rid of the very low contrast and
>>>> B: force the use of a larger font such that I can still
>>>> read it when it does not have "focus"?
>>> You could experiment with the high contrast styles in the desktop
>>> manager, though that doesn't seem to have much effect on halmeter.
>> I have added that dir and css file which didn't exist, getting
>> a fixed black background which helps a bit but the text size
>> of 20 doesn't make it bigger. I've not tried larger values. I will
>> when next at the machines own keyboard. Currently I am
>> attempting to reconfigure it back to 3 axis for doing some
>> simple EDM. I have the hardware to make the edm feed
>> automatic, winding my own transformer to measure the
>> sparking activity & making that an analogue voltage to
>> present to a 7i76D analogue input pin. If I am successful, you
>> will get schematics that could be used W-EDM machine.
>>>
>>
>> Cheers, Gene Heskett, CET.
>
>
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers
Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Don't poison our oceans, interdict drugs at the src.
|
|
From: Hans U. <han...@gm...> - 2025-11-21 21:47:11
|
With that CSS I get a white background with 20 pt font size (though it
needs some fine tuning to not affect other applications hat much):
notebook*,box*{
background-color: white;
font-size: 20;
}
Hans
Am 21.11.25 um 19:18 schrieb gene heskett:
>
>
> On 11/20/25 16:05, andy pugh wrote:
>> On Thu, 20 Nov 2025 at 20:10, gene heskett <ghe...@sh...> wrote:
>>
>>> Is there a way to A; get rid of the very low contrast and
>>> B: force the use of a larger font such that I can still
>>> read it when it does not have "focus"?
>> You could experiment with the high contrast styles in the desktop
>> manager, though that doesn't seem to have much effect on halmeter.
> I have added that dir and css file which didn't exist, getting
> a fixed black background which helps a bit but the text size
> of 20 doesn't make it bigger. I've not tried larger values. I will
> when next at the machines own keyboard. Currently I am
> attempting to reconfigure it back to 3 axis for doing some
> simple EDM. I have the hardware to make the edm feed
> automatic, winding my own transformer to measure the
> sparking activity & making that an analogue voltage to
> present to a 7i76D analogue input pin. If I am successful, you
> will get schematics that could be used W-EDM machine.
>>
>
> Cheers, Gene Heskett, CET.
|
|
From: gene h. <ghe...@sh...> - 2025-11-21 18:18:26
|
On 11/20/25 16:05, andy pugh wrote: > On Thu, 20 Nov 2025 at 20:10, gene heskett <ghe...@sh...> wrote: > >> Is there a way to A; get rid of the very low contrast and >> B: force the use of a larger font such that I can still >> read it when it does not have "focus"? > You could experiment with the high contrast styles in the desktop > manager, though that doesn't seem to have much effect on halmeter. I have added that dir and css file which didn't exist, getting a fixed black background which helps a bit but the text size of 20 doesn't make it bigger. I've not tried larger values. I will when next at the machines own keyboard. Currently I am attempting to reconfigure it back to 3 axis for doing some simple EDM. I have the hardware to make the edm feed automatic, winding my own transformer to measure the sparking activity & making that an analogue voltage to present to a 7i76D analogue input pin. If I am successful, you will get schematics that could be used W-EDM machine. > Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Don't poison our oceans, interdict drugs at the src. |
|
From: gene h. <ghe...@sh...> - 2025-11-21 17:50:03
|
On 11/21/25 06:46, J.M. Garcia wrote: > El jue, 20 nov 2025 a las 23:55, gene heskett (<ghe...@sh...>) > escribió: > >>> from the hal file: >>> # ---manual tool change signals--- >>> loadusr -W hal_manualtoolchange >>> net tool-change-request <= iocontrol.0.tool-change => >>> hal_manualtoolchange.change <<< does not exist. >>> net tool-change-confirmed <= iocontrol.0.tool-changed => >>> hal_manualtoolchange.changed >>> net tool-number <= iocontrol.0.tool-prep-number => >>> hal_manualtoolchange.number >>> net tool-prepare-loopback <= iocontrol.0.tool-prepare => >>> iocontrol.0.tool-prepared And it all works normally IF I login with ssh -X gene@alias. W/o the -X no gfx which was the REAL error. At 91 I've reached that age where I don't recall what if anything. I had for breakfast. Embarrassing. All of this takes place on my side of a router running dd-wrt. So I don't worry much about hackers, no one has gotten in in 25 years yet every machine here can browse the net. dd-wrt has very sharp teeth, an excellent guard dog.. >>> This is 2.10-pre running on an old bullseye install >> > Ok, Gene. > > My first question would be whether the user component hal_manualtoolchange > loads and functions correctly. > > In a terminal: > > xiuser@HPi7:~$halrun > halcmd: loadusr -W hal_manualtoolchange ( + popup window) > halcmd: show pin > Component Pins: > Owner Type Dir Value Name > 4 bit IN FALSE hal_manualtoolchange.change > 4 bit IN FALSE hal_manualtoolchange.change_button > 4 bit OUT FALSE hal_manualtoolchange.changed > 4 s32 IN 0 hal_manualtoolchange.number > > halcmd: start > halcmd: setp hal_manualtoolchange.change TRUE (+ manual tool change popup > window) > halcmd: show pin > Component Pins: > Owner Type Dir Value Name > 4 bit IN TRUE hal_manualtoolchange.change > 4 bit IN FALSE hal_manualtoolchange.change_button > 4 bit OUT TRUE hal_manualtoolchange.changed > 4 s32 IN 0 hal_manualtoolchange.number > halcmd: stop > halcmd: exit > > As you can see, the component loads and changes values correctly. > I am using a RIP 2.10.pre installation. The component compiled perfectly. > > Regards Thanks J.M. Garcia. > _______________________________________________ > Emc-developers mailing list > Emc...@li... > https://lists.sourceforge.net/lists/listinfo/emc-developers Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Don't poison our oceans, interdict drugs at the src. |
|
From: J.M. G. <jmg...@gm...> - 2025-11-21 11:45:23
|
El jue, 20 nov 2025 a las 23:55, gene heskett (<ghe...@sh...>)
escribió:
> > from the hal file:
> > # ---manual tool change signals---
>
> > loadusr -W hal_manualtoolchange
> > net tool-change-request <= iocontrol.0.tool-change =>
> > hal_manualtoolchange.change <<< does not exist.
> > net tool-change-confirmed <= iocontrol.0.tool-changed =>
> > hal_manualtoolchange.changed
> > net tool-number <= iocontrol.0.tool-prep-number =>
> > hal_manualtoolchange.number
> > net tool-prepare-loopback <= iocontrol.0.tool-prepare =>
> > iocontrol.0.tool-prepared
>
> > This is 2.10-pre running on an old bullseye install
>
>
Ok, Gene.
My first question would be whether the user component hal_manualtoolchange
loads and functions correctly.
In a terminal:
xiuser@HPi7:~$halrun
halcmd: loadusr -W hal_manualtoolchange ( + popup window)
halcmd: show pin
Component Pins:
Owner Type Dir Value Name
4 bit IN FALSE hal_manualtoolchange.change
4 bit IN FALSE hal_manualtoolchange.change_button
4 bit OUT FALSE hal_manualtoolchange.changed
4 s32 IN 0 hal_manualtoolchange.number
halcmd: start
halcmd: setp hal_manualtoolchange.change TRUE (+ manual tool change popup
window)
halcmd: show pin
Component Pins:
Owner Type Dir Value Name
4 bit IN TRUE hal_manualtoolchange.change
4 bit IN FALSE hal_manualtoolchange.change_button
4 bit OUT TRUE hal_manualtoolchange.changed
4 s32 IN 0 hal_manualtoolchange.number
halcmd: stop
halcmd: exit
As you can see, the component loads and changes values correctly.
I am using a RIP 2.10.pre installation. The component compiled perfectly.
Regards
|
|
From: Robert S. <rm...@un...> - 2025-11-21 09:18:18
|
Am Donnerstag, dem 20.11.2025 um 17:10 -0500 schrieb gene heskett: > > Which document are you missing in the docs? > docs for hal. Its pretty simple but I find I need to experiment with > the == and =< => syntax from time to time. the "net" command in hal ignores "==", "=>" and so on, that is purely there to document intent. LinuxCNC HAL documentation is here https://linuxcnc.org/docs/html/ under "HAL" resp. Chapter 5 in https://linuxcnc.org/docs/stable/pdf/LinuxCNC_Documentation.pdf -- Robert Schöftner <rm...@un...> |
|
From: andy p. <bod...@gm...> - 2025-11-21 09:07:32
|
On Thu, 20 Nov 2025 at 22:55, gene heskett <ghe...@sh...> wrote: > Pin 'hal_manualtoolchange.change' does not exist Presumably hal_manualtoolchange isn't loading. There should be further clues in the debug output. > This is 2.10-pre running on an old bullseye install Technically 2.10 isn't supported on anything older than Bookworm. But that's unlikely to _suddenly_ be the problem. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 |
|
From: gene h. <ghe...@sh...> - 2025-11-20 22:52:43
|
On 11/20/25 15:26, Hans Unzner wrote: > I think you can play around with the CSS to get a higher contrast > (adjust the background color etc.). > For the font I can only refer to my answer of your question from march > 2022: https://sourceforge.net/p/emc/mailman/message/37647667/ > Which document are you missing in the docs? > New problem: none of my previous configs will now run. This code at the bottom of the .hal file, unchanged in 2 decades; errors now: twopass: Error in file ./go704-xyz-edm.hal: Pin 'hal_manualtoolchange.change' does not exist Shutting down and cleaning up LinuxCNC... from the hal file: # ---manual tool change signals--- loadusr -W hal_manualtoolchange net tool-change-request <= iocontrol.0.tool-change => hal_manualtoolchange.change <<< does not exist. net tool-change-confirmed <= iocontrol.0.tool-changed => hal_manualtoolchange.changed net tool-number <= iocontrol.0.tool-prep-number => hal_manualtoolchange.number net tool-prepare-loopback <= iocontrol.0.tool-prepare => iocontrol.0.tool-prepared This is 2.10-pre running on an old bullseye install > Hans > > Am 20.11.25 um 21:07 schrieb gene heskett: >> Diabetes other medication and 91 years is beginning to >> affect my eyesight. >> >> Is there a way to A; get rid of the very low contrast and >> B: force the use of a larger font such that I can still >> read it when it does not have "focus"? >> >> ISTR there was a mention of such in the now apparently >> discontinued hal document. But that been gone about a >> decade now. Where is that documentation now? >> >> Thanks everybody. >> >> Cheers, Gene Heskett, CET. > > > > _______________________________________________ > Emc-developers mailing list > Emc...@li... > https://lists.sourceforge.net/lists/listinfo/emc-developers > . Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Don't poison our oceans, interdict drugs at the src. |
|
From: gene h. <ghe...@sh...> - 2025-11-20 22:10:23
|
On 11/20/25 15:26, Hans Unzner wrote: > I think you can play around with the CSS to get a higher contrast > (adjust the background color etc.). > For the font I can only refer to my answer of your question from march > 2022: https://sourceforge.net/p/emc/mailman/message/37647667/ Creating that file gave me an unchanging dark grey background but did not appear to effect a size of text change, but the black does help the visibility enough to be read a little easier. Thank you Hans. > Which document are you missing in the docs? docs for hal. Its pretty simple but I find I need to experiment with the == and =< => syntax from time to time. > > Hans > > Am 20.11.25 um 21:07 schrieb gene heskett: >> Diabetes other medication and 91 years is beginning to >> affect my eyesight. >> >> Is there a way to A; get rid of the very low contrast and >> B: force the use of a larger font such that I can still >> read it when it does not have "focus"? >> >> ISTR there was a mention of such in the now apparently >> discontinued hal document. But that been gone about a >> decade now. Where is that documentation now? >> >> Thanks everybody. >> >> Cheers, Gene Heskett, CET. > > > > _______________________________________________ > Emc-developers mailing list > Emc...@li... > https://lists.sourceforge.net/lists/listinfo/emc-developers > . Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Don't poison our oceans, interdict drugs at the src. |
|
From: andy p. <bod...@gm...> - 2025-11-20 21:04:50
|
On Thu, 20 Nov 2025 at 20:10, gene heskett <ghe...@sh...> wrote: > Is there a way to A; get rid of the very low contrast and > B: force the use of a larger font such that I can still > read it when it does not have "focus"? You could experiment with the high contrast styles in the desktop manager, though that doesn't seem to have much effect on halmeter. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 |
|
From: Hans U. <han...@gm...> - 2025-11-20 20:26:18
|
I think you can play around with the CSS to get a higher contrast (adjust the background color etc.). For the font I can only refer to my answer of your question from march 2022: https://sourceforge.net/p/emc/mailman/message/37647667/ Which document are you missing in the docs? Hans Am 20.11.25 um 21:07 schrieb gene heskett: > Diabetes other medication and 91 years is beginning to > affect my eyesight. > > Is there a way to A; get rid of the very low contrast and > B: force the use of a larger font such that I can still > read it when it does not have "focus"? > > ISTR there was a mention of such in the now apparently > discontinued hal document. But that been gone about a > decade now. Where is that documentation now? > > Thanks everybody. > > Cheers, Gene Heskett, CET. |
|
From: gene h. <ghe...@sh...> - 2025-11-20 20:07:50
|
Diabetes other medication and 91 years is beginning to affect my eyesight. Is there a way to A; get rid of the very low contrast and B: force the use of a larger font such that I can still read it when it does not have "focus"? ISTR there was a mention of such in the now apparently discontinued hal document. But that been gone about a decade now. Where is that documentation now? Thanks everybody. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Don't poison our oceans, interdict drugs at the src. |
|
From: klemen d. <k.d...@gm...> - 2025-11-20 15:34:57
|
Dear Bertho, Thank you for your fast response. You were right, this (volatile) solved the problem. The same program now works fine :) So much time wasted for such a stupid mistake... Thank you! :) Regards, Klemen On Thu, 20 Nov 2025 at 13:26, Bertho Stultiens <lc...@va...> wrote: > On 11/20/25 12:51 PM, klemen dovrtel wrote: > > *(rtapi_u32*)(pci_device.ptr_bar2 + 0x0000) = 0x11111111; nanosleep > > (&ts_dtLong, NULL); > > *(rtapi_u32*)(pci_device.ptr_bar2 + 0x0004) = 0x22222222; > > Using '*(rtapi_u32 *)(ptr + 0) = xyz' several times may not result in > what you expect. The compiler sees multiple references to the same > address(es) and may opt to cache the result(s). These addresses are > actually volatile targets and must be declared as such. > > > Maybe you should try: > volatile rtapi_u32 *addr0 = (volatile rtapi_u32 *)(pci_device.ptr_bar2 + > 0x0000); > volatile rtapi_u32 *addr4 = (volatile rtapi_u32 *)(pci_device.ptr_bar2 + > 0x0004); > > // Write > *addr0 = 0x11111111; > *addr4 = 0x22222222; > > // Read > rtapi_print_msg(RTAPI_MSG_INFO, "rd offs 0: %08x.\n", *addr0); > rtapi_print_msg(RTAPI_MSG_INFO, "rd offs 4: %08x.\n", *addr4); > > // Write > *addr0 = 0x33333333; > *addr4 = 0x44444444; > > // Read > rtapi_print_msg(RTAPI_MSG_INFO, "rd offs 0: %08x.\n", *addr0); > rtapi_print_msg(RTAPI_MSG_INFO, "rd offs 4: %08x.\n", *addr4); > > ... etc ... > > > -- > Greetings Bertho > > (disclaimers are disclaimed) > > > > _______________________________________________ > Emc-developers mailing list > Emc...@li... > https://lists.sourceforge.net/lists/listinfo/emc-developers > |
|
From: Bertho S. <lc...@va...> - 2025-11-20 12:23:44
|
On 11/20/25 12:51 PM, klemen dovrtel wrote: > *(rtapi_u32*)(pci_device.ptr_bar2 + 0x0000) = 0x11111111; nanosleep > (&ts_dtLong, NULL); > *(rtapi_u32*)(pci_device.ptr_bar2 + 0x0004) = 0x22222222; Using '*(rtapi_u32 *)(ptr + 0) = xyz' several times may not result in what you expect. The compiler sees multiple references to the same address(es) and may opt to cache the result(s). These addresses are actually volatile targets and must be declared as such. Maybe you should try: volatile rtapi_u32 *addr0 = (volatile rtapi_u32 *)(pci_device.ptr_bar2 + 0x0000); volatile rtapi_u32 *addr4 = (volatile rtapi_u32 *)(pci_device.ptr_bar2 + 0x0004); // Write *addr0 = 0x11111111; *addr4 = 0x22222222; // Read rtapi_print_msg(RTAPI_MSG_INFO, "rd offs 0: %08x.\n", *addr0); rtapi_print_msg(RTAPI_MSG_INFO, "rd offs 4: %08x.\n", *addr4); // Write *addr0 = 0x33333333; *addr4 = 0x44444444; // Read rtapi_print_msg(RTAPI_MSG_INFO, "rd offs 0: %08x.\n", *addr0); rtapi_print_msg(RTAPI_MSG_INFO, "rd offs 4: %08x.\n", *addr4); ... etc ... -- Greetings Bertho (disclaimers are disclaimed) |
|
From: klemen d. <k.d...@gm...> - 2025-11-20 11:51:40
|
Hello everybody,
I am working with a pciE FPGA card and i am trying to write to memory
mapped memory as fast as possible. If I generate a sequence of
successive write commands, nothing gets written.
I was not sure if there is a problem with the fpga pcie IP core, so I
decided to buy a LPT port pcie card (based on AX99100 chip) and test it. I
tried the same test again and the result is the same - nothing gets
written. The registers seem to have just one byte writable, but I think
this is not crucial here.
Does anybody have an idea how I should write an array of data to a pcie
card as fast as possible? I did try to add a delay in between and that
helped, but this added a lot of delay and I am not sure how close to the
limitation is that.
Please find my code and the result (on LPT port card) below.
Regards
Klemen
code snippet
---------------
pci_device.ptr_bar0 = rtapi_pci_ioremap_bar(dev, 0);
rtapi_print_msg(RTAPI_MSG_INFO, "lptPortdriver: bar 0 mapped to %p\n",
pci_device.ptr_bar0);
pci_device.ptr_bar2 = rtapi_pci_ioremap_bar(dev, 2);
rtapi_print_msg(RTAPI_MSG_INFO, "pciLedTest_wb: bar 2 mapped to %p\n",
pci_device.ptr_bar2);
rtapi_print_msg(RTAPI_MSG_INFO, "\n\n");
rtapi_print("max_delay_avaliable = %ld ns\n", rtapi_delay_max());
rtapi_print_msg(RTAPI_MSG_INFO, "lptPortdriver - test1: write to led
register\n");
t1 = rtapi_get_time(); // returns time in ns
*(rtapi_u32*)(pci_device.ptr_bar2 + 0x0000) = 0x11111111; nanosleep
(&ts_dtLong, NULL);
*(rtapi_u32*)(pci_device.ptr_bar2 + 0x0004) = 0x22222222;
t2 = rtapi_get_time(); // returns time in ns
rtapi_print_msg(RTAPI_MSG_INFO, "lptPortDriver read32: offset 0x0000:
%08x.\n", *(rtapi_u32*)(pci_device.ptr_bar2 + 0x0000) );
rtapi_print_msg(RTAPI_MSG_INFO, "lptPortDriver read32: offset 0x0004:
%08x.\n", *(rtapi_u32*)(pci_device.ptr_bar2 + 0x0004) );
rtapi_print_msg(RTAPI_MSG_INFO, "lptPortdriver - test2: write to led
register\n");
t3 = rtapi_get_time(); // returns time in ns
*(rtapi_u32*)(pci_device.ptr_bar2 + 0x0000) = 0x33333333; rtapi_delay(1);
*(rtapi_u32*)(pci_device.ptr_bar2 + 0x0004) = 0x44444444;
t4 = rtapi_get_time(); // returns time in ns
rtapi_print_msg(RTAPI_MSG_INFO, "lptPortDriver read32: offset 0x0000:
%08x.\n", *(rtapi_u32*)(pci_device.ptr_bar2 + 0x0000) );
rtapi_print_msg(RTAPI_MSG_INFO, "lptPortDriver read32: offset 0x0004:
%08x.\n", *(rtapi_u32*)(pci_device.ptr_bar2 + 0x0004) );
rtapi_print_msg(RTAPI_MSG_INFO, "lptPortdriver - test3: write to led
register\n");
t5 = rtapi_get_time(); // returns time in ns
*(rtapi_u32*)(pci_device.ptr_bar2 + 0x0000) = 0x55555555;
*(rtapi_u32*)(pci_device.ptr_bar2 + 0x0004) = 0x66666666;
t6 = rtapi_get_time(); // returns time in ns
rtapi_print_msg(RTAPI_MSG_INFO, "lptPortDriver read32: offset 0x0000:
%08x.\n", *(rtapi_u32*)(pci_device.ptr_bar2 + 0x0000) );
rtapi_print_msg(RTAPI_MSG_INFO, "lptPortDriver read32: offset 0x0004:
%08x.\n", *(rtapi_u32*)(pci_device.ptr_bar2 + 0x0004) );
tdiff1 = t2 - t1;
tdiff2 = t4 - t3;
tdiff3 = t6 - t5;
rtapi_print("nanosleep Tdiff1 = %ld ns\n", tdiff1);
rtapi_print("rtapidelay Tdiff2 = %ld ns\n", tdiff2);
rtapi_print("rtapidelay Tdiff3 = %ld ns\n", tdiff3);
output
---------------
RTAPI_PCI: Map BAR 0
Failed to remap MMIO 0 of PCI device 0000:05:00.2: No such device
lptPortdriver: bar 0 mapped to (nil)
RTAPI_PCI: Map BAR 2
pciLedTest_wb: bar 2 mapped to 0x7f2d4b2bd000
max_delay_avaliable = 10000 ns
lptPortdriver - test1: write to led register
lptPortDriver read32: offset 0x0000: 00000011.
lptPortDriver read32: offset 0x0004: 00000022.
lptPortdriver - test2: write to led register
lptPortDriver read32: offset 0x0000: 00000033.
lptPortDriver read32: offset 0x0004: 00000044.
lptPortdriver - test3: write to led register
lptPortDriver read32: offset 0x0000: 00000033.
lptPortDriver read32: offset 0x0004: 00000044.
nanosleep Tdiff1 = 100054728 ns
rtapidelay Tdiff2 = 55561 ns
rtapidelay Tdiff3 = 38 ns
|
116 messages has been excluded from this view by a project administrator.
