discuss@lists.openscad.org

OpenSCAD general discussion Mailing-list

View all threads

Latest snapshot echo format has changed

NH
nop head
Fri, Oct 2, 2020 9:06 AM

The latest snapshot no longer starts the echo lines with ECHO: when echoed
to the command line console. It does still include them in the GUI and in
.echo files. Is this intentional as it breaks some of my scripts?

The latest snapshot no longer starts the echo lines with ECHO: when echoed to the command line console. It does still include them in the GUI and in .echo files. Is this intentional as it breaks some of my scripts?
TP
Torsten Paul
Fri, Oct 2, 2020 1:00 PM

On 02.10.20 11:06, nop head wrote:

The latest snapshot no longer starts the echo lines with ECHO: when
echoed to the command line console. It does still include them in the
GUI and in .echo files. Is this intentional as it breaks some of my
scripts?

No, it's not intentional. So that only affects the standard output
when generating for example STLs via command line?

ciao,
Torsten.

On 02.10.20 11:06, nop head wrote: > The latest snapshot no longer starts the echo lines with ECHO: when > echoed to the command line console. It does still include them in the > GUI and in .echo files. Is this intentional as it breaks some of my > scripts? No, it's not intentional. So that only affects the standard output when generating for example STLs via command line? ciao, Torsten.
NH
nop head
Fri, Oct 2, 2020 1:11 PM

Yes when generating anything with the command line that isn't a .echo file.
Any echos go to the console and I rely on the ECHO: prefix to separate them
from the rest of the console messages, which I see has increased.

On Fri, 2 Oct 2020 at 14:01, Torsten Paul Torsten.Paul@gmx.de wrote:

On 02.10.20 11:06, nop head wrote:

The latest snapshot no longer starts the echo lines with ECHO: when
echoed to the command line console. It does still include them in the
GUI and in .echo files. Is this intentional as it breaks some of my
scripts?

No, it's not intentional. So that only affects the standard output
when generating for example STLs via command line?

ciao,
Torsten.


OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

Yes when generating anything with the command line that isn't a .echo file. Any echos go to the console and I rely on the ECHO: prefix to separate them from the rest of the console messages, which I see has increased. On Fri, 2 Oct 2020 at 14:01, Torsten Paul <Torsten.Paul@gmx.de> wrote: > On 02.10.20 11:06, nop head wrote: > > The latest snapshot no longer starts the echo lines with ECHO: when > > echoed to the command line console. It does still include them in the > > GUI and in .echo files. Is this intentional as it breaks some of my > > scripts? > > No, it's not intentional. So that only affects the standard output > when generating for example STLs via command line? > > ciao, > Torsten. > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >
T
Troberg
Sat, Oct 3, 2020 11:49 AM

That would break a lot of my post-processing as well.

--
Sent from: http://forum.openscad.org/

That would break a lot of my post-processing as well. -- Sent from: http://forum.openscad.org/
TP
Torsten Paul
Sat, Oct 3, 2020 7:48 PM

On 03.10.20 13:49, Troberg wrote:

That would break a lot of my post-processing as well.

Should be fixed now via
https://github.com/openscad/openscad/pull/3453

ciao,
Torsten.

On 03.10.20 13:49, Troberg wrote: > That would break a lot of my post-processing as well. Should be fixed now via https://github.com/openscad/openscad/pull/3453 ciao, Torsten.
NH
nop head
Sat, Oct 3, 2020 8:37 PM

Yes it works again for me now, thanks.

On Sat, 3 Oct 2020 at 20:49, Torsten Paul Torsten.Paul@gmx.de wrote:

On 03.10.20 13:49, Troberg wrote:

That would break a lot of my post-processing as well.

Yes it works again for me now, thanks. On Sat, 3 Oct 2020 at 20:49, Torsten Paul <Torsten.Paul@gmx.de> wrote: > On 03.10.20 13:49, Troberg wrote: > > That would break a lot of my post-processing as well. > > Should be fixed now via > https://github.com/openscad/openscad/pull/3453 > > ciao, > Torsten. > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >
T
Troberg
Sun, Oct 4, 2020 6:09 AM

tp3 wrote

On 03.10.20 13:49, Troberg wrote:

That would break a lot of my post-processing as well.

Should be fixed now via
https://github.com/openscad/openscad/pull/3453

ciao,
Torsten.

My hero!

--
Sent from: http://forum.openscad.org/

tp3 wrote > On 03.10.20 13:49, Troberg wrote: >> That would break a lot of my post-processing as well. > > Should be fixed now via > https://github.com/openscad/openscad/pull/3453 > > ciao, > Torsten. My hero! -- Sent from: http://forum.openscad.org/
WF
William F. Adams
Sun, Oct 4, 2020 3:44 PM

Could we please preserve the code which allowed writing out only what the user has added and wire it up to an option to write out that text via a menu in the interface?
I would find that very useful.
William

