From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: Re: washing quoted-printable bug again
Date: 27 Oct 1998 21:14:33 +0300 [thread overview]
Message-ID: <m3n26hg9di.fsf@vvv.vsu.ru> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "27 Oct 1998 10:35:00 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> > I have the following in my .emacs file:
> >
> > (set-language-environment "Cyrillic-KOI8")
>
> I'm still not able to reproduce this. I start Emacs with --unibyte,
> and I have
>
> (set-language-environment "Cyrillic-KOI8")
>
> in my .emacs file. Still, no Gnus buffers show up with "R:". Are you
> totally, absolutely sure that nothing meddles with
> `enable-multibyte-characters' -- perhaps some site-wide init file?
Well, i just started "emacs --unibyte" with the following trivial
~/.emacs file (no ~/.gnus* files):
(set-default-font "fontset-standard")
(set-language-environment "Cyrillic-KOI8")
(load "files") ; partial bugfix for literal file visiting
(setq rfc2047-default-charset 'koi8-r)
(setq mm-default-coding-system 'koi8)
(setq gnus-select-method '(nntp "localhost"))
(setq gnus-secondary-select-methods '((nnmbox "")))
and buffers are unibyte "-:". But i'm not able to input/see russian
characters anymore! instead, i see latin1 (iso-8859-1) characters.
this is not with which i can live. :-) [and i tested again with my
"standard" .emacs running with --unibyte option, -- i got the same
result: all buffers were unibyte, but no russian characters]
And in general, is it good to run emacs with --unibyte? for example,
will japanese characters work? if i preview japanese/chinese mails in
gnus running in "emacs --unibyte", i see only messy symbols. imho,
gnus should work right without --unibyte too. and 0.36 worked fine,
--- things were broken in 0.38.
Best regards, vvv.
next prev parent reply other threads:[~1998-10-27 18:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-21 20:09 Vladimir Volovich
1998-10-24 7:06 ` Lars Magne Ingebrigtsen
1998-10-24 9:10 ` Vladimir Volovich
1998-10-24 18:02 ` Lars Magne Ingebrigtsen
1998-10-24 20:17 ` Vladimir Volovich
1998-10-24 20:48 ` Vladimir Volovich
1998-10-24 21:23 ` Lars Magne Ingebrigtsen
1998-10-24 21:51 ` Vladimir Volovich
1998-10-24 22:15 ` Lars Magne Ingebrigtsen
1998-10-25 7:26 ` Vladimir Volovich
1998-10-25 17:18 ` Lars Magne Ingebrigtsen
1998-10-25 20:03 ` Vladimir Volovich
1998-10-25 20:39 ` Lars Magne Ingebrigtsen
1998-10-25 22:56 ` Vladimir Volovich
1998-10-26 2:46 ` Lars Magne Ingebrigtsen
1998-10-26 8:29 ` Vladimir Volovich
1998-10-26 21:04 ` Lars Magne Ingebrigtsen
1998-10-26 22:02 ` Vladimir Volovich
1998-10-27 9:35 ` Lars Magne Ingebrigtsen
1998-10-27 18:14 ` Vladimir Volovich [this message]
1998-10-28 7:27 ` Steinar Bang
1998-11-09 8:52 ` Vladimir Volovich
1998-11-13 17:42 ` Lars Magne Ingebrigtsen
1998-10-29 10:26 ` Lars Magne Ingebrigtsen
1998-11-09 8:46 ` Vladimir Volovich
1998-11-09 9:05 ` Vladimir Volovich
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=m3n26hg9di.fsf@vvv.vsu.ru \
--to=vvv@vvv.vsu.ru \
/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).