From: Sebastian Tennant <sebyte@smolny.plus.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#1973: Bug in simple.el (Emacs version 22.2.1)
Date: Thu, 22 Jan 2009 18:07:03 +0000 [thread overview]
Message-ID: <mydj2p14.fsf@vps203.linuxvps.org> (raw)
In-Reply-To: jwvzlhjjsv4.fsf-monnier+emacsbugreports@gnu.org
Quoth "Stefan Monnier" <monnier@iro.umontreal.ca>:
>> There seems to be a bug within shell mode that prevents it from handling
>> Ctrl-Ms properly.
>
> It's not a bug. shell-command just runs a command and gives you the output
> of the command. Some commands presume the output is displayed by some
> kind of terminal and will use terminal commands like ^M (or even ANSI
> color escape sequences), whereas shell-command was not designed for
> this purpose.
So the shell mode used in interactive shells (started with M-x shell) is
enhanced somehow to handle ^Ms?
Note that Kevin Rodgers does not observe the same behaviour:
http://article.gmane.org/gmane.emacs.bugs/24348
>>> I'm not sure that just using make-comint-in-buffer is good enough.
>>> Maybe we should provide a new command instead, along the lines of
>>> comint-run, or maybe even change comint-run so that it accepts a shell
>>> command rather than an executable name.
>>
>> Why?
>
> Because I'm not sure in what kinds of circumstances people use
> shell-command with an "&" at the end.
I use it for commands that take a while to complete, so that I can
continue doing other things and/or watch what's going on. I expect the
buffer to behave/look/feel as much like an ordinary shell as possible.
Perhaps this is not typical. I don't know.
>> In any case, I suspect we should extend rather than alter, comint mode
>> being the basis for dozens of other 'interpreter modes'.
>
> `comint-run' is a command (i.e. for interactive use). I do see that it
> is occasionally misused from Elisp code (which should use make-comint
> instead), so we should be somewhat careful indeed when changing it.
Noted (and agreed)
Sebastian
--
Emacs' AlsaPlayer - Music Without Jolts
Lightweight, full-featured and mindful of your idyllic happiness.
http://home.gna.org/eap
next prev parent reply other threads:[~2009-01-22 18:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ocqnneu3.fsf@cyd.mit.edu>
2009-01-20 20:10 ` bug#1973: Bug in simple.el (Emacs version 22.2.1) Sebastian Tennant
2009-01-21 4:59 ` Kevin Rodgers
2009-01-21 10:34 ` Sebastian Tennant
2009-01-21 22:04 ` Stefan Monnier
2009-01-22 8:45 ` Sebastian Tennant
2009-01-22 15:09 ` Stefan Monnier
2009-01-22 18:07 ` Sebastian Tennant [this message]
2009-01-22 21:30 ` Stefan Monnier
2009-01-22 23:15 ` Sebastian Tennant
2009-01-23 7:53 ` Stefan Monnier
2009-01-23 10:46 ` Sebastian Tennant
2009-01-23 18:01 ` Sebastian Tennant
2009-01-25 17:58 ` Sebastian Tennant
2009-01-22 14:00 ` Sebastian Tennant
2009-01-22 18:27 ` Sebastian Tennant
2009-08-11 4:45 ` bug#1973: marked as done (Bug in simple.el (Emacs version 22.2.1)) Emacs bug Tracking System
2009-01-24 21:14 bug#1973: Bug in simple.el (Emacs version 22.2.1) Stefan Monnier
2009-02-04 9:47 ` Sebastian Tennant
[not found] <63k0dk26.fsf@vps203.linuxvps.org>
[not found] ` <jwveiyno719.fsf-monnier+emacs@gnu.org>
2009-01-29 7:06 ` bug#2103: Bug in simple.el Sebastian Tennant
2009-08-11 4:45 ` bug#2103: marked as done (Bug in simple.el) Emacs bug Tracking System
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=mydj2p14.fsf@vps203.linuxvps.org \
--to=sebyte@smolny.plus.com \
--cc=1973@emacsbugs.donarmstrong.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.