running os commands on ms windows

running os commands on ms windows

[sliwa]

--text follows this line--
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.

In GNU Emacs 21.2.1 (i386-msvc-windows98.2222)
 of 2002-03-27 on NEVERYON
configured using `configure --with-msvc (12.00)'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: plk
  locale-coding-system: iso-latin-2
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

Running DOS commands fails if the shell config.sys variable is not a
plain file name (i.e. if there are the usual parameters like
shell="c:\windows\command.com /p /e:4096").

C.S.


Recent input:

Recent messages:
isearch-abort: Quit
Loading emacsbug...done
byte-code: Quit
isearch-abort: Quit
Mark saved where search started
Loading ispell...done
Starting new Ispell process...
ispell-init-process: ispell did not output version line
(Shell command failed with no output)
shell-command-on-region: Searching for program: no such file or directory, "c:\windows\command.com /p /e:4096"

Re: running os commands on ms windows

[Eli Zaretskii]

> From: sliwa@cft.edu.pl
> Date: Tue, 26 Nov 2002 14:38:35 +0100
> 
> Running DOS commands fails if the shell config.sys variable is not a
> plain file name (i.e. if there are the usual parameters like
> shell="c:\windows\command.com /p /e:4096").

I don't think you are allowed to do that.  SHELL's value should be a
single file name, not a shell command with options.