Re: [Emc-developers] /usr/share/doc has many .ini files but .ini files are not documentation

[Alec Ari via Emc-developers]

Configs show up now, but now there's a new problem:

ntu@ryzen ~ $ linuxcnc
LINUXCNC - 2.9.0~pre0
Machine configuration directory is '/home/ntu/linuxcnc/configs/sim.axis'
Machine configuration file is 'axis.ini'
can't find package Linuxcnc
    while executing
"package require Linuxcnc "
    (file "/usr/share/linuxcnc/hallib/check_config.tcl" line 187)
check_config validation failed
LinuxCNC terminated with an error.  You can find more information in the log:
    /home/ntu/linuxcnc_debug.txt
and
    /home/ntu/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal

ntu@ryzen ~ $ cat linuxcnc*.txt
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
INIFILE=/home/ntu/linuxcnc/configs/sim.axis/axis.ini
VERSION=1.1

ntu@ryzen ~ $ doas dmesg | tail -n 50
doas (ntu@ryzen) password:
[   12.919007] [drm]   Encoders:
[   12.919007] [drm] DFP1: INTERNAL_UNIPHY2
[   12.919008] [drm] Connector 1:
[   12.919009] [drm]   HDMI-A-1
[   12.919009] [drm]   HPD3
[   12.919009] [drm]   DDC: 0x1954 0x1954 0x1955 0x1955 0x1956 0x1956 0x1957 
0x1957
[   12.919010] [drm]   Encoders:
[   12.919011] [drm] DFP2: INTERNAL_UNIPHY2
[   12.919011] [drm] Connector 2:
[   12.919012] [drm]   DVI-D-1
[   12.919012] [drm]   HPD1
[   12.919012] [drm]   DDC: 0x1958 0x1958 0x1959 0x1959 0x195a 0x195a 0x195b 
0x195b
[   12.919014] [drm]   Encoders:
[   12.919014] [drm] DFP3: INTERNAL_UNIPHY1
[   12.919014] [drm] Connector 3:
[   12.919015] [drm]   DVI-D-2
[   12.919015] [drm]   HPD6
[   12.919016] [drm]   DDC: 0x1960 0x1960 0x1961 0x1961 0x1962 0x1962 0x1963 
0x1963
[   12.919017] [drm]   Encoders:
[   12.919017] [drm] DFP4: INTERNAL_UNIPHY
[   12.952812] [drm] Found UVD firmware Version: 1.64 Family ID: 9
[   13.036639] [drm] Found VCE firmware Version: 50.10 Binary ID: 2
[   13.037147] [drm] PCIE gen 3 link speeds already enabled
[   13.144615] [drm] UVD initialized successfully.
[   13.265656] [drm] VCE initialized successfully.
[   13.266285] amdgpu :1e:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 11, 
active_cu_number 40
[   13.269456] [drm] Initialized amdgpu 3.46.0 20150101 for :1e:00.0 on 
minor 0
[   13.329332] EXT4-fs (sda4): re-mounted. Quota mode: disabled.
[   13.368157] fbcon: amdgpudrmfb (fb0) is primary device
[   13.527652] Console: switching to colour frame buffer device 240x67
[   13.641937] amdgpu :1e:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[   13.972989] EXT4-fs (sda3): mounted filesystem with ordered data mode. Quota 
mode: disabled.
[   16.344279] Generic FE-GE Realtek PHY r8169-0-1800:00: attached PHY driver 
(mii_bus:phy_addr=r8169-0-1800:00, irq=MAC)
[   16.511525] r8169 :18:00.0 enp24s0: Link is Down
[   17.410748] elogind-daemon[1647]: New seat seat0.
[   17.414355] elogind-daemon[1647]: Watching system buttons on 
/dev/input/event1 (Power Button)
[   17.414477] elogind-daemon[1647]: Watching system buttons on 
/dev/input/event0 (Power Button)
[   17.414621] elogind-daemon[1647]: Watching system buttons on 
/dev/input/event2 (Razer Razer Huntsman V2)
[   17.414756] elogind-daemon[1647]: Watching system buttons on 
/dev/input/event3 (Razer Razer Huntsman V2 Keyboard)
[   17.415074] elogind-daemon[1647]: Watching system buttons on 
/dev/input/event8 (ROCCAT ROCCAT Tyon Black Consumer Control)
[   19.588787] r8169 :18:00.0 enp24s0: Link is Up - 1Gbps/Full - flow 
control rx/tx
[   25.121116] elogind-daemon[1647]: New session c1 of user root.
[   34.414130] elogind-daemon[1647]: Removed session c1.
[   34.472972] elogind-daemon[1647]: New session c2 of user ntu.
[   47.135966] elogind-daemon[1647]: New session c3 of user root.
[  393.109299] fuse: init (API version 7.36)
[ 3040.998846] elogind-daemon[1647]: Removed session c2.
[ 3041.799691] elogind-daemon[1647]: New session c4 of user root.
[ 3047.501076] elogind-daemon[1647]: Removed session c4.
[ 3047.525401] elogind-daemon[1647]: New session c5 of user ntu.

