unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sebastian Tennant <sebyte@smolny.plus.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: bug-gnu-emacs@gnu.org, Sebastian Tennant <sebyte@smolny.plus.com>,
	1973@emacsbugs.donarmstrong.com
Subject: bug#1973: Bug in simple.el (Emacs version 22.2.1)
Date: Thu, 22 Jan 2009 08:45:41 +0000	[thread overview]
Message-ID: <eiyvwwy2.fsf@vps203.linuxvps.org> (raw)
In-Reply-To: <jwvvds8mia0.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Wed, 21 Jan 2009 17:04:23 -0500")

Quoth Stefan Monnier <monnier@iro.umontreal.ca>:
>> Asynchronous commands called via shell-command, for example:
>
>>  (shell-command "apt-get update &")
>
>> fill the buffer *Async Shell Command Output* with Ctrl-Ms, which I'm
>> sure is not what's intended.
>
>> My patch (attached) fixes this by using make-comint-in-buffer, rather
>> than start-process, to call the asynchronous process.
>
> Such a feature would be good, indeed.  

Sorry Stefan, I'm not sure what feature it is you are refering to.

There seems to be a bug within shell mode that prevents it from handling
Ctrl-Ms properly.

> 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?

In any case, I suspect we should extend rather than alter, comint mode
being the basis for dozens of other 'interpreter modes'.

Sebastian






  reply	other threads:[~2009-01-22  8:45 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 [this message]
2009-01-22 15:09       ` Stefan Monnier
2009-01-22 18:07         ` Sebastian Tennant
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

  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=eiyvwwy2.fsf@vps203.linuxvps.org \
    --to=sebyte@smolny.plus.com \
    --cc=1973@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.savannah.gnu.org/cgit/emacs.git

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