Re: RE: Magicka 0.10?
By: apam to Dumas Walker on Mon May 21 2018 07:52:50

Is there any way to set the git and/or compile so that it does NOT
erase the magimail config file EVERY time one upgrades to the next
patch version? I had copied it to another directory (but not one
that was nut under MagickaBBS) so it got both copies this time.
Here on my pi, magimail won't find it unless it is in the magimail
bin directory. It would be nice if it was in the directory with all
of the other INI files as that one (apparently) does not get erased
every time.

What I do is have it in an ftn folder under the MagickaBBS. Magimail only
looks in the current working directory for the magimail.prefs, so what I
do is invoke magimail like this

cd MagickaBBS/ftn

../utils/magimail/bin/magimail scan

I could tweak the makefile to not erase the bin folder but the individual binaries instead when clean is run, but for the short term try the above
method :)

Andrew

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

Hello apam

So tell me what is added new to 0.11 ?

I just updated today and missed what you added....


Havok

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: After Hours|The Villages,FL|afterhours-bbs.com (21:4/119)

Hi

So tell me what is added new to 0.11 ?

0.11 is the new "work in progress" branch, all I've added so far is the
message flagging function :)

Andrew

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

What I do is have it in an ftn folder under the MagickaBBS. Magimail
only looks in the current working directory for the magimail.prefs, so what I do is invoke magimail like this

That suggestion should fix it. thanks!


... 2 + 2 = 5 for extremely large values of 2.
--- MultiMail
* Origin: Possum Lodge South * capitolcityonline.net:7636 (21:1/175.8)