RW
Ray West
Sat, Jul 31, 2021 4:38 PM
Thanks, I've set the editor to DejaVu Sans Mono and also the windows
command line. How do I set the openscad console font, and it's size?
On 31/07/2021 16:30, Torsten Paul wrote:
On 31.07.21 17:15, Ray West wrote:
A courier font is probably better for distinguishing characters, but
I expect there are better ones now - Verdana seems pretty good.
I'm using "Iosevka Nerd Font" as it has extra combined glyphs for
things like >= and runs quite compact.
For a long selection of such fonts, including version extended with
those special glyphs, see:
https://github.com/ryanoasis/nerd-fonts
List of fonts with some example images:
https://www.nerdfonts.com/font-downloads
There should be something for everyone's taste :-). The overview
page also links to the original font versions, in case the hacked
ones are not preferred.
ciao,
Torsten.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
Thanks, I've set the editor to DejaVu Sans Mono and also the windows
command line. How do I set the openscad console font, and it's size?
On 31/07/2021 16:30, Torsten Paul wrote:
> On 31.07.21 17:15, Ray West wrote:
>> A courier font is probably better for distinguishing characters, but
>> I expect there are better ones now - Verdana seems pretty good.
> I'm using "Iosevka Nerd Font" as it has extra combined glyphs for
> things like >= and runs quite compact.
>
> For a long selection of such fonts, including version extended with
> those special glyphs, see:
>
> https://github.com/ryanoasis/nerd-fonts
>
> List of fonts with some example images:
>
> https://www.nerdfonts.com/font-downloads
>
> There should be something for everyone's taste :-). The overview
> page also links to the original font versions, in case the hacked
> ones are not preferred.
>
> ciao,
> Torsten.
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
TP
Torsten Paul
Sat, Jul 31, 2021 4:46 PM
On 31.07.21 18:38, Ray West wrote:
Thanks, I've set the editor to DejaVu Sans Mono and also the
windows command line. How do I set the openscad console font,
and it's size?
That's available in the Dev-Snapshots only. See screenshot.
ciao,
Torsten.
On 31.07.21 18:38, Ray West wrote:
> Thanks, I've set the editor to DejaVu Sans Mono and also the
> windows command line. How do I set the openscad console font,
> and it's size?
That's available in the Dev-Snapshots only. See screenshot.
ciao,
Torsten.
L
larry
Sat, Jul 31, 2021 9:05 PM
On Sat, 2021-07-31 at 14:04 +0100, Ray West wrote:
On 31/07/2021 13:11, nop head wrote:
I don't like typing and I try to avoid repeating anything.
I'm with you in that. A hang over from when punch card operators
entered my code, and variable names restricted to max of 4 chars,
starting with i to n for integers, etc. Fortran IV, g and h, iirc. 8k
core memory, etc.
Boy that brings back memories. My first Fortran program was a brute-
force prime number finder. I wrote it with exactly the same algorithm I
had used on an IBM 6400 Electronic Accounting Machine, which was
programmed with jumper wires in a plugboard. I started it when I left
work one night (5PM), and at 8:30 when I arrived the next morning, the
last prime printed out was 853. Not surprising, since a multiply or
divide took in the order of 300 ms (yes, that's milliseconds).
Anyway I loaded my program into an IBM 360/30, and 853 came up faster
than I could walk the 10 feet to the printer.
I may just try that same algorithm on my Linux box.
BTW, we were fond of referring to punch cards as "short pieces of 80
channel paper tape".
On Sat, 2021-07-31 at 14:04 +0100, Ray West wrote:
> On 31/07/2021 13:11, nop head wrote:
> > I don't like typing and I try to avoid repeating anything.
> I'm with you in that. A hang over from when punch card operators
> entered my code, and variable names restricted to max of 4 chars,
> starting with i to n for integers, etc. Fortran IV, g and h, iirc. 8k
> core memory, etc.
Boy that brings back memories. My first Fortran program was a brute-
force prime number finder. I wrote it with exactly the same algorithm I
had used on an IBM 6400 Electronic Accounting Machine, which was
programmed with jumper wires in a plugboard. I started it when I left
work one night (5PM), and at 8:30 when I arrived the next morning, the
last prime printed out was 853. Not surprising, since a multiply or
divide took in the order of 300 ms (yes, that's milliseconds).
Anyway I loaded my program into an IBM 360/30, and 853 came up faster
than I could walk the 10 feet to the printer.
I may just try that same algorithm on my Linux box.
BTW, we were fond of referring to punch cards as "short pieces of 80
channel paper tape".
M
MichaelAtOz
Sun, Aug 1, 2021 5:44 AM
That is another of those limitations I mentioned that Empathy has.
Terry copied the code from Empathy rather than an email.
I think Empathy treats '*'s as markup or something.
-----Original Message-----
From: Torsten Paul [mailto:Torsten.Paul@gmx.de]
Sent: Sun, 1 Aug 2021 00:40
To: discuss@lists.openscad.org
Subject: [OpenSCAD] Re: How best to apply offset on 2D square?
On 31.07.21 16:10, Terry wrote:
WARNING: Ignoring unknown variable '3l' in file Ray.scad, line 37
WARNING: Ignoring unknown variable '3w' in file Ray.scad, line 37
WARNING: Unable to convert cube(size=[undef, undef, 154.5], ...)
parameter to a number or a vec3 of numbers in file Ray.scad, line 37
That's very likely this line:
translate([0,0, h+cut]) cube([3l,3w,3*h],true);
missing two "*" so instead of calculating 3 * l it's trying to find
the variable "3l". In turn that's then causing those 2 undef of the
3rd warning.
ciao,
Torsten.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
That is another of those limitations I mentioned that Empathy has.
Terry copied the code from Empathy rather than an email.
I think Empathy treats '*'s as markup or something.
> -----Original Message-----
> From: Torsten Paul [mailto:Torsten.Paul@gmx.de]
> Sent: Sun, 1 Aug 2021 00:40
> To: discuss@lists.openscad.org
> Subject: [OpenSCAD] Re: How best to apply offset on 2D square?
>
> On 31.07.21 16:10, Terry wrote:
> > WARNING: Ignoring unknown variable '3l' in file Ray.scad, line 37
> > WARNING: Ignoring unknown variable '3w' in file Ray.scad, line 37
> > WARNING: Unable to convert cube(size=[undef, undef, 154.5], ...)
> > parameter to a number or a vec3 of numbers in file Ray.scad, line 37
>
> That's very likely this line:
>
> > translate([0,0, h+cut]) cube([3*l,3*w,3*h],true);
>
> missing two "*" so instead of calculating 3 * l it's trying to find
> the variable "3l". In turn that's then causing those 2 undef of the
> 3rd warning.
>
> ciao,
> Torsten.
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
--
This email has been checked for viruses by AVG.
https://www.avg.com
T
Terry
Sun, Aug 1, 2021 11:56 AM
I'd have sworn I copied the code directly from Ray's post, Michael, but
I can't think of any other explanation!
I use Empathy only for the reason I mentioned, to see all posts in
logical sequence, including my own. And as you know, in my 3rd July post
to the thread stated by Ben, 'New and a question', I reported that very
flaw:
"Empathy clearly doesn't like the asterisk symbol. Sometimes treating it
as a signal to switch on italics.
Who knows what other symbols are wrongly handled?"
But the fact remains that I just tried copying it again from Ray's post,
and now the line
translate([0,0, h+cut]) cube([3l,3w,3*h],true);
is clearly fine, so no warnings.
Terry
====================
On Sun, 1 Aug 2021 15:44:52 +1000, you wrote:
That is another of those limitations I mentioned that Empathy has.
Terry copied the code from Empathy rather than an email.
I think Empathy treats '*'s as markup or something.
-----Original Message-----
From: Torsten Paul [mailto:Torsten.Paul@gmx.de]
Sent: Sun, 1 Aug 2021 00:40
To: discuss@lists.openscad.org
Subject: [OpenSCAD] Re: How best to apply offset on 2D square?
On 31.07.21 16:10, Terry wrote:
WARNING: Ignoring unknown variable '3l' in file Ray.scad, line 37
WARNING: Ignoring unknown variable '3w' in file Ray.scad, line 37
WARNING: Unable to convert cube(size=[undef, undef, 154.5], ...)
parameter to a number or a vec3 of numbers in file Ray.scad, line 37
That's very likely this line:
translate([0,0, h+cut]) cube([3l,3w,3*h],true);
missing two "*" so instead of calculating 3 * l it's trying to find
the variable "3l". In turn that's then causing those 2 undef of the
3rd warning.
ciao,
Torsten.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
I'd have sworn I copied the code directly from Ray's post, Michael, but
I can't think of any other explanation!
I use Empathy only for the reason I mentioned, to see all posts in
logical sequence, including my own. And as you know, in my 3rd July post
to the thread stated by Ben, 'New and a question', I reported that very
flaw:
"Empathy clearly doesn't like the asterisk symbol. Sometimes treating it
as a signal to switch on italics.
Who knows what other symbols are wrongly handled?"
But the fact remains that I just tried copying it again from Ray's post,
and now the line
translate([0,0, h+cut]) cube([3*l,3*w,3*h],true);
is clearly fine, so no warnings.
Terry
====================
On Sun, 1 Aug 2021 15:44:52 +1000, you wrote:
>That is another of those limitations I mentioned that Empathy has.
>
>Terry copied the code from Empathy rather than an email.
>I think Empathy treats '*'s as markup or something.
>
>> -----Original Message-----
>> From: Torsten Paul [mailto:Torsten.Paul@gmx.de]
>> Sent: Sun, 1 Aug 2021 00:40
>> To: discuss@lists.openscad.org
>> Subject: [OpenSCAD] Re: How best to apply offset on 2D square?
>>
>> On 31.07.21 16:10, Terry wrote:
>> > WARNING: Ignoring unknown variable '3l' in file Ray.scad, line 37
>> > WARNING: Ignoring unknown variable '3w' in file Ray.scad, line 37
>> > WARNING: Unable to convert cube(size=[undef, undef, 154.5], ...)
>> > parameter to a number or a vec3 of numbers in file Ray.scad, line 37
>>
>> That's very likely this line:
>>
>> > translate([0,0, h+cut]) cube([3*l,3*w,3*h],true);
>>
>> missing two "*" so instead of calculating 3 * l it's trying to find
>> the variable "3l". In turn that's then causing those 2 undef of the
>> 3rd warning.
>>
>> ciao,
>> Torsten.
>> _______________________________________________
>> OpenSCAD mailing list
>> To unsubscribe send an email to discuss-leave@lists.openscad.org
