From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Bug? Are multibyte marks (e.g. gnus-unseen-mark) allowed?
Date: Thu, 08 Jan 2004 18:47:49 +0100 [thread overview]
Message-ID: <m3zncygwmy.fsf@defun.localdomain> (raw)
In-Reply-To: <v91xqb4gau.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 07 Jan 2004 22:09:13 +0100")
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> I've changed `gnus-unseen-mark' to some Latin-1 char and found that
> `o' (gnus-summary-save-article) no longer works.
>
> _If_ `gnus-*-mark' must not be multibyte, we should document it.
I think multibyte should be allowed.
But my naive fix (delete-char, insert-char instead of
subst-char-in-region) had some unintended side effects.
prev parent reply other threads:[~2004-01-08 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 21:09 Reiner Steib
2004-01-08 17:47 ` Jesper Harder [this message]
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=m3zncygwmy.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/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).