This seemingly went into the abyss. Admittedly it fell off of my radar too.
Maybe the better question is: who maintains Linuxcnc.org? Perhaps I could ask
them directly…
> On Mar 7, 2025, at 5:20 PM, Greg C wrote:
>
>
> Hopefully this is a simple request...currently we have the following l
On Thu, Apr 3, 2025 at 4:38 PM andy pugh wrote:
> On Thu, 3 Apr 2025 at 17:09, Greg C wrote:
>
> > Maybe the better question is: who maintains Linuxcnc.org?
>
> We all do?
>
> Are you referring to the links here?
> https://github.com/LinuxCNC/wlo/blob/master/documents/index.md
Yes, at least I
Thanks Andy. I appreciate the insight.
I will work out another way to keep this aligned.
Have a good day!
-Greg
On Thu, Apr 3, 2025 at 6:22 PM andy pugh wrote:
> On Thu, 3 Apr 2025 at 22:16, Greg C wrote:
>
> > Where would I change that?
>
> I think those are symlinks on the server:
>
> [pd
On Thu, 3 Apr 2025 at 22:16, Greg C wrote:
> Where would I change that?
I think those are symlinks on the server:
[pdx1-shared-a3-06]$ ls -la
total 60
drwxr-xr-x 17 emcboard pg167418 4096 Nov 4 2023 .
drwxr-xr-x 40 emcboard pg167418 4096 Feb 3 07:52 ..
drwxrwxr-x 2 emcboard pg167418 128 Ap
On Thu, 3 Apr 2025 at 17:09, Greg C wrote:
> Maybe the better question is: who maintains Linuxcnc.org?
We all do?
Are you referring to the links here?
https://github.com/LinuxCNC/wlo/blob/master/documents/index.md
Or to symlinks in the www.linuxcnc.org directory?
--
atp
"A motorcycle is a b
Am 10.04.23 um 02:16 schrieb andy pugh:
On Sat, 8 Apr 2023 at 08:41, Hans Unzner wrote:
You meant "docs/src/man/man3",right?
Ok, I added that and it seemed to work, but then deleting the old files led
to problems. There are 559 instances of the string "hm2_pktuart_read.3hm2"
in the .po fi
On Sat, 8 Apr 2023 at 08:41, Hans Unzner wrote:
> You meant "docs/src/man/man3",right?
Ok, I added that and it seemed to work, but then deleting the old files led
to problems. There are 559 instances of the string "hm2_pktuart_read.3hm2"
in the .po files.
Rather than try to fix that, I reinsta
Am 08.04.23 um 01:36 schrieb Sebastian Kuzminsky:
On 4/7/23 16:49, andy pugh wrote:
I have made some changes to hm2_pktuart and I feel the urge to document
them.
Currently this feature is (barely) documented in groff/troff in the
files:
docs/man/man3/hm2_pktuart_read.3hm2
docs/man/man3/hm2
On 4/7/23 16:49, andy pugh wrote:
I have made some changes to hm2_pktuart and I feel the urge to document
them.
Currently this feature is (barely) documented in groff/troff in the files:
docs/man/man3/hm2_pktuart_read.3hm2
docs/man/man3/hm2_pktuart_send.3hm2
docs/man/man3/hm2_pktuart_setup.3hm2
On Sat, 29 Aug 2020 at 04:44, Rod Webster wrote:
> I'm sure now is not the time to change authoring environments but it likely
> explains the convoluted workflow you've found. Asciidoc to me seems to be a
> very archaic authoring environment.
Asciidoc seems a neat and elegant solution compared t
>On the other hand, do we lose the LateX / texlive dependencies?
I would hope so, texlive is enormous.
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
Its been a while since i've been involved in document production and I was
never heavily involved in this sort of thing. But I believe that best
practice in document authoring was to use XSLT (which uses an XML
structure) see
https://en.wikipedia.org/wiki/XSLT#:~:text=XSLT%20(Extensible%20Styleshee
On Tuesday 31 March 2020 09:22:11 andy pugh wrote:
> On Tue, 31 Mar 2020 at 10:43, Gene Heskett
wrote:
> > Internal to the docs and the installed debs are all dated like this:
> > pi@rpi4:/usr/share/doc/linuxcnc $ ls -l
>
> It might be that you need to explicitly build the docs before building
>
On Tue, 31 Mar 2020 at 10:43, Gene Heskett wrote:
> Internal to the docs and the installed debs are all dated like this:
> pi@rpi4:/usr/share/doc/linuxcnc $ ls -l
It might be that you need to explicitly build the docs before building
the debs.
My 2.9 debs have older docs, like yours.
My 2.8 deb
On Tuesday 31 March 2020 05:01:42 andy pugh wrote:
> On Tue, 31 Mar 2020 at 09:36, Gene Heskett
wrote:
> > I'm running master on all my stuff but haven't played with some of
> > the features because they are not documented.
> > LinuxCNC_Documentation.pdf is still carrying a June 2019 last
> > mo
On Tue, 31 Mar 2020 at 09:36, Gene Heskett wrote:
> I'm running master on all my stuff but haven't played with some of the
> features because they are not documented. LinuxCNC_Documentation.pdf is
> still carrying a June 2019 last modified date
Are you building docs when you build?
Is this a fil
Sam,
Thanks for clearing that up.
John
On 1/17/2012 8:01 AM, sam sokolik wrote:
> I am homing a locking rotary... It evokes the unlock sequence.
>
> sam
>
> On 1/17/2012 7:15 AM, andy pugh wrote:
>> On 17 January 2012 13:12, John Thornton wrote:
>>> A note on the original commit said that hom
I am homing a locking rotary... It evokes the unlock sequence.
sam
On 1/17/2012 7:15 AM, andy pugh wrote:
> On 17 January 2012 13:12, John Thornton wrote:
>> A note on the original commit said that homing didn't know how to unlock
>> and lock... I wonder if it does now?
> I guess that that coul
On 17 January 2012 13:12, John Thornton wrote:
> A note on the original commit said that homing didn't know how to unlock
> and lock... I wonder if it does now?
I guess that that could be handled in HAL?
--
atp
The idea that there is no such thing as objective truth is, quite simply, wrong.
--
A note on the original commit said that homing didn't know how to unlock
and lock... I wonder if it does now?
John
On 1/17/2012 7:03 AM, andy pugh wrote:
> LOCKING_INDEXER appears in
> http://www.linuxcnc.org/docview/2.5/html/config/ini_homing.html
> rather than where I expected, ie
> http://www
Working on that as we speak
John
On 1/17/2012 7:03 AM, andy pugh wrote:
> LOCKING_INDEXER appears in
> http://www.linuxcnc.org/docview/2.5/html/config/ini_homing.html
> rather than where I expected, ie
> http://www.linuxcnc.org/docview/2.5/html/config/ini_config.html
>
> I don't see any mention o
Hi Oscar,
As I think I mentioned before, we are moving away from LyX,
so it would be better if you could wait just a bit and start
with the revised AsciiDoc (.txt) files I'm about to push.
Or, if you can't wait, start with the existing .txt files
instead of the .lyx files.
In either case I
Hi my name is Oscar Chaides, I'm from Mexico, i just come back from the
Digital Machinist Work Shop were i met Jon, Matt and Ray, I'm very
interesting in the translation of the manuals to Spanish, is some body
else working on it? what can i do to get access to the original editable
manuals not
On Mon, Feb 07, 2011 at 08:50:42AM +0300, Pavel Shramov wrote:
> > Still left:
> > * compatible html output names
> For site or you think that local docs need dir_file names too?
The goal of building an html docs package is so that the gcode quickref
gcode.html can link to the actual html manual.
On Sun, Feb 06, 2011 at 08:52:26PM -0600, Jeff Epler wrote:
> I've finally gotten around to taking a look at the latest incarnation of
> the asiidoc project.
>
> To fix:
> * don't use shell find / shell ls -- this is unsafe and inefficient
> * it's unsafe if any (future) doc file has a character
I've finally gotten around to taking a look at the latest incarnation of
the asiidoc project.
To fix:
* don't use shell find / shell ls -- this is unsafe and inefficient
* it's unsafe if any (future) doc file has a character treated specially
by the shell
* use $(wildcard *.txt) instead of $
On Fri, Jan 28, 2011 at 02:57:09PM +0100, Francis TISSERANT wrote:
> Pavel
> I am a French translator. Nice work Pavel. Choosing asciidoc looks good
> to me, John T. has already explored this possibility long ago. The
> process of renaming fichiers_fr.* was created by Jeff to simplify my
> trans
On Fri, Jan 28, 2011 at 07:56:01AM -0600, EBo wrote:
> Just a thought. Maybe there is a way to extract the full TOC in the
> HTML version and link just that to a separate document. I personally
> find a TOC in an HTML file annoying, and breaking it up into little
> bittsy pieces that can o
Pavel
I am a French translator. Nice work Pavel. Choosing asciidoc looks good
to me, John T. has already explored this possibility long ago. The
process of renaming fichiers_fr.* was created by Jeff to simplify my
translation work. I can not thank him enough! Now, pass the French
documentation
Just a thought. Maybe there is a way to extract the full TOC in the
HTML version and link just that to a separate document. I personally
find a TOC in an HTML file annoying, and breaking it up into little
bittsy pieces that can only be viewed via a TOC side menu even more
annoying. That
Pavel,
One advantage of having the manuals in the HTML the same as the PDF
manuals is you can search the whole thing very easy. Another is the PDF
and the HTML are the same layout which makes it easier to find things in
either one. One thing that I don't care for is the TOC in the HTML. In
the
On Thu, Jan 27, 2011 at 06:13:53PM -0800, Alexey Starikovskiy wrote:
> After a quick look over "Getting Started", I've noticed following:
> 1. '{0.5in}' markup still present,
Fixed.
> 2. markup of links is not cleared everywhere: [sub:, [cha:, etc
I won't consider it's a bug - by default ref name
After a quick look over "Getting Started", I've noticed following:
1. '{0.5in}' markup still present,
2. markup of links is not cleared everywhere: [sub:, [cha:, etc
2. Table in 6.5 is broken
Regards,
Alex.
On 01/27/2011 03:50 PM, Pavel Shramov wrote:
> On Fri, Jan 14, 2011 at 06:34:47PM +0300,
On Fri, Jan 14, 2011 at 06:34:47PM +0300, Pavel Shramov wrote:
> In the light of upcoming 2.5 version and new branch I want
> to bring up again question about documentation format.
This is call for bug hunting.
I've done initial conversion of docs to asciidoc and created branch
with new docs [1].
On Fri, Jan 14, 2011 at 06:34:47PM +0300, Pavel Shramov wrote:
> In the light of upcoming 2.5 version and new branch I want
> to bring up again question about documentation format.
After playing a bit more with RST and AsciiDoc and trying to implement
suggestions from #emc-devel i believe that Asci
On Jan 24, 2011, at 2:33 PM, Dave Caroline wrote:
> PDF's take an obscene amount of memory to render so are ok for
> printing but not easy reference, one large PDF would only make matters
> worse there. Anyone using small amount of memory will soon be swapping
> to disk.
>
> Local HTML should be
PDF's take an obscene amount of memory to render so are ok for
printing but not easy reference, one large PDF would only make matters
worse there. Anyone using small amount of memory will soon be swapping
to disk.
Local HTML should be very easy to setup as part of the install,
current docs have so
First I want to thank Pavel for all his research and effort on this
subject as well as others.
The installed PDF documents:
They do not contain all the man page information automagically.
The G Code quick reference is only useful if your machine has an
internet connection.
IMHO me
To move the discussion forward I think it would be helpful to steer by
requirements for a document format, and then decide wether its worthwhile to
change.
I am by no means an expert on these formats and tools. However, I would view
the following as important (in no particular order or rating):
Jeff Epler wrote:
> Seb, this will require you to remove some slaves from buildbot, such as
> dapper-x86-trunk-realtime-deb -- basically, anything that is on dapper
> or older, builds trunk, and uses --enable-build-documentation.
That's the only affected buildslave, i've removed it from the buildb
Hello Ben
I always carefully read system requirements on the games boxes before
buying. It's useful information.
The rest of your comments would be really useful if included in the
documentation/wiki. I have not run any of the software you have
described (except ssh) so I didn't know the syst
Dear Darren,
"minimum requirements" is the sort of thing you'd put on a video game box.
EMC comes with various GUI's that each have different requirements. Axis
wants a system with OpenGL hardware acceleration but it can use software
rendering too; mini is a bit more frugal; and keystick requir
Darren,
That is a great idea. I've added system requirements to the Getting Started
Guide.
When you complete this please share how you made it all work.
Thanks for the feedback on the Getting Started Guide.
John
On 31 Oct 2008 at 21:23, Darren Conway wrote:
> Hello
>
> I suggest that the m
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Hardware_Requirements
Regards,
Alex
- Original Message -
From: "Darren Conway" <[EMAIL PROTECTED]>
To: "EMC developers"
Sent: Friday, October 31, 2008 10:23 AM
Subject: [Emc-developers] Documentation Question and Suggestion :
Minimumsystem re
44 matches
Mail list logo
