Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: gnus-registry.el on emacs-unicode-2 (Emacs 23)
Date: Thu, 28 Sep 2006 14:43:26 -0400	[thread overview]
Message-ID: <g69zmcjsugh.fsf@CN1374059D0130.kendall.corp.akamai.com> (raw)
In-Reply-To: <v9r6xvudft.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 28 Sep 2006 19:08:06 +0200")

On 28 Sep 2006, reinersteib+gmane@imap.cc wrote:

> Could you please try if the problem also exists in Emacs 22 (trunk)?
> As I understand from the previous messages, it only exists in
> emacs-unicode-2 (Emacs 23).  Is this correct?  Then I could remove it
> from the list of release-relevant bugs for Emacs 22
> (admin/FOR-RELEASE).

I think the problem will exist in any Emacs that has text properties.
Emacs 22 does, I believe.

Ted



  reply	other threads:[~2006-09-28 18:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m37izsx28r.fsf@sl392.st-edmunds.cam.ac.uk>
     [not found] ` <E1GRdu3-0001cN-00@etlken>
     [not found]   ` <ufyegboyc.fsf@news.eqiao.com>
     [not found]     ` <E1GSBLt-0004R0-00@etlken>
     [not found]       ` <m2u02usrmr.fsf@eqiao.com>
     [not found]         ` <m2mz8msjey.fsf@eqiao.com>
     [not found]           ` <m2irjatuek.fsf@eqiao.com>
     [not found]             ` <E1GSOhd-0006lo-00@etlken>
     [not found]               ` <uac4mnjez.fsf@news.eqiao.com>
     [not found]                 ` <E1GSPRU-0007Ka-00@etlken>
     [not found]                   ` <ud59ij6nq.fsf@news.eqiao.com>
     [not found]                     ` <E1GSRA4-0000HP-00@etlken>
     [not found]                       ` <uejtx519t.fsf@news.eqiao.com>
     [not found]                         ` <E1GSSdJ-0001Tm-00@etlken>
     [not found]                           ` <u64f9203s.fsf@news.eqiao.com>
     [not found]                             ` <E1GSYk0-0000MT-00@etlken>
     [not found]                               ` <m2ejtx79k4.fsf@eqiao.com>
2006-09-27 14:43                                 ` gnus-registry.el on emacs-unicode-2 (Emacs 23) (was: [bug]Malformed -*- line) Reiner Steib
2006-09-27 14:55                                   ` CHENG Gao
2006-09-28 17:08                                     ` gnus-registry.el on emacs-unicode-2 (Emacs 23) Reiner Steib
2006-09-28 18:43                                       ` Ted Zlatanov [this message]
2006-09-29  3:09                                         ` CHENG Gao
2006-09-28  2:14                                   ` gnus-registry.el on emacs-unicode-2 (Emacs 23) (was: [bug]Malformed Richard Stallman
     [not found]                       ` <g69lko5w7jn.fsf_-_@CN1374059D0130.kendall.corp.akamai.com>
     [not found]                         ` <u3bachfrs.fsf@news.eqiao.com>
     [not found]                           ` <E1GSnBy-0003Ow-00@etlken>
     [not found]                             ` <ur6xwbl6i.fsf@news.eqiao.com>
     [not found]                               ` <E1GSpdJ-0007Hs-00@etlken>
     [not found]                                 ` <E1GSplm-0007OB-00@etlken>
2006-09-28 14:35                                   ` gnus-registry text property removal question Ted Zlatanov
2006-09-28 18:41                                     ` Ted Zlatanov

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=g69zmcjsugh.fsf@CN1374059D0130.kendall.corp.akamai.com \
    --to=tzz@lifelogs.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).