X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <20220616112936.17897.qmail@stuge.se>
Date: Thu, 16 Jun 2022 11:29:36 +0000
From: "Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user ailing list <geda-user AT delorie DOT com>
Subject: Re: [geda-user] pcb- gcode export
References: <c7bdfc66-52cb-3fd6-5a7f-831b9af70901 AT epilitimus DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c7bdfc66-52cb-3fd6-5a7f-831b9af70901@epilitimus.com>
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Glenn (glimrick AT epilitimus DOT com) [via geda-user AT delorie DOT com] wrote:
> I would like to have some custom postfix code in each gcode file
> (Moves to a safe location essentially) but the prefix and postfix
> code are hard coded into the binary.
> 
> So unless I am missing something my options are:
> 1. hand edit each gcode file (already getting old)
> 2. Hack the source code (hid/gcode/gcode.c) to make it what I want -
> which is what I am probably going to do
> 3. Beg for a feature.

4. Write a post-processor to modify prefix/postfix in gcode files.

This could possibly be as simple as a single sed command and would
relieve the need to maintain modified source code. If you want I'm
happy to propose a solution, just send me before and after gcode files.


Kind regards

//Peter