Gnus development mailing list
 help / color / mirror / Atom feed
From: Brian May <bam@snoopy.apana.org.au>
Cc: Brian May <bmay@csse.monash.edu.au>
Subject: [supercite] from address mis-parsed
Date: 17 Dec 1999 08:59:49 +1100	[thread overview]
Message-ID: <84d7s61r8q.fsf@snoopy.apana.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 304 bytes --]

Hello,

I found this bug in supercite. When I tried to mail the supercite bug
reporting address, the mail bounced...

Does anyone have any ideas what I should do with this bug report?

I have been told that the address in question, while it looks strange,
is actually quite correct.

Thanks in advance.


[-- Attachment #2: Type: message/rfc822, Size: 2413 bytes --]

From: Brian May <bam@snoopy.apana.org.au>
To: supercite-help@anthem.nlm.nih.gov
Subject: from address mis-parsed
Date: Wed,  1 Dec 1999 09:08:27 +1100 (EST)
Message-ID: <19991130220827.4F701179C@snoopy.apana.org.au>


Original:
From: "Roy J. Tellason" <"Roy=20J.=20Tellason"@f615.n270.z1.fidonet.org>

When following up, the header is:
>>>>> "Roy" == Roy J Tellason" <"Roy=20J =20Tellason <Roy> writes:
 
Perhaps that address is illegal (not sure if quotes are allowed there,
might be a bug in my gateway). If so please tell me, and I will
complain elsewhere. In fact, I might complain there anyway, that
address looks wrong.

However, I find supercites interpretation... well... strange.

Emacs  : XEmacs 20.4 "Emerald" [Lucid] (i386-debian-linux) of Thu Jan  7 1999 on dres
Package: Supercite version 3.1

current state:
==============
(setq
 sc-attrib-selection-list nil
 sc-auto-fill-region-p nil
 sc-blank-lines-after-headers 1
 sc-citation-leader "    "
 sc-citation-delimiter ">"
 sc-citation-separator " "
 sc-citation-leader-regexp "[ 	]*"
 sc-citation-root-regexp "[-._a-zA-Z0-9]*"
 sc-citation-nonnested-root-regexp "[-._a-zA-Z0-9]+"
 sc-citation-delimiter-regexp "[>]+"
 sc-citation-separator-regexp "[ 	]*"
 sc-cite-region-limit t
 sc-confirm-always-p t
 sc-default-attribution "Anon"
 sc-default-author-name "Anonymous"
 sc-downcase-p nil
 sc-electric-circular-p t
 sc-electric-references-p nil
 sc-fixup-whitespace-p nil
 sc-mail-warn-if-non-rfc822-p t
 sc-mumble ""
 sc-name-filter-alist '(("\\[.*\\]\\|\\[[^]]*\\|[^[]*\\]" . any)
			("^\\(Mr\\|Mrs\\|Ms\\|Dr\\)[.]?$" . 0)
			("^\\(Jr\\|Sr\\)[.]?$" . last) ("^ASTS$" . 0)
			("^[I]+$" . last))
 sc-nested-citation-p nil
 sc-nuke-mail-headers 'all
 sc-nuke-mail-header-list nil
 sc-preferred-attribution-list '("sc-lastchoice" "x-attribution" "firstname"
				 "initials" "lastname")
 sc-preferred-header-style 4
 sc-reference-tag-string ">>>>> "
 sc-rewrite-header-list '((sc-no-header) (sc-header-on-said)
			  (sc-header-inarticle-writes)
			  (sc-header-regarding-adds)
			  (sc-header-attributed-writes)
			  (sc-header-author-writes) (sc-header-verbose)
			  (sc-no-blank-line-or-header)
			  (sc-header-author-email-writes))
 sc-titlecue-regexp "\\s +-+\\s +"
 sc-use-only-preference-p nil
 )


[-- Attachment #3: Type: text/plain, Size: 41 bytes --]


-- 
Brian May <bam@snoopy.apana.org.au>

                 reply	other threads:[~1999-12-16 21:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=84d7s61r8q.fsf@snoopy.apana.org.au \
    --to=bam@snoopy.apana.org.au \
    --cc=bmay@csse.monash.edu.au \
    /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).