zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: Gary Oberbrunner <garyo@genarts.com>,
	zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Zsh 4.0.4 and Emacs 21.1 in Windows XP
Date: Thu, 22 Nov 2001 11:35:54 +0000	[thread overview]
Message-ID: <4930.1006428954@csr.com> (raw)
In-Reply-To: "Gary Oberbrunner"'s message of "Wed, 21 Nov 2001 14:59:55 EST." <3BFC07BB.8090601@genarts.com>

Gary Oberbrunner wrote:
> I'm trying to use Zsh 4.0.4 on Windows XP with Emacs 21.1 in shell-mode. 
>  I compiled both of them from sources.
> 
> Everything works OK except zsh thinks all my input has an extra CR (^M) 
> at the end of each line.

If you mean you are seeing extra ^M's appearing, I don't think this is
specific to Windows, actually.  Here's the entry from the FAQ --- see if
this helps with your problem.

3.10: Why does zsh not work in an Emacs shell mode any more?

  (This information comes from Bart Schaefer and other zsh-workers.)

  Emacs 19.29 or thereabouts stopped using a terminal type of "emacs"
  in shell buffers, and instead sets it to "dumb".  Zsh only kicks in
  its special I'm-inside-emacs initialization when the terminal type
  is "emacs".

  Probably the most reliable way of dealing with this is to look for
  the environment variable `$EMACS', which is set to `t' in
  Emacs' shell mode.  Putting

    [[ $EMACS = t ]] && unsetopt zle

  in your .zshrc should be sufficient.

  Another method is to put

    #!/bin/sh
    TERM=emacs exec zsh

  into a file ~/bin/eshell, then `chmod +x ~/bin/eshell', and
  tell emacs to use that as the shell by adding

    (setenv "ESHELL" (expand-file-name "~/bin/eshell"))

  to ~/.emacs.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 392070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


      parent reply	other threads:[~2001-11-22 11:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 19:59 Gary Oberbrunner
2001-11-22 11:26 ` Borsenkow Andrej
2001-11-23  2:38   ` Gary Oberbrunner
2001-11-23  6:05     ` Borsenkow Andrej
2001-11-23 15:48       ` Gary Oberbrunner
2001-11-23 22:09         ` Gary Oberbrunner
2001-11-23 21:21   ` Gary Oberbrunner
2001-11-26  7:32     ` Borsenkow Andrej
2001-11-26 15:31       ` Gary Oberbrunner
2002-02-08 15:20   ` Gary Oberbrunner
2001-11-22 11:35 ` Peter Stephenson [this message]

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=4930.1006428954@csr.com \
    --to=pws@csr.com \
    --cc=garyo@genarts.com \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).