From: jari.aalto@poboxes.com (Jari Aalto+mail.emacs)
Cc: ding@gnus.org
Subject: Re: User Agent string: making it more specific?
Date: 31 Dec 1999 17:45:17 +0200 [thread overview]
Message-ID: <wkvh5ff71u.fsf@blue.sea.net> (raw)
In-Reply-To: Karl Kleinpaste's message of "31 Dec 1999 06:09:48 -0500"
This is your copy. Article has been posted to the newsgroup(s).
* 1999-12-31 Karl Kleinpaste <karl@justresearch.com> gnu.emacs.gnus
* <http://search.dejanews.com/msgid.xp?MID=%3Cvxkg0wjjrib.fsf@beaver.jprc.com%3E&format=threaded>
| Jonadab the Unsightly One <jonadab@bright.net> writes:
| [+]
| > I'd like to have it be more specific, for example:
| > User-Agent: Gnus v5.8.2 GNU Emacs 20.4.1 (i386-*-windows95.1212)
| > Is there an easy way to do this?
|
| No. User-Agent, in the USEFOR draft, has a rather particular syntax.
| The general form for each segment is "name/version (free format string)"
| and its generation is fixed. If there were an architecture string
| naturally part of Emacs 20.4's environment, that would go into the
| parenthesized part at the end, but there isn't one.
...But Emacs knows it Karl :-)
I suggest that the architecture info is added to next Gnus release
jari
(defadvice gnus-extended-version (around my act)
"Add Architechture string to User-Agent: string."
ad-do-it
(setq
ad-return-value
(format "%s (%s)"
ad-return-value
system-configuration )))
(gnus-extended-version)
--> "Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 (i386-*-windows98.1998)"
next parent reply other threads:[~1999-12-31 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <wk4scz7bca.fsf@R1.JONADAB.NET>
[not found] ` <vxkg0wjjrib.fsf@beaver.jprc.com>
1999-12-31 15:45 ` Jari Aalto+mail.emacs [this message]
2000-01-02 23:46 ` Stainless Steel Rat
2000-01-03 8:22 ` Per Abrahamsen
2000-01-03 9:02 ` Eric Marsden
2000-01-03 9:12 ` Arcady Genkin
2000-01-03 9:39 ` Florian Weimer
2000-01-03 11:58 ` William M. Perry
2000-01-03 15:40 ` Stainless Steel Rat
2000-01-03 19:10 ` Kai Großjohann
2000-01-04 16:52 ` Steinar Bang
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=wkvh5ff71u.fsf@blue.sea.net \
--to=jari.aalto@poboxes.com \
--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).