unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
Subject: Re: C-x RET does not do what the documentation says it should
Date: Sat, 21 Feb 2004 11:52:54 +0200	[thread overview]
Message-ID: <9743-Sat21Feb2004115254+0200-eliz@elta.co.il> (raw)
In-Reply-To: <72A87F7160C0994D8C5A36E2FDC227F50925A59A@txnexc01.americas.cpqcorp.net> (jay.bingham@hp.com)

> Date: Fri, 20 Feb 2004 18:18:20 -0600
> From: "Bingham, Jay" <jay.bingham@hp.com>
> 
> In emacs 20.4 (running on a Unix platform), the key sequence is a prefix
> for commands that pertain to multibyte characters coding systems, and
> input methods.
> In emacs 21.2 (the win32 binary loaded from the windows page
> <http://ftp.gnu.org/gnu/windows/emacs/latest> running on a Windows32
> platform), the key sequence C-x RET now invokes spell [...]
> 
> Since I do not have access to an emacs 21.1 running on a UNIX platform I
> don't know if this is a bug or if the person who created the win32
> binary provided this feature.

Are you sure your Emacs behaves like that even when invoked with the
"-q --no-init-file" switches?

If indeed your local customizations are not responsible for this, it's
some strange bug in the binary you are using.  While I cannot test
that precise binary, I have 2 versions of the Windows port of Emacs
21.x on my machines, and they both behave as advertised: "C-x RET" is
a prefix of the commands related to encoding and decoding text.

  reply	other threads:[~2004-02-21  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-21  0:18 C-x RET does not do what the documentation says it should Bingham, Jay
2004-02-21  9:52 ` Eli Zaretskii [this message]
     [not found] <mailman.220.1077322824.340.help-gnu-emacs@gnu.org>
2004-02-21  9:57 ` Alan Mackenzie
  -- strict thread matches above, loose matches on Subject: below --
2004-02-23 16:35 Bingham, Jay

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9743-Sat21Feb2004115254+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).