persistance in zcalc funct defs

persistance in zcalc funct defs

[jdh]

 Example I am doing some trigonometry calcuations and am more familiar with using degrees for angles, rather than radians.

Today I learned how do define zcalc functions to ease this


In zcalc I did the below (The constants are for 360/(2*pi) and it's inverse)

..> function dtor $1 *  0.0174533
..> function rtod $1 * 57.2958



When I shut down and reboot on the morrow, I dought that these will persist.

Do I need to, or can I put these functions in a zcalc read/init file ? This syntax will probably not work in the zsh startup files.

What is the recommended way to get functions for zcalc loaded automatically.


Regards

Re: persistance in zcalc funct defs

[Peter Stephenson]

On Thu, 03 May 2018 03:38:01 -0700
"jdh" <dhenman@gmail.com> wrote:
> In zcalc I did the below (The constants are for 360/(2*pi) and it's
> inverse)
> 
> ..> function dtor $1 *  0.0174533
> ..> function rtod $1 * 57.2958  
> 
> 
> 
> When I shut down and reboot on the morrow, I dought that these will
> persist.
> 
> Do I need to, or can I put these functions in a zcalc read/init
> file ? This syntax will probably not work in the zsh startup files.

Just put the following in your .zshrc:


autoload -Uz zmathfuncdef
zmathfuncdef dtor '$1 *  0.0174533'
zmathfuncdef rtod '$1 * 57.2958'


See the zshcontrib manaul.

pws

Re: persistance in zcalc funct defs

[Ray Andrews]

On 03/05/18 04:18 AM, Peter Stephenson wrote:
> On Thu, 03 May 2018 03:38:01 -0700
> "jdh" <dhenman@gmail.com> wrote:
>> In zcalc I did the below (The constants are for 360/(2*pi) and it's
>> inverse)
>>
>> ..> function dtor $1 *  0.0174533
>> ..> function rtod $1 * 57.2958
>>
What an interesting coincidence, I was doing some trig just last night, 
and the conversion from degrees to radians was a minor bother, but a 
bother just the same.  Could we have the choice?  It would seem to be a 
very simple thing to add: "setopt ZCALC_DEGREES" "setopt ZCALC_RADIANS" 
?? ... and of course the internal math would be trivial, but faster and 
more accurate than belaboring it in one's code.  20 minutes work (he 
said, with his laughable naivety ;-)