Gnus development mailing list
 help / color / mirror / Atom feed
From: Alex Ott <ott@jet.msk.su>
Cc: ding@gnus.org
Subject: broken gnus summary in Cyrillic Environment
Date: Wed, 15 Sep 2004 09:41:57 +0400	[thread overview]
Message-ID: <ht2zn3sccm2.fsf@seal.service.jet.msk.su> (raw)

[-- Attachment #1: Type: text/plain, Size: 813 bytes --]

Hello all

I found strange bug when working with gnus 5.10.x and No Gnus with Emacs
from CVS. When i use default summary spec and Cyrillic-KOI8 environment,
summary lines is not updated in run-time (you can see this on first image
- gnus-brocken-summary.png, in this image, first two articles is readed,
but not marked by gnus). Also with this error, not working mark-processing
functions, such as, spam-move, etc.

With default language environment, all works fine - you can see this on the
second image - gnus-default-summary.png - this image was taken from gnus
and emacs without any customisation.

And i can work-around this bug with custom specifier of gnus summary, such
as  "%U%R%z %I%(%6{[ %}%-23,23n%6{ ]%}%) %s\n", for example. Results of
this, you can see on the third image - gnus-good-summary.png.


[-- Attachment #2: gnus-brocken-summary.png --]
[-- Type: image/png, Size: 27636 bytes --]

[-- Attachment #3: gnus-default-summary.png --]
[-- Type: image/png, Size: 20963 bytes --]

[-- Attachment #4: gnus-good-summary.png --]
[-- Type: image/png, Size: 27889 bytes --]

[-- Attachment #5: Type: text/plain, Size: 125 bytes --]



-- 
With best wishes, Alex Ott
Jet Infosystems,       http://www.jetinfosoft.ru/
                       +7 (095) 411 76 01

[-- Attachment #6: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

             reply	other threads:[~2004-09-15  5:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-15  5:41 Alex Ott [this message]
2004-09-15  7:57 ` Alex Ott
2004-10-03  0:15 ` Juri Linkov
2004-10-03  0:51   ` Miles Bader

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=ht2zn3sccm2.fsf@seal.service.jet.msk.su \
    --to=ott@jet.msk.su \
    --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).