Gnus development mailing list
 help / color / mirror / Atom feed
From: jsbien@mimuw.edu.pl (Janusz S. Bien)
Cc: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: Re: should mbox be opened in unibyte mode
Date: 23 May 2000 05:26:56 -0000	[thread overview]
Message-ID: <20000523052656.31940.qmail@duch.mimuw.edu.pl> (raw)

Vladimir wrote:

>Here at home i only have GNU Emacs 20.4, and describe-coding-system
>says about `binary':
>
[...]
>Perhaps, 20.6 has a more verbose description (which states in
>particular that 'binary forces unibyte).

There is no substantial difference between GNU 20.4 and 20.6 in this
respect (21 will introduce some important changes).

My quotation come from the "Coding systems" section of Emacs manual
--- look at "International character support" chapter or search the
info files for relevant phrases. The Elisp manual contains also
useful information (IHMO, some of it would be better placed in the
user manual).

>(btw, where i can access the current CVS emacs version for testing?)

It's not so simple, but you definitely will be welcomed as a
pretester. Contact Gerd Moellmann <gerd@gnu.org> for details.

>(BTW, when a buffer is multibyte, C-x RET f binary RET is not supposed
>to switch to unibyte mode, right? only opening a file with a binary
>mode (C-x RET c binary RET C-x C-f filename RET) does this?)

Right.

Regards

Janusz

---------------------------------------------------------------------
                     ,   
dr hab. Janusz S. Bien, prof. UW
Prof. Janusz S. Bien, Warsaw Uniwersity
---------------------------------------------------------------------
---------------------------------------------------------------------
Na tym koncie czytam i wysylam poczte i wiadomosci offline -
prosze nie oczekiwac szybkiej odpowiedzi!
Data w naglowku to data rozpoczecia pisania listu, a nie jego wyslania.
---------------------------------------------------------------------
On this account I read/post mail/news offline - do not expect 
an immediate answer!
The date in the header refers to the moment when I started to write
the letter, not to the moment when I sent it.
---------------------------------------------------------------------



             reply	other threads:[~2000-05-23  5:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-23  5:26 Janusz S. Bien [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-05-22  6:06 Janusz S. Bien
2000-05-22 19:47 ` Vladimir Volovich
2000-05-21 14:08 Janusz S. Bien
2000-05-21 16:15 ` 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=20000523052656.31940.qmail@duch.mimuw.edu.pl \
    --to=jsbien@mimuw.edu.pl \
    --cc=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).