From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Bug? Are multibyte marks (e.g. gnus-unseen-mark) allowed?
Date: Wed, 07 Jan 2004 22:09:13 +0100 [thread overview]
Message-ID: <v91xqb4gau.fsf@marauder.physik.uni-ulm.de> (raw)
Hi,
I've changed `gnus-unseen-mark' to some Latin-1 char and found that
`o' (gnus-summary-save-article) no longer works.
To reproduce:
(setq gnus-unseen-mark 2231) ;; or use `?·' (middle dot)
(setq gnus-default-article-saver (lambda (&optional n) n))
Enter a group with unseen article and hit `o' on an unseen article.
Here's the backtrace:
Debugger entered--Lisp error: (error "Characters \
in subst-char-in-region have different byte-lengths")
subst-char-in-region(85 86 2231 83)
gnus-summary-update-mark(83 replied)
gnus-summary-update-secondary-mark(1714)
gnus-summary-set-saved-mark(1714)
gnus-summary-save-article(nil)
call-interactively(gnus-summary-save-article)
This is the relevant line in `gnus-summary-update-mark':
;; Replace the old mark with the new mark.
(subst-char-in-region (point) (1+ (point)) (char-after) mark)
;; ^^^^^^^^^^^^
_If_ `gnus-*-mark' must not be multibyte, we should document it.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next reply other threads:[~2004-01-07 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 21:09 Reiner Steib [this message]
2004-01-08 17:47 ` Jesper Harder
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=v91xqb4gau.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).