Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Wrong use of "path" in spam.el
Date: Wed, 27 Dec 2006 14:24:12 -0500	[thread overview]
Message-ID: <g69hcvh5ehv.fsf@dhcp-65-162.kendall.corp.akamai.com> (raw)
In-Reply-To: <v9zm999tb9.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed\, 27 Dec 2006 17\:50\:34 +0100")

On 27 Dec 2006, reinersteib+gmane@imap.cc wrote:

On Wed, Dec 27 2006, Ted Zlatanov wrote: 
> On 26 Dec 2006, reinersteib+gmane@imap.cc wrote:
>>> [...] `spam-*-path' variables and doc strings.  We should rename
>>> those variables to `spam-*-program' and mark the former as obsolete.
>>>
>>> I'm not 100% sure that it's a good idea to do this now (while Emacs 22
>>> is in pretest), but OTOH spam.el was not part of Emacs 21 so it's
>>> probably better to do it now so that Emacs 22 will have the right
>>> names.  Opinions?
>>
>> I'm OK with that.  Since the old variable names will work today, I
>> expect the support issues to be minimal.  
>
> Maybe we should better use `defvaralias' instead of
> `make-obsolete-variable'?  I wasn't sure which one is more suitable
> here.

I'm OK with either; I don't know the right one though.

>> But the manual will also have to be updated,
>
> AFAICS, it's only the following change (installed in v5-10):
> --- gnus.texi	26 Dec 2006 19:10:32 +0100	6.603.2.107
> +++ gnus.texi	27 Dec 2006 17:38:39 +0100	
> @@ -23952,7 +23952,7 @@
> the default value of @samp{spam}.
> @end defvar
>
> -@defvar spam-ifile-database-path
> +@defvar spam-ifile-database
>
> This is the filename for the ifile database.  It is not specified by
> default, so ifile will use its own default database name.

OK, I thought there were more.  Sorry.

>> and we need to check with the Emacs maintainers regarding the 22
>> prerelease.
>
> The changes will automatically be included in the next pretest after
> Miles next sync.  Do you have something else in mind?

That was all, I didn't know if we need to ask before making such
changes since they are not really bug fixes.

Ted



  reply	other threads:[~2006-12-27 19:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-26 17:33 Reiner Steib
2006-12-27 13:53 ` Ted Zlatanov
2006-12-27 16:50   ` Reiner Steib
2006-12-27 19:24     ` Ted Zlatanov [this message]
2006-12-27 21:49       ` Reiner Steib
2006-12-27 23:31         ` Miles Bader
2006-12-28 14:57           ` Reiner Steib
2006-12-28 19:55         ` Reiner Steib

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=g69hcvh5ehv.fsf@dhcp-65-162.kendall.corp.akamai.com \
    --to=tzz@lifelogs.com \
    /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).