Line of code failing:

ntu@ryzen ~ $ sed -n 187p /usr/share/linuxcnc/hallib/check_config.tcl
package require Linuxcnc ;# parse_ini

.ini file:

ntu@ryzen ~ $ cat linuxcnc/configs/sim.axis/axis.ini
# EMC controller parameters for a simulated machine.

# General note: Comments can either be preceded with a # or ; - either is
# acceptable, although # is in keeping with most linux config files.

# General section -
[EMC]

# Version of this INI file
VERSION = 1.1

# Name of machine, for use with display, etc.
MACHINE = LinuxCNC-HAL-SIM-AXIS

# Debug level, 0 means no messages. See src/emc/nml_int/emcglb.h for others
#DEBUG = 0x7FFF
DEBUG = 0

# Sections for display options 
[DISPLAY]

# Name of 

Re: [Emc-developers] /usr/share/doc has many .ini files but .ini files are not documentation

[Alec Ari via Emc-developers]

Ah.. Gentoo compresses all documentation by default:

ntu@ryzen ~ $ ls /usr/share/doc/linuxcnc/examples/sample-configs/sim/axis/
README.bz2   foam   ini_with_includes    
ldelta_demo_es.txt.bz2    rdelta.ini.bz2
README_es.bz2    gantry iocontrolv2  
minimal_xyz.ini.bz2   remap
axis.ini.bz2 geometry   ja_tests 
moveoff   rose_engine
axis_9axis.ini.bz2   gladevcp   lathe-fanucy 
nc_files  sim.tbl.bz2
axis_mm.ini.bz2  halui_pyvcp    lathe.ini.bz2    ngcgui 
   sim_mm.tbl.bz2
canterp.ini.bz2  histogram_demo.ini.bz2 lathe.tbl.bz2    
orphans   simpockets.tbl.bz2
canterp_example.can.bz2  histogram_demo.txt.bz2 lathe.xml.bz2    
panelui-demo  simtcl
classicladder    histogram_demo_es.txt.bz2  lathe_multispindle   
pentapod  spindle_orient
corexy   historical_lathe.ini.bz2   lathe_postgui.hal    
postgui_calib_helper.hal.bz2  twopass
db_demo  ini_hal_demo.ini.bz2   ldelta.ini.bz2   
profile_axis.ini.bz2  vismach
external_offsets ini_hal_demo.txt.bz2   ldelta_demo.ini.bz2  qtvcp  
   wrapped_rotary
extrajoints  ini_hal_demo_es.txt    ldelta_demo.txt.bz2  
random_tc.ini.bz2 xhc-hb04

https://devmanual.gentoo.org/ebuild-writing/functions/src_install/docompress/index.html

Well that explains everything!!!

Alec


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] /usr/share/doc has many .ini files but .ini files are not documentation

[Alec Ari via Emc-developers]

So I fixed the symlink but none of the other configs are actually showing up, 
this is what I added:

https://github.com/NTULINUX/ntu_overlay/commit/5e07d93a625f2acd459c85e7a6c427718f857457

Does anything look odd here?

