From: Michael Welsh Duggan <md5i@cs.cmu.edu>
Subject: Re: For lack of content...
Date: Mon, 31 Aug 1998 22:02:49 GMT [thread overview]
Message-ID: <v1td89gyflk.fsf@peoria.mt.cs.cmu.edu> (raw)
In-Reply-To: <m3emtwx2oi.fsf@sparky.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Michael Welsh Duggan <md5i@cs.cmu.edu> writes:
> > I actually wrote a prototype of such myself, but ran into the
> > problem that decode-coding-region trashes text-properties.
>
> Hm. It does seem that that function trashes text props. Why?
Here's a segment of the discussion engendered by my original bug
report:
| From: Kenichi Handa <handa@etl.go.jp>
| Subject: Re: Text Properties in decoded regions (correction)
| To: rms@gnu.org
| CC: md5i@cs.cmu.edu
| Date: Thu, 27 Aug 1998 14:35:01 +0900
|
| Richard Stallman <rms@santafe.edu> writes:
| > I asked Handa what he thinks we should do.
| > In principle, decode-encoding-region should preserve text properties,
| > but if that is hard to do, maybe it should delete them.
|
| It's a rather hard task to preserve text properties with
| decode-coding-region and encode-coding-region. At least, I can't do
| that before the release of 20.4.
|
| So, I agree that we should delete text properties of the target region
| and document it.
(BTW, is there a good way in Gnus to do forwards of other articles in
replies to other articles, or cites from multiple articles?)
--
Michael Duggan
(md5i@cs.cmu.edu)
.
next prev parent reply other threads:[~1998-08-31 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-31 18:18 Michael Welsh Duggan
1998-08-31 21:27 ` Lars Magne Ingebrigtsen
1998-08-31 22:02 ` Michael Welsh Duggan [this message]
1998-09-01 1:47 ` Justin Sheehy
1998-09-01 14:30 ` Michael Welsh Duggan
1998-09-01 22:33 ` Lars Magne Ingebrigtsen
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=v1td89gyflk.fsf@peoria.mt.cs.cmu.edu \
--to=md5i@cs.cmu.edu \
/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).