From: Pavel.Janik@inet.cz (Pavel Janík ml.)
Cc: ding@gnus.org
Subject: Re: People with From: <mail@domain.com>
Date: 24 Apr 2000 20:56:13 +0200 [thread overview]
Message-ID: <m3hfcrz5te.fsf@SnowWhite.inet.cz> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Mon, 24 Apr 2000 20:39:15 +0200"
[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Date: Mon, 24 Apr 2000 20:39:15 +0200
Hi,
> Hm. This seems to be a different problem, though.
yes, when you set gnus-extract-address-components to
mail-extract-address-components from mail-extr.el it will correctly display
the sender with
From: <someone@somewhere.com>
but it can fail on some correct From headers like yours. There is probably
some bug in regexp there...
> If the From header looks like ``From: <jrl@frob.org>'', Gnus is
> wont to show the empty string as the author name in the Summary
> buffer. I'm not sure what to do about that, but maybe setting the
> variable gnus-extract-address-components is the right way to go.
Yes, it solves my problem. I can customize it to be mail-...
> see my full name in the Summary buffer, but now I have told Gnus to
> display `-> recipient' in the Summary buffer, instead.
If I leave gnus-extract-address-components untouched I see your name complete,
but mail-extract-... is buggy for it.
> Strange. Is anybody else seeing a truncated From address for my
> messages?
Maybe some with gnus-extract-... variable customized to mail-... :-)) But it
is NOT your fault. It is Emacs's mail-extr fault.
> Maybe it only happens for Latin-X users with X not equal to 1? (My
> name has a Latin-1 character in it.) Pavel, could you try sending a
> message with the appropriate Latin-2 characters in your name?
OK. This message should contain it :-) If I send a test message to myself
which contains
[-- Attachment #2: Type: text/plain, Size: 205 bytes --]
From: "Pavel Janík ml." <Pavel.Janik@inet.cz>
and customize the gnus-extract-... to mail-... it will display only Pavel
Janík even if there is "Pavel Janík ml."...
--
Pavel Janík ml.
Pavel.Janik@inet.cz
next prev parent reply other threads:[~2000-04-24 18:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-22 9:55 Pavel.Janik
2000-04-22 11:09 ` Lars Magne Ingebrigtsen
2000-04-23 20:07 ` Pavel.Janik
2000-04-24 14:31 ` Lars Magne Ingebrigtsen
2000-04-24 17:04 ` Pavel Janik ml.
2000-04-24 18:39 ` Kai Großjohann
2000-04-24 18:56 ` Pavel Janík ml. [this message]
2000-04-25 11:04 ` Kai Großjohann
2000-04-25 11:38 ` Lars Magne Ingebrigtsen
2000-04-25 11:35 ` Kai Großjohann
2000-04-25 20:03 ` Florian Weimer
2000-04-25 20:15 ` Kai Großjohann
2000-04-26 17:14 ` Florian Weimer
2000-04-26 17:29 ` Shenghuo ZHU
2000-04-26 18:06 ` Florian Weimer
2000-04-26 18:15 ` Shenghuo ZHU
2000-04-25 13:36 ` Pavel Janík ml.
2000-04-25 14:47 ` Kai Großjohann
2000-04-25 15:31 ` Pavel Janík ml.
2000-04-25 17:10 ` Kai Großjohann
2000-04-25 10:45 ` Florian Weimer
2000-04-25 11:11 ` Kai Großjohann
2000-04-25 6:42 ` Jaap-Henk Hoepman
2000-04-26 14:05 ` Erik Toubro Nielsen
2000-04-26 20:59 ` Pavel Janík ml.
2000-04-28 2:00 ` Shenghuo ZHU
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3hfcrz5te.fsf@SnowWhite.inet.cz \
--to=pavel.janik@inet.cz \
--cc=ding@gnus.org \
/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 NNTP newsgroup(s).