From: Joe Corneli <jcorneli@math.utexas.edu>
Subject: Re: Is Emacs becoming Word?
Date: Sat, 26 Mar 2005 05:24:27 -0600 [thread overview]
Message-ID: <E1DF9P1-0002qa-00@lab45.ma.utexas.edu> (raw)
In-Reply-To: <16965.12661.700062.963115@mail.eng.it> (GianUberto.Lauri@eng.it)
>>>>> "JC" == Joe Corneli <jcorneli@math.utexas.edu> writes:
JC> Eg. the first time \pi turns into a greek
JC> symbol,
I disagree with the whole argument except for having some
documentation that tells you how to replace an old behaviour if you
don't like the new.
That IS the whole argument. Anyone who says differently is selling
something.
They use them in their everyday life. TeX has grown and understands
them. It's fair that Emacs handles them the right way and I love the
True One Editor when it does it.
Have cake? Eat it, too.
next prev parent reply other threads:[~2005-03-26 11:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 18:05 Is Emacs becoming Word? Greg Novak
2005-03-25 18:21 ` Joe Corneli
2005-03-25 18:35 ` nfreimann
[not found] ` <mailman.224.1111776025.28103.help-gnu-emacs@gnu.org>
2005-03-25 21:20 ` David Kastrup
2005-03-25 21:30 ` Joe Corneli
2005-03-26 12:44 ` Eli Zaretskii
[not found] ` <mailman.238.1111787876.28103.help-gnu-emacs@gnu.org>
2005-03-25 22:29 ` David Kastrup
2005-03-25 22:58 ` Joe Corneli
2005-03-26 9:55 ` Gian Uberto Lauri
2005-03-26 11:24 ` Joe Corneli [this message]
[not found] ` <mailman.260.1111832868.28103.help-gnu-emacs@gnu.org>
2005-03-26 11:24 ` David Kastrup
2005-03-26 17:42 ` Bad iso-2022-jp encoding (was: Is Emacs becoming Word?) Reiner Steib
[not found] ` <mailman.245.1111792713.28103.help-gnu-emacs@gnu.org>
2005-03-25 23:37 ` Is Emacs becoming Word? David Kastrup
2005-03-26 1:30 ` Henrik Enberg
2005-03-26 2:06 ` Joe Corneli
2005-03-26 12:37 ` Eli Zaretskii
2005-03-26 12:53 ` Eli Zaretskii
2005-03-26 17:11 ` Joe Corneli
2005-03-26 17:32 ` Eli Zaretskii
2005-03-27 1:08 ` Greg Novak
2005-03-27 4:35 ` Eli Zaretskii
[not found] ` <mailman.300.1111886723.28103.help-gnu-emacs@gnu.org>
2005-03-27 2:02 ` David Kastrup
2005-03-27 10:05 ` Steinar Børmer
2005-03-27 17:08 ` Joe Corneli
2005-03-28 0:17 ` Greg Novak
2005-03-28 0:54 ` Joe Corneli
[not found] ` <mailman.370.1111972552.28103.help-gnu-emacs@gnu.org>
2005-03-28 2:13 ` Thomas A. Horsley
2005-03-28 3:13 ` Henrik Enberg
2005-03-28 4:39 ` Joe Corneli
2005-03-31 20:52 ` Greg Novak
2005-03-31 21:26 ` Joe Corneli
[not found] ` <mailman.808.1112304527.28103.help-gnu-emacs@gnu.org>
2005-04-01 0:35 ` Thien-Thi Nguyen
[not found] ` <mailman.272.1111843857.28103.help-gnu-emacs@gnu.org>
2005-03-26 16:45 ` Thomas A. Horsley
[not found] <mailman.223.1111775070.28103.help-gnu-emacs@gnu.org>
2005-03-25 21:37 ` David Kastrup
2005-03-25 23:30 ` Jochen Küpper
2005-03-26 7:15 ` Greg Novak
2005-03-26 11:43 ` Eli Zaretskii
2005-03-26 12:04 ` Peter Dyballa
[not found] ` <mailman.257.1111822540.28103.help-gnu-emacs@gnu.org>
2005-03-26 11:08 ` Chong Yidong
2005-03-26 11:14 ` David Kastrup
2005-03-28 10:50 ` Olive
2005-03-28 21:04 ` Miles Bader
2005-03-28 22:52 ` David Kastrup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1DF9P1-0002qa-00@lab45.ma.utexas.edu \
--to=jcorneli@math.utexas.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).