On 3/30/2017 12:35 PM, The Tick wrote:
Goodness! All I wanted was to have a comment contain a copyright character. Thanks to the people who were kind enough to take the time to respond to my questions. Now my commit messages are no longer a big blob of text, my .vimrc is modified, I've gotten fossil to stop complaining about my file, and I've learned some more about the intricacies of language support.
This list is one of the good ones, in my experience at least. You may not expect the thread you get, but usually you learn something about some fragment of reality you didn't expect to come up. And actual trolling is quite rare.
I never meant to start another editor war -- I thought that was over when the vi vs. emacs debate finally died years ago.
I didn't see a war here, just a bunch of people happy with the tools they use. Somehow I don't expect that to change soon.
I started using vi back when it was still named "vi" on early BSD systems, I'm happy to see it live on. I've used a commercial emacs inspired editor on the PC since DOS 3.1 (Lugaru Epsilon, and yes it is still supported by the same people). I've used DEC's TECO on a PDP-11, and ed on System III. (And punched cards and tape too, but I'm not that old, really!) I've survived IDEs too, and generally avoid them in favor of one or the other editor when I can. I may be unusual in not being willing to enlist in the editor wars. But I've found being willing to learn to use the tool that gets the job done is more likely to get the bills paid....
Now its been suggested that I not only change my editor, but my keyboard, my programming language, my OS, and even to buy a new computer from a different manufacturer. While I suppose that might move the world closer to perfection, but I've been around long enough to know that will never happen.
Only in jest.... mixed with at least a little of platform bragging where some platforms make it easier to get things right.
The large part of the world stuck with MS products can and should exert some pressure to get better compliance from MS with many standards, not just Unicode. They change at glacial speeds, but they do change. A good first step would be for them to develop and support a "proper" Unicode Locale and code page for their console window. Doing that right likely means following the examples and lessons learned from the Linux community which has been blazing that trail and found (and escaped) most of the dead ends. I think it has become clear that Unicode is here to stay, and UTF-8 is the best representation of it both at rest in files and on the wire in protocols.
-- Ross Berteig [email protected] Cheshire Engineering Corp. http://www.CheshireEng.com/ +1 626 303 1602 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