ntu@ryzen ~/ntu_overlay $ ls -la /usr/share/doc/linuxcnc/examples/*/*
-rw-r--r--  1 root root  5350 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/3D_Chips.html
-rw-r--r--  1 root root 29069 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/3D_Chips.ngc.bz2
-rw-r--r--  1 root root 69393 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/3D_Chips.pdf
-rw-r--r--  1 root root   425 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/3dtest.ngc.bz2
-rwxr-xr-x  1 root root   381 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/M101.bz2
-rw-r--r--  1 root root   403 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/M102.c.bz2
-rw-r--r--  1 root root  9494 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/arcspiral.ngc.bz2
-rw-r--r--  1 root root   179 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/b-index.ngc.bz2
-rw-r--r--  1 root root   477 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/butterfly.ngc.bz2
-rw-r--r--  1 root root  1933 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/cds.ngc.bz2
-rw-r--r--  1 root root   497 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/comp-g1.ngc.bz2
-rw-r--r--  1 root root   167 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/comp.ngc.bz2
-rw-r--r--  1 root root   322 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/comp311.ngc.bz2
-rw-r--r--  1 root root   334 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/comp311_2.ngc.bz2
-rw-r--r--  1 root root   420 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/cone.ngc.bz2
-rw-r--r--  1 root root  1058 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/daisy.ngc.bz2
-rw-r--r--  1 root root   173 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/factorial.ngc.bz2
-rw-r--r--  1 root root   848 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/filtertest-gui.py.bz2
-rw-r--r--  1 root root   298 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/filtertest.py.bz2
-rw-r--r--  1 root root   454 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/flowsnake.ngc.bz2
-rw-r--r--  1 root root   334 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/flowsnake.py.bz2
-rw-r--r--  1 root root   180 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/g20sub.ngc.bz2
-rw-r--r--  1 root root   763 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/g76.ngc.bz2
-rw-r--r--  1 root root   281 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/g881.ngc.bz2
-rw-r--r--  1 root root    94 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/g881min.ngc
-rw-r--r--  1 root root   102 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/g882.ngc
-rw-r--r--  1 root root   663 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/gmoccapy_2_tools_with_cutter_radius_compensation.ngc.bz2
-rw-r--r--  1 root root   502 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/gridprobe.ngc.bz2
-rw-r--r--  1 root root   242 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/hole-circle.ngc.bz2
-rw-r--r--  1 root root  2544 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/holecircle.py.bz2
-rw-r--r--  1 root root    56 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/increment.ngc
-rw-r--r--  1 root root   190 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/involute.py.bz2
-rw-r--r--  1 root root   763 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/lathe-g76.ngc.bz2
-rw-r--r--  1 root root   353 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/lathe_g70_71_demo.ngc.bz2
-rw-r--r--  1 root root   167 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/lathe_g7x_face_boring.ngc.bz2
-rw-r--r--  1 root root   354 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/lathe_g7x_quadrants.ngc.bz2
-rw-r--r--  1 root root   754 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/lathe_pawn.ngc.bz2
-rw-r--r--  1 root root   171 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/lathecomp.ngc.bz2
-rw-r--r--  1 root root   229 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/m250.ngc.bz2
-rw-r--r--  1 root root   511 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/m61demo.ngc.bz2
-rw-r--r--  1 root root  1013 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/m6demo.ngc.bz2
-rw-r--r--  1 root root   101 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/m6remap.ngc
-rw-r--r--  1 root root   437 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/m70m72-demo.ngc.bz2
-rw-r--r--  1 root root   563 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/m73-demo.ngc.bz2
-rw-r--r--  1 root root   274 Jul 28 21:53 
/usr/share/doc/linuxcnc/examples/nc_files/m75.ngc.bz2
-rw-r--r--  1 root root   228 Jul 28 21:53 

Re: [Emc-developers] /usr/share/doc has many .ini files but .ini files are not documentation

[Alec Ari via Emc-developers]

I think the problem here is actually a symlink to nc_files that the Gentoo 
package manager is breaking somehow rather than the .ini files in 
/usr/share/doc.

Need to figure out where it wants it and what's missing.

Current installation:

ntu@ryzen ~ $ ls -la /usr/share/doc/linuxcnc/examples/sample-configs/*
-rw-r--r--  1 root root 1903 Jul 28 21:40 
/usr/share/doc/linuxcnc/examples/sample-configs/maintainer.txt.bz2
-rw-r--r--  1 root root 2087 Jul 28 21:40 
/usr/share/doc/linuxcnc/examples/sample-configs/maintainer_es.txt.bz2
lrwxrwxrwx  1 root root   11 Jul 28 21:40 
/usr/share/doc/linuxcnc/examples/sample-configs/nc_files -> ../nc_files 
(flashing red, broken symlink)

/usr/share/doc/linuxcnc/examples/sample-configs/apps:
total 56
drwxr-xr-x  8 root root 4096 Jul 28 21:41 .
drwxr-xr-x  8 root root 4096 Jul 28 21:41 ..
-rw-r--r--  1 root root  210 Jul 28 21:40 README.bz2
-rw-r--r--  1 root root  247 Jul 28 21:40 README_es.bz2
drwxr-xr-x 11 root root 4096 Jul 28 21:41 gladevcp
drwxr-xr-x  2 root root 4096 Jul 28 21:41 halrun
-rwxr-xr-x  1 root root   27 Jul 28 21:40 info.demo
-rw-r--r--  1 root root  263 Jul 28 21:40 info.txt.bz2
-rw-r--r--  1 root root  294 Jul 28 21:40 info_es.txt.bz2
drwxr-xr-x  2 root root 4096 Jul 28 21:41 latency
-rw-r--r--  1 root root  130 Jul 28 21:40 nodemocopy.bz2
drwxr-xr-x  2 root root 4096 Jul 28 21:41 parport
drwxr-xr-x  2 root root 4096 Jul 28 21:41 pyvcp
drwxr-xr-x  2 root root 4096 Jul 28 21:41 xhc-hb04

/usr/share/doc/linuxcnc/examples/sample-configs/attic:
total 28
drwxr-xr-x 5 root root 4096 Jul 28 21:41 .
drwxr-xr-x 8 root root 4096 Jul 28 21:41 ..
-rw-r--r-- 1 root root  119 Jul 28 21:40 README
-rw-r--r-- 1 root root  146 Jul 28 21:40 README_es.bz2
drwxr-xr-x 2 root root 4096 Jul 28 21:41 dallur-thc
drwxr-xr-x 2 root root 4096 Jul 28 21:41 demo_mazak
drwxr-xr-x 4 root root 4096 Jul 28 21:41 unclaimed

/usr/share/doc/linuxcnc/examples/sample-configs/by_interface:
total 48
drwxr-xr-x 10 root root 4096 Jul 28 21:41 .
drwxr-xr-x  8 root root 4096 Jul 28 21:41 ..
-rw-r--r--  1 root root   60 Jul 28 21:40 README
-rw-r--r--  1 root root   73 Jul 28 21:40 README_es
drwxr-xr-x  3 root root 4096 Jul 28 21:41 general_mechatronics
drwxr-xr-x  5 root root 4096 Jul 28 21:41 mesa
lrwxrwxrwx  1 root root   14 Jul 28 21:40 nc_files -> ../../nc_files (flashing 
red, broken symlink)
drwxr-xr-x 11 root root 4096 Jul 28 21:41 parport
drwxr-xr-x  8 root root 4096 Jul 28 21:41 pico
drwxr-xr-x  4 root root 4096 Jul 28 21:41 pluto
drwxr-xr-x  2 root root 4096 Jul 28 21:41 servotogo
drwxr-xr-x  2 root root 4096 Jul 28 21:41 vigilant
drwxr-xr-x  2 root root 4096 Jul 28 21:41 vitalsystems

/usr/share/doc/linuxcnc/examples/sample-configs/by_machine:
total 44
drwxr-xr-x 9 root root 4096 Jul 28 21:41 .
drwxr-xr-x 8 root root 4096 Jul 28 21:41 ..
-rw-r--r-- 1 root root   56 Jul 28 21:40 README
-rw-r--r-- 1 root root   65 Jul 28 21:40 README_es
drwxr-xr-x 2 root root 4096 Jul 28 21:41 boss
drwxr-xr-x 2 root root 4096 Jul 28 21:41 cooltool
lrwxrwxrwx 1 root root   14 Jul 28 21:40 nc_files -> ../../nc_files (flashing 
red, broken symlink)
drwxr-xr-x 3 root root 4096 Jul 28 21:41 qtplasmac
drwxr-xr-x 2 root root 4096 Jul 28 21:41 scorbot-er-3
drwxr-xr-x 5 root root 4096 Jul 28 21:41 sherline
drwxr-xr-x 2 root root 4096 Jul 28 21:41 smithy
drwxr-xr-x 2 root root 4096 Jul 28 21:41 tormach

/usr/share/doc/linuxcnc/examples/sample-configs/common:
total 36
drwxr-xr-x 3 root root 4096 Jul 28 21:41 .
drwxr-xr-x 8 root root 4096 Jul 28 21:41 ..
-rw-r--r-- 1 root root  615 Jul 28 21:40 client.nml.bz2
drwxr-xr-x 4 root root 4096 Jul 28 21:41 configurable_options
-rw-r--r-- 1 root root  586 Jul 28 21:40 linuxcnc.nml.bz2
-rw-r--r-- 1 root root  594 Jul 28 21:40 linuxcnc_big.nml.bz2
-rw-r--r-- 1 root root  791 Jul 28 21:40 server.nml.bz2
-rw-r--r-- 1 root root 1863 Jul 28 21:40 shuttle.hal.bz2
-rw-r--r-- 1 root root  150 Jul 28 21:40 tool.tbl.bz2

/usr/share/doc/linuxcnc/examples/sample-configs/sim:
total 128
drwxr-xr-x  9 root root 4096 Jul 28 21:41 .
drwxr-xr-x  8 root root 4096 Jul 28 21:41 ..
-rw-r--r--  1 root root  208 Jul 28 21:40 README.bz2
-rw-r--r--  1 root root  218 Jul 28 21:40 README_es.bz2
drwxr-xr-x 31 root root 4096 Jul 28 21:41 axis
drwxr-xr-x  8 root root 4096 Jul 28 21:41 gmoccapy
-rw-r--r--  1 root root  318 Jul 28 21:40 gremlin_view.ui.bz2
-rw-r--r--  1 root root  148 Jul 28 21:40 gs2.hal.bz2
drwxr-xr-x  8 root root 4096 Jul 28 21:41 gscreen
-rw-r--r--  1 root root  898 Jul 28 21:40 hitcounter.py.bz2
-rw-r--r--  1 root root  188 Jul 28 21:40 lathe.tbl.bz2
-rw-r--r--  1 root root  237 Jul 28 21:40 lathe.xml.bz2
-rw-r--r--  1 root root   95 Jul 28 21:40 lathe_postgui.hal
-rw-r--r--  1 root root  723 Jul 28 21:40 manual-example.hal.bz2
-rw-r--r--  1 root root 2016 Jul 28 21:40 manual-example.ui.bz2
lrwxrwxrwx  1 root root   14 Jul 28 21:40 nc_files -> ../../nc_files (flashing 
red, broken symlink)
-rw-r--r--  1 root root  218 Jul 28 21:40 nstools.tbl.bz2
-rw-r--r--  1 root root  370 Jul 28 

Re: [Emc-developers] Protocol on Google Docs Re: LinuxCNC online meeting - 13th of June (next Monday) 20:00 CEST was: "doodle" to set time for a LinuxCNC online meeting

[Petter Reinholdtsen]

[Steffen Möller 2022-06-15]
> This would be a great preparation for a next meeting, which will be
> orchestrated by Rene. We are aiming at about 4-6 weeks from now.

Any news on the next meeting?

-- 
Happy hacking
Petter Reinholdtsen


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

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

[gene heskett]

On 7/28/22 06:37, Hans Unzner wrote:

Maybe
will restart the program at the following line. --> will continue executing
the program at the following line.
?
I'm not happy with this, the word restart is IMO correct because the 
state of the machine
can only be determined by scanning and re-executing all the mode changes 
that have
occurred since the file was initially ran, or at least that's how I've 
understood it since
that "start from line" was added several years ago.  The motion code may 
not be

re-executed, but the mode changes it implies are.

Am I mistaken?

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
Weblate](https://hosted.weblate.org) /
[LinuxCNC](https://hosted.weblate.org/projects/linuxcnc/) / [LinuxCNC
Documentation](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/)
/
[English](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/en/)

## Source string

'M0' - pause a running program temporarily. LinuxCNC remains in the Auto
Mode
so MDI and other manual actions are not enabled. Pressing the resume button
will restart the program at the following line.

## Source string description

type: Plain text

## Comment

I am unhappy with the term "restart". That would imply that something
would be
"re"-executed, which is not the case, and variables are not affected,
either.
I would prefer "the execution of that program continues in the following
line."

[Edit this string](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
docs/en/?checksum=acfba46ddc59075d#comments

)

## Source string location

[src/gcode/m-code.adoc:47](
https://github.com/LinuxCNC/linuxcnc/blob/master/docs/src/gcode/m-code.adoc?plain=1#L47
)

##  Translation Info

All strings|  [
29,515
](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-docs/en/) |


---|---|
Translated strings |  [
29,515
](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
docs/en/?q=state:>=translated) |  [
100%
](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
docs/en/?q=state:>=translated)
Untranslated strings   |  [ 0

](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
docs/en/?q=state:empty)|  [
0%
](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
docs/en/?q=state:empty)
Unfinished strings |  [ 0

](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
docs/en/?q=state:https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
docs/en/?q=state:https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
docs/en/?q=state:needs-editing)|  [
0%
](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
docs/en/?q=state:needs-editing)


[View](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/en/)


[Weblate, the libre continuous localization system.](https://weblate.org/)

Generated on July 28, 2022, 11:53 a.m..

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers



Cheers, Gene Heskett.
--
"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
Genes Web page 



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Addition Ethercat Homing Routine/Variable

[Rod Webster]

Nicklas,
this will be a pretty big brain dump so please read on.

This is where Dewey's work comes in to solve your problem. You can now
write a custom homing component and install it using halcompile.
You need to start by reading the homecomp docs
http://linuxcnc.org/docs/devel/html/man/man9/homecomp.9.html
Then refer to the sample code
https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/homecomp.comp
You also become familiar with homing.c
https://github.com/LinuxCNC/linuxcnc/blob/master/src/emc/motion/homing.c
Homing starts in homing_init()
https://github.com/LinuxCNC/linuxcnc/blob/master/src/emc/motion/homing.c#L1411
You might also like to review Dominic Braun's cia402 component
https://github.com/dbraun1981/hal-cia402 for CANOpen/CIA402 related stuff.

homing_init() in homing.c has been reworked so the default code is moved to
base_homing_init()
This allows a custom version of homecomp to totally rewrite the homing code
in homing_init and other procedures who have base versions in homing.c
So a custom homing module for CANopen devices might live in a file called
canopen_home.comp and contain its own version of homing_init() that starts
the homing process and just waits until the drive signals homing is
completed, then set the joint.N.homed pin to true.

Dominc has some useful stuff in his component and triggered homing
using joint.N.index-enable
But Daniel and I found this was not enough, changes to homing.c was
required. Then Dewey released his custom homing module we are discussing
here.
Dominic's code has two functions read_all() and write_all() to transfer
data to and from ethercat slaves.
I think this could be quite a useful technique. I think this could be
replicated in canopen_home.comp by extending
void read_homing_in_pins() and write_homing_out_pins() and creating any
additional CANopen pins at the joint level.
I did attempt this and got close as I could init the homing process but
cancelling it did not restore the correct state and I did not proceed due
to time constraints.
I will say working in a homecomp becomes quite complex because you have to
deal with all joints at once so additional data (and pins) must be stored in
static custom_home_local_data customH[EMCMOT_MAX_JOINTS];
ref:
https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/homecomp.comp#L96
By comparison the cia402.comp only needs to deal with one joint per
instance.

My work on this is here https://github.com/rodw-au/ciahome but after I
started, Dewey made a lot of changes to simplify writing a custom homing
module. In the version I was working with every procedure in homing.c
needed to be included in the comp by using the base procedures in homing.c.
This is no longer required. You only need to redefine the procedures you
want to redefine. So my work needs to be rewritten to follow the current
code base.

I hope this helps. It would be awesome if a more experienced developer
could have a go at this. Daniel and I will be cheering from the side lines.
I do have a CIA402 test rig set up so I am happy to test subject to time
constraints. You have my email address.

Rod Webster
*1300 896 832*
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au


On Thu, 28 Jul 2022 at 20:12, Nicklas SB Karlsson  wrote:

> tis 2022-05-03 klockan 13:09 +0100 skrev andy pugh:
> > On Tue, 21 Sept 2021 at 15:35, Daniel Dempsey 
> > wrote:
> >
> > > Will try to sort out the rest of homing.c this week and hopefully
> > > test on
> > > the weekend when the shop is quiet.
> >
> > This has been sat in my inbox for months awaiting a reply. In the
> > meantime, Dewey has introduced a system whereby LinuxCNC can be
> > configured to support a custom homing scheme. Have you seen that
> > work?
> >
> > Here is a sample homing  component:
> >
> https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/homecomp.comp
> > The docs for that component:
> > http://linuxcnc.org/docs/devel/html/man/man9/homecomp.9.html
>
> Some commands are limited then not homed and guess motion module tell
> Linuxcnc this. Looking into my .hal file there is however neither an
> input to tell motion it should home nor an output connected somewhere
> to Linuxcnc GUI then it is homed. Not sure what is part of the motion
> module but could see it is named motmod in my .ini file.
>
> Pretty sure there is a problem in motion module as it always do the
> homing by itself running the joint(s) setting the offsets. There is a
> bit output pin in motion module indicating if homing but no possibility
> to tell motion module it is done by externally and not possible tell
> motion module homing is done or in an error. There is most certainly
> also a need to tell motion module if home offset is added or not by
> device itself then homing is completed successfully.
>
>
> Reading CANopen document homing procedure. At first device have to be
> set to special "Homing mode". There i an input bit to tell device start
> or continue homing. There is 

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

[Stuart Stevenson]

PAUSE/CONTINUE with II/> as the symbols. My 22 month old grandson
understands this on my phone and on the tv screen.

Returning to earlier NC/CNC commands is "rewind" to start at the beginning
of the program.

A strip visual cues on the screen showing the major start points such as
tool changes.


On Thu, Jul 28, 2022 at 5:36 AM Hans Unzner  wrote:

> 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
> > Weblate](https://hosted.weblate.org) /
> > [LinuxCNC](https://hosted.weblate.org/projects/linuxcnc/) / [LinuxCNC
> > Documentation](
> https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/)
> > /
> > [English](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/en/
> )
> >
> > ## Source string
> >
> > 'M0' - pause a running program temporarily. LinuxCNC remains in the Auto
> > Mode
> > so MDI and other manual actions are not enabled. Pressing the resume
> button
> > will restart the program at the following line.
> >
> > ## Source string description
> >
> > type: Plain text
> >
> > ## Comment
> >
> > I am unhappy with the term "restart". That would imply that something
> > would be
> > "re"-executed, which is not the case, and variables are not affected,
> > either.
> > I would prefer "the execution of that program continues in the following
> > line."
> >
> > [Edit this string](
> https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> > docs/en/?checksum=acfba46ddc59075d#comments
> > <
> https://hosted.weblate.org/translate/linuxcnc/linuxcnc-docs/en/?checksum=acfba46ddc59075d#comments
> >
> > )
> >
> > ## Source string location
> >
> > [src/gcode/m-code.adoc:47](
> >
> https://github.com/LinuxCNC/linuxcnc/blob/master/docs/src/gcode/m-code.adoc?plain=1#L47
> > )
> >
> > ##  Translation Info
> >
> > All strings|  [
> > 29,515
> > ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-docs/en/) |
> >
> >
> >
> ---|---|
> > Translated strings |  [
> > 29,515
> > ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> > docs/en/?q=state:>=translated) |  [
> > 100%
> > ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> > docs/en/?q=state:>=translated)
> > Untranslated strings   |  [ 0
> >
> > ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> > docs/en/?q=state:empty)|  [
> > 0%
> > ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> > docs/en/?q=state:empty)
> > Unfinished strings |  [ 0
> >
> > ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> > docs/en/?q=state: > 0%
> > ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> > docs/en/?q=state: > Strings marked for edit|  [ 0
> >
> > ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> > docs/en/?q=state:needs-editing)|  [
> > 0%
> > ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> > docs/en/?q=state:needs-editing)
> >
> >
> > [View](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/en/)
> >
> >
> > [Weblate, the libre continuous localization system.](
> https://weblate.org/)
> >
> > Generated on July 28, 2022, 11:53 a.m..
> >
> > ___
> > Emc-developers mailing list
> > Emc-developers@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/emc-developers
> >
>
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>


-- 
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.

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] /usr/share/doc has many .ini files but .ini files are not documentation

[andy pugh]

On Thu, 28 Jul 2022 at 08:25, Alec Ari via Emc-developers
 wrote:
>
> I have a LinuxCNC ebuild now for Gentoo but there's a problem. All of the 
> config files are missing (i.e. sim axis) so these need to be forced to be 
> installed in the ebuild. Gentoo doesn't like it and there's going to be a lot 
> of QA notices by the time the ebuild is finished because documentation is 
> supposed to be in the doc folder, not config files. Why did you guys decide 
> to use /usr/share/doc/linuxcnc to store things like axis.ini if axis.ini is 
> NOT documentation? /etc/linuxcnc or /etc/linuxcnc/configs would be a perfect 
> spot to store these instead.

Looking about the filesystem, this seems to be normal, many other
packages in /usr/doc have an "examples" folder containing samples. (m4
as one example)

Also the kernel headers seem to be in there too, also not documentation.

So, it seems that an "examples" folder is common, and the LinuxCNC
configs are in "examples"

-- 
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-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

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

[Hans Unzner]

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
> Weblate](https://hosted.weblate.org) /
> [LinuxCNC](https://hosted.weblate.org/projects/linuxcnc/) / [LinuxCNC
> Documentation](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/)
> /
> [English](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/en/)
>
> ## Source string
>
> 'M0' - pause a running program temporarily. LinuxCNC remains in the Auto
> Mode
> so MDI and other manual actions are not enabled. Pressing the resume button
> will restart the program at the following line.
>
> ## Source string description
>
> type: Plain text
>
> ## Comment
>
> I am unhappy with the term "restart". That would imply that something
> would be
> "re"-executed, which is not the case, and variables are not affected,
> either.
> I would prefer "the execution of that program continues in the following
> line."
>
> [Edit this string](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> docs/en/?checksum=acfba46ddc59075d#comments
> 
> )
>
> ## Source string location
>
> [src/gcode/m-code.adoc:47](
> https://github.com/LinuxCNC/linuxcnc/blob/master/docs/src/gcode/m-code.adoc?plain=1#L47
> )
>
> ##  Translation Info
>
> All strings|  [
> 29,515
> ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-docs/en/) |
>
>
> ---|---|
> Translated strings |  [
> 29,515
> ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> docs/en/?q=state:>=translated) |  [
> 100%
> ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> docs/en/?q=state:>=translated)
> Untranslated strings   |  [ 0
>
> ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> docs/en/?q=state:empty)|  [
> 0%
> ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> docs/en/?q=state:empty)
> Unfinished strings |  [ 0
>
> ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> docs/en/?q=state: 0%
> ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> docs/en/?q=state: Strings marked for edit|  [ 0
>
> ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> docs/en/?q=state:needs-editing)|  [
> 0%
> ](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
> docs/en/?q=state:needs-editing)
>
>
> [View](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/en/)
>
>
> [Weblate, the libre continuous localization system.](https://weblate.org/)
>
> Generated on July 28, 2022, 11:53 a.m..
>
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

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

[Nicklas SB Karlsson]

tor 2022-07-28 klockan 09:53 + skrev 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.weblate.org/projects/linuxcnc/linuxcnc-docs/) /
> [English](
> https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/en/)
> 
> ## Source string
> 
> 'M0' - pause a running program temporarily. LinuxCNC remains in the
> Auto Mode
> so MDI and other manual actions are not enabled. Pressing the resume
> button
> will restart the program at the following line.
> 
> ## Source string description
> 
> type: Plain text
> 
> ## Comment
> 
> I am unhappy with the term "restart". That would imply that something
> would be
> "re"-executed, which is not the case, and variables are not affected,
> either.
> I would prefer "the execution of that program continues in the
> following
> line."

Agree.



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Addition Ethercat Homing Routine/Variable

[Nicklas SB Karlsson]

tis 2022-05-03 klockan 13:09 +0100 skrev andy pugh:
> On Tue, 21 Sept 2021 at 15:35, Daniel Dempsey 
> wrote:
> 
> > Will try to sort out the rest of homing.c this week and hopefully
> > test on
> > the weekend when the shop is quiet.
> 
> This has been sat in my inbox for months awaiting a reply. In the
> meantime, Dewey has introduced a system whereby LinuxCNC can be
> configured to support a custom homing scheme. Have you seen that
> work?
> 
> Here is a sample homing  component:
> https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/homecomp.comp
> The docs for that component:
> http://linuxcnc.org/docs/devel/html/man/man9/homecomp.9.html

Some commands are limited then not homed and guess motion module tell
Linuxcnc this. Looking into my .hal file there is however neither an
input to tell motion it should home nor an output connected somewhere
to Linuxcnc GUI then it is homed. Not sure what is part of the motion
module but could see it is named motmod in my .ini file.

Pretty sure there is a problem in motion module as it always do the
homing by itself running the joint(s) setting the offsets. There is a
bit output pin in motion module indicating if homing but no possibility
to tell motion module it is done by externally and not possible tell
motion module homing is done or in an error. There is most certainly
also a need to tell motion module if home offset is added or not by
device itself then homing is completed successfully.


Reading CANopen document homing procedure. At first device have to be
set to special "Homing mode". There i an input bit to tell device start
or continue homing. There is also three status bits, it is in
particularly possible to tell i homing is: in progress, failed or done.
Device also do add an offset internally so should not be done by motion
module and it should also expect offset is added position to position
then homing is completed succesfully. Might be possible to access
position with or without added home offset but are uncertain. Even
though device could do homing by itself I found it work great use the
homing procedure builtin into Linuxcnc. There is however a problem
index pulse on encoder usually is to short to detect by Linuxcnc.


Nicklas Karlsson



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] /usr/share/doc has many .ini files but .ini files are not documentation

[Jérémie Tarot]

Le jeu. 28 juil. 2022 à 09:25, Alec Ari via Emc-developers <
emc-developers@lists.sourceforge.net> a écrit :

> I have a LinuxCNC ebuild now for Gentoo but there's a problem. All of the
> config files are missing (i.e. sim axis) so these need to be forced to be
> installed in the ebuild. Gentoo doesn't like it and there's going to be a
> lot of QA notices by the time the ebuild is finished because documentation
> is supposed to be in the doc folder, not config files. Why did you guys
> decide to use /usr/share/doc/linuxcnc to store things like axis.ini if
> axis.ini is NOT documentation? /etc/linuxcnc or /etc/linuxcnc/configs would
> be a perfect spot to store these instead.
>


I believe because those are not ment to be used as is but rather are really
example configs.

There's so much thing that can differ in an lcnc config that I actually
hardly see how we could provide a default one out of just arbitrarily
choosing a dumb one.

Would gentooists be happier if it was put in some "lib" directory? Say
/usr/share/lib?

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

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

[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.weblate.org/projects/linuxcnc/linuxcnc-docs/) /
[English](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/en/)

## Source string

'M0' - pause a running program temporarily. LinuxCNC remains in the Auto Mode
so MDI and other manual actions are not enabled. Pressing the resume button
will restart the program at the following line.

## Source string description

type: Plain text

## Comment

I am unhappy with the term "restart". That would imply that something would be
"re"-executed, which is not the case, and variables are not affected, either.
I would prefer "the execution of that program continues in the following
line."

[Edit this string](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-
docs/en/?checksum=acfba46ddc59075d#comments)

## Source string location

[src/gcode/m-code.adoc:47](https://github.com/LinuxCNC/linuxcnc/blob/master/docs/src/gcode/m-code.adoc?plain=1#L47)

##  Translation Info

All strings|  [ 29,515 
](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-docs/en/) |   
---|---|
Translated strings |  [ 29,515 
](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-  
docs/en/?q=state:>=translated) |  [ 100%   
](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-  
docs/en/?q=state:>=translated) 
Untranslated strings   |  [ 0  
](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-  
docs/en/?q=state:empty)|  [ 0% 
](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-  
docs/en/?q=state:empty)
Unfinished strings |  [ 0  
](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-  
docs/en/?q=state:https://hosted.weblate.org/translate/linuxcnc/linuxcnc-  
docs/en/?q=state:https://hosted.weblate.org/translate/linuxcnc/linuxcnc-  
docs/en/?q=state:needs-editing)|  [ 0% 
](https://hosted.weblate.org/translate/linuxcnc/linuxcnc-  
docs/en/?q=state:needs-editing)


[View](https://hosted.weblate.org/projects/linuxcnc/linuxcnc-docs/en/)

  
[Weblate, the libre continuous localization system.](https://weblate.org/)

Generated on July 28, 2022, 11:53 a.m..

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] /usr/share/doc has many .ini files but .ini files are not documentation

[Alec Ari via Emc-developers]

I have a LinuxCNC ebuild now for Gentoo but there's a problem. All of the 
config files are missing (i.e. sim axis) so these need to be forced to be 
installed in the ebuild. Gentoo doesn't like it and there's going to be a lot 
of QA notices by the time the ebuild is finished because documentation is 
supposed to be in the doc folder, not config files. Why did you guys decide to 
use /usr/share/doc/linuxcnc to store things like axis.ini if axis.ini is NOT 
documentation? /etc/linuxcnc or /etc/linuxcnc/configs would be a perfect spot 
to store these instead.

Alec


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers