Carolyn: I was thrown/hurt/confused recently when my boyfriend of two years told me hes never really been in love and isnt sure what its supposed to feel like. He then tried to exempt me, but initially he said it as a blanket response to my asking why he never says, I love you. He has said it, but always when Ive said it first. Were 31 and 32.
I didnt know how to respond. I didnt want to make him feel bad since he was clearly emotional when he told me, so I just comforted him. I guess Im the first girlfriend hes talked to about this.
Were actually pretty good otherwise and Im not looking for a ring. But Im also not very good at gauging when its time to admit this is not OK, and it hurts to think about breaking up since I do love him. Any advice?
CONFUSED AND SAD
Boom. No wonder you both ran for cover.
As a final response to his confession, though, I dont recommend the running or the cover.
Thats because the only good outcome for both of you is to get on the right course, be it together tightly, together loosely or heading your separate ways. And the best way to find that right course is to dig out what your boyfriend was trying to say before he lost his nerve.
Even if hes not entirely sure, your willingness to raise this topic without flinching will remove for him the Im afraid to hurt her feelings obstacle, the one that keeps so many couples from expressing their true feelings, the one that keeps relationships going well past their expiration dates.
You know youre stuck at pretty good, or you wouldnt have pressed him on the I love you thing. So, walk toward what scares you and see whether your boyfriend needs a confidant or an out.
Two caveats: 1) His confession could be more manipulation than honesty. I dont think anyone has to strain to imagine a tortured-looking character saying in a soft voice, eyes on the horizon, I dont think Ive ever loved before. Im not sure what it feels like.
2) Even if its bona fide, its not the most promising truth ever shared.
Email tellme@washpost.com. Chat online at 10 a.m. Fridays at www.washingtonpost.com.




