Mercurial > emacs
comparison lisp/calc/README @ 77465:1154f082efd9
Update maintainer's address.
author | Jay Belanger <jay.p.belanger@gmail.com> |
---|---|
date | Mon, 23 Apr 2007 21:30:42 +0000 |
parents | dc23aaa67696 |
children | 25780bd5f0e7 |
comparison
equal
deleted
inserted
replaced
77464:e62817ef9d31 | 77465:1154f082efd9 |
---|---|
15 2698 Orchard Parkway | 15 2698 Orchard Parkway |
16 San Jose CA 95134 | 16 San Jose CA 95134 |
17 daveg@synaptics.com, uunet!synaptx!daveg | 17 daveg@synaptics.com, uunet!synaptx!daveg |
18 | 18 |
19 Currently maintained by: | 19 Currently maintained by: |
20 Jay Belanger <belanger@truman.edu> | 20 Jay Belanger <jay.p.belanger@gmail.com> |
21 | 21 |
22 From the introduction to the manual: | 22 From the introduction to the manual: |
23 | 23 |
24 "Calc" is an advanced calculator and mathematical tool that runs as | 24 "Calc" is an advanced calculator and mathematical tool that runs as |
25 part of the GNU Emacs environment. Very roughly based on the HP-28/48 | 25 part of the GNU Emacs environment. Very roughly based on the HP-28/48 |
57 | 57 |
58 | 58 |
59 Calc is written entirely in Emacs Lisp, for maximum portability. | 59 Calc is written entirely in Emacs Lisp, for maximum portability. |
60 | 60 |
61 I am anxious to hear about your experiences using Calc. Send mail to | 61 I am anxious to hear about your experiences using Calc. Send mail to |
62 "belanger@truman.edu". A bug report is most useful if you include the | 62 "jay.p.belanger@gmail.com". A bug report is most useful if you include the |
63 exact input and output that occurred, any modes in effect (such as the | 63 exact input and output that occurred, any modes in effect (such as the |
64 current precision), and so on. If you find Calc is difficult to operate | 64 current precision), and so on. If you find Calc is difficult to operate |
65 in any way, or if you have other suggestions, don't hesitate to let me | 65 in any way, or if you have other suggestions, don't hesitate to let me |
66 know. If you find errors (including simple typos) in the manual, let | 66 know. If you find errors (including simple typos) in the manual, let |
67 me know. Even if you find no bugs at all I would love to hear your | 67 me know. Even if you find no bugs at all I would love to hear your |