--part1_8d.7786559.284bec1b_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Marcia, this is the order in which I received Rick's posts.
(1) Rick sends Bible passage
(2) I reply (commenting on Bible pasage)
> Heads up! It doesn't say that they didn't see him. It says that they
> > didn't
> > know (recognize) him. Read the rest of the passage (and reread the
> > part
> > you've quoted).
>
(3) Rick replies
> > Sorry Pat, I see your point now. A body was seen but not one
> > recognized as Jesus. I wrote "Jesus was there but not seen." It sort
> > of boils down to whether Jesus was "seen" if he was viewed but not
> > recognized.
>
If the question is what the passage says, it definitely does not, as Rick
originally claimed, say that Christ was invisible to the disciples whom he
met on the road to Emmaus. As we all agree on that, I don't understand what
else you want to know, or why it matters whether you and I received his posts
in the same order or received the same posts. If this is a forum on whether
it was "nice" of me to correct Rick--who isn't exactly enthusiastic about
being corrected--that's an etiquette issue rather than an Eliot issue, and
I'll answer in this way.
99.9% of the time, I don't correct Rick's errors and I just let him go on and
on and on. This isn't especially because I'm "nice," but more because saying
anything is an exercise in futility that can only lead to the now-familiar
argument from Rick about how even when he's wrong he's really right. As I
said, that's his problem, his vanity, machismo, power-tripping or
insecurities. Whatever it is, I usually do honor the axiom that one gives a
person who behaves this way a wide berth, and if the behavior seems
annoying, one tolerates it as a low level annoyance.
So how come this time I didn't ignore him? I don't know. How come you told
him, when he was advising us to read Lamb's Tales from Shakespeare, that this
wasn't a substitute for reading Shakespeare? How come somebody else, or maybe
it was you again, told him that the url he found for a Mantegna painting was
obviously the wrong Mantegna painting? Sometimes the annoyance barometer
shoots through the roof, and one doesn't always know why. I have a few ideas
on what might have been especially annoying lately. But if you really need to
know, shouldn't we continue this discussion off list? It doesn't have much to
do with Eliot.
pat
--part1_8d.7786559.284bec1b_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
<HTML><FONT FACE=arial,helvetica><FONT SIZE=3 FAMILY="SANSSERIF" FACE="Arial Narrow" LANG="0"><B>Marcia, this is the order in which I received Rick's posts.
<BR>
<BR></FONT><FONT COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></B>
<BR>(1) Rick sends Bible passage
<BR>
<BR>(2) I reply (commenting on Bible pasage)
<BR>
<BR>> Heads up! It doesn't say that they didn't see him. It says that they</FONT><FONT COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR></FONT><FONT COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0"><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">> didn't
<BR>> know (recognize) him. Read the rest of the passage (and reread the
<BR>> part
<BR>> you've quoted).
<BR></FONT><FONT COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">(3) Rick replies
<BR></FONT><FONT COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR></FONT><FONT COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0"><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">> Sorry Pat, I see your point now. A body was seen but not one
<BR>> recognized as Jesus. I wrote "Jesus was there but not seen." It sort
<BR>> of boils down to whether Jesus was "seen" if he was viewed but not
<BR>> recognized.
<BR></FONT><FONT COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial Narrow" LANG="0"><B>
<BR>If the question is what the passage says, it definitely does not, as Rick
<BR>originally claimed, say that Christ was invisible to the disciples whom he
<BR>met on the road to Emmaus. As we all agree on that, I don't understand what
<BR>else you want to know, or why it matters whether you and I received his posts
<BR>in the same order or received the same posts. If this is a forum on whether
<BR>it was "nice" of me to correct Rick--who isn't exactly enthusiastic about
<BR>being corrected--that's an etiquette issue rather than an Eliot issue, and
<BR>I'll answer in this way.
<BR>
<BR>99.9% of the time, I don't correct Rick's errors and I just let him go on and
<BR>on and on. This isn't especially because I'm "nice," but more because saying
<BR>anything is an exercise in futility that can only lead to the now-familiar
<BR>argument from Rick about how even when he's wrong he's really right. As I
<BR>said, that's his problem, his vanity, machismo, power-tripping or
<BR>insecurities. Whatever it is, I usually do honor the axiom that one gives a
<BR>person who behaves this way a wide berth, and if the behavior seems
<BR>annoying, one tolerates it as a low level annoyance.
<BR>
<BR>So how come this time I didn't ignore him? I don't know. How come you told
<BR>him, when he was advising us to read Lamb's Tales from Shakespeare, that this
<BR>wasn't a substitute for reading Shakespeare? How come somebody else, or maybe
<BR>it was you again, told him that the url he found for a Mantegna painting was
<BR>obviously the wrong Mantegna painting? Sometimes the annoyance barometer
<BR>shoots through the roof, and one doesn't always know why. I have a few ideas
<BR>on what might have been especially annoying lately. But if you really need to
<BR>know, shouldn't we continue this discussion off list? It doesn't have much to
<BR>do with Eliot.
<BR>
<BR>pat
<BR>
<BR></B></FONT></HTML>
--part1_8d.7786559.284bec1b_boundary--
|