-----Original Message-----
From: Troberg troberg.anders@gmail.com
To: discuss@lists.openscad.org
Sent: Sun, Oct 4, 2020 2:09 am
Subject: Re: [OpenSCAD] Latest snapshot echo format has changed

tp3 wrote

On 03.10.20 13:49, Troberg wrote:

That would break a lot of my post-processing as well.

Should be fixed now via
https://github.com/openscad/openscad/pull/3453

ciao,
  Torsten.

Could we please preserve the code which allowed writing out only what the user has added and wire it up to an option to write out that text via a menu in the interface? I would find that very useful. William -----Original Message----- From: Troberg <troberg.anders@gmail.com> To: discuss@lists.openscad.org Sent: Sun, Oct 4, 2020 2:09 am Subject: Re: [OpenSCAD] Latest snapshot echo format has changed tp3 wrote > On 03.10.20 13:49, Troberg wrote: >> That would break a lot of my post-processing as well. > > Should be fixed now via > https://github.com/openscad/openscad/pull/3453 > > ciao, >  Torsten. My hero! -- Sent from: http://forum.openscad.org/ _______________________________________________ OpenSCAD mailing list Discuss@lists.openscad.org http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
NH
nop head
Sun, Oct 4, 2020 4:13 PM

It wasn't ever that though because strings are enclosed in quotes, it just
missed the ECHO: prefix. And there are lots of other messages now on
stdout, so without the prefix it is hard to pick out the user output.

Geometries in cache: 9

Geometry cache size in bytes: 117536
CGAL Polyhedrons in cache: 0
CGAL cache size in bytes: 0
Total rendering time: 0:00:00.004
Top level object is a 3D object:
Facets:        728

On Sun, 4 Oct 2020 at 16:45, William F. Adams via Discuss <
discuss@lists.openscad.org> wrote:

Could we please preserve the code which allowed writing out only what the
user has added and wire it up to an option to write out that text via a
menu in the interface?

I would find that very useful.

William

-----Original Message-----
From: Troberg troberg.anders@gmail.com
To: discuss@lists.openscad.org
Sent: Sun, Oct 4, 2020 2:09 am
Subject: Re: [OpenSCAD] Latest snapshot echo format has changed

tp3 wrote

On 03.10.20 13:49, Troberg wrote:

That would break a lot of my post-processing as well.

Should be fixed now via
https://github.com/openscad/openscad/pull/3453

ciao,
Torsten.

It wasn't ever that though because strings are enclosed in quotes, it just missed the ECHO: prefix. And there are lots of other messages now on stdout, so without the prefix it is hard to pick out the user output. Geometries in cache: 9 > Geometry cache size in bytes: 117536 > CGAL Polyhedrons in cache: 0 > CGAL cache size in bytes: 0 > Total rendering time: 0:00:00.004 > Top level object is a 3D object: > Facets: 728 On Sun, 4 Oct 2020 at 16:45, William F. Adams via Discuss < discuss@lists.openscad.org> wrote: > Could we please preserve the code which allowed writing out only what the > user has added and wire it up to an option to write out that text via a > menu in the interface? > > I would find that very useful. > > William > > > -----Original Message----- > From: Troberg <troberg.anders@gmail.com> > To: discuss@lists.openscad.org > Sent: Sun, Oct 4, 2020 2:09 am > Subject: Re: [OpenSCAD] Latest snapshot echo format has changed > > tp3 wrote > > On 03.10.20 13:49, Troberg wrote: > >> That would break a lot of my post-processing as well. > > > > Should be fixed now via > > https://github.com/openscad/openscad/pull/3453 > > > > ciao, > > Torsten. > > My hero! > > > > -- > Sent from: http://forum.openscad.org/ > > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >
JB
Jordan Brown
Sun, Oct 4, 2020 9:12 PM

On 10/4/2020 8:44 AM, William F. Adams via Discuss wrote:

Could we please preserve the code which allowed writing out only what
the user has added and wire it up to an option to write out that text
via a menu in the interface?

I would find that very useful.

I think that would be one of the goals of a "printf" feature.

On 10/4/2020 9:13 AM, nop head wrote:

It wasn't ever that though because strings are enclosed in quotes, it
just missed the ECHO: prefix. And there are lots of other messages now
on stdout, so without the prefix it is hard to pick out the user output. 

If the program has full control over its output, it can emit its own prefix.

On 10/4/2020 8:44 AM, William F. Adams via Discuss wrote: > Could we please preserve the code which allowed writing out only what > the user has added and wire it up to an option to write out that text > via a menu in the interface? > > I would find that very useful. I think that would be one of the goals of a "printf" feature. On 10/4/2020 9:13 AM, nop head wrote: > It wasn't ever that though because strings are enclosed in quotes, it > just missed the ECHO: prefix. And there are lots of other messages now > on stdout, so without the prefix it is hard to pick out the user output.  If the program has full control over its output, it can emit its own prefix.