Gnus development mailing list
 help / color / mirror / Atom feed
From: Vladimir Volovich <vvv@vvv.vsu.ru>
Cc: ding@gnus.org
Subject: Re: should mbox be opened in unibyte mode
Date: 21 May 2000 20:15:04 +0400	[thread overview]
Message-ID: <m3puqfop6f.fsf@vvv.vsu.ru> (raw)
In-Reply-To: jsbien@mimuw.edu.pl's message of "Sun, 21 May 2000 15:08:05 +0100"

"JSB" == Janusz S Bien writes:

 JSB> It, too, sets `enable-multibyte-characters' to `nil'.
 JSB> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 >> i've tried the above settings of nnmbox-file-coding-system and
 >> nnmbox-active-file-coding-system but nevertheless mbox is still
 >> opened in multibyte mode (in violation with the above).

 JSB> Do you use XEmacs or GNU Emacs? This appeared to be relevant.

I use GNU Emacs.

 JSB> You can force (in GNU Emacs) the current buffer to unibyte mode
 JSB> with `toggle-enable-multibyte-characters'. Does it help?

Yes, i can manually switch to unibyte mode in mbox buffer using
toggle-enable-multibyte-characters.

But:

1) imho it should be done by gnus (i.e. gnus should open mbox in
   unibyte mode in the first place)

2) you wrote that

 > In contrast, the coding system `no-conversion' specifies no
 > character code conversion at all--none for non-ASCII byte values and
 > none for end of line.  This is useful for reading or writing binary
 > files, tar files, and other files that must be examined verbatim.  It,
 > too, sets `enable-multibyte-characters' to `nil'.

is the above about XEmacs or GNU Emacs? If it is about GNU Emacs, then
why setting nnmbox-file-coding-system to 'binary does not switch off
multibyte characters?

	Best regards, -- Vladimir.



  reply	other threads:[~2000-05-21 16:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-21 14:08 Janusz S. Bien
2000-05-21 16:15 ` Vladimir Volovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-05-23  5:26 Janusz S. Bien
2000-05-22  6:06 Janusz S. Bien
2000-05-22 19:47 ` Vladimir Volovich
2000-05-05 21:50 Janusz S. Bien
2000-05-05  5:42 Janusz S. Bien
2000-05-05 15:31 ` Stainless Steel Rat
2000-05-05 16:38   ` Hrvoje Niksic
2000-05-05 17:00     ` Shenghuo ZHU
2000-05-05 17:15       ` Hrvoje Niksic
2000-05-05 17:46         ` Kai Großjohann
2000-05-06 18:55           ` Hrvoje Niksic
2000-05-06  0:50     ` Stainless Steel Rat
2000-05-21  8:31 ` Vladimir Volovich
2000-05-04 11:04 Vladimir Volovich
2000-05-04 14:39 ` Shenghuo ZHU
2000-05-04 20:27   ` Vladimir Volovich
2000-05-04 21:33     ` Shenghuo ZHU
2000-05-05  5:05     ` Shenghuo ZHU

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=m3puqfop6f.fsf@vvv.vsu.ru \
    --to=vvv@vvv.vsu.ru \
    --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).