From: Peter Tury <tury.peter@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: Re: offical Emacs 22.1: `term' problem on MS Windows
Date: Tue, 18 Mar 2008 01:08:10 -0700 (PDT) [thread overview]
Message-ID: <fd39bbf5-787d-4d44-bc28-092784a123ae@k13g2000hse.googlegroups.com> (raw)
In-Reply-To: mailman.9055.1205796345.18990.bug-gnu-emacs@gnu.org
On Mar 18, 12:25 am, Jason Rumney <jas...@gnu.org> wrote:
> Peter Tury wrote:
> > Then I digged into the code and saw that term-exec-1 from term.el
> > uses "/bin/sh" unconditionally. I tried to comment it out, so I got:
>
> > "
> > (apply 'start-process name buffer
> > ;; "/bin/sh" "-c"
> > ;; (format "stty -nl echo rows %d columns %d sane 2>/dev/null;\
> > ;;if [ $1 = .. ]; then shift; fi; exec \"$@\""
> > ;; term-height term-width)
> > ;; ".."
> > command switches)))
> > "
> > and, for first sight it seems to work (since `command' has write
> > value: "C:/Program Files/emacs-22.1/bin/cmdproxy.exe").
>
> It might seem to work for some definition of "work", but it is no longer
> a terminal emulator if you remove those lines, and you might as well
> just use M-x shell.
>
> AFAIK there is no way to get M-x term working on Windows, as its
> implementation of terminals is completely different and undocumented.
Then, I think, it should be removed from Windows binaries. Or be
documented as not working there. In its current form it simply gives
an error message showing some buggy behaviour. At least it should show
up an error message saying "this is not implemented in this OS". What
do you think?
Thanks,
P
next prev parent reply other threads:[~2008-03-18 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 17:49 offical Emacs 22.1: `term' problem on MS Windows Peter Tury
2008-03-17 23:25 ` Jason Rumney
[not found] ` <mailman.9055.1205796345.18990.bug-gnu-emacs@gnu.org>
2008-03-18 8:08 ` Peter Tury [this message]
2008-03-18 11:39 ` Jason Rumney
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=fd39bbf5-787d-4d44-bc28-092784a123ae@k13g2000hse.googlegroups.com \
--to=tury.peter@gmail.com \
--cc=bug-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.