Sivaram Neelakantan <nsivaram....@gmail.com> writes:
> I've run into this problem and I don't know where to start. I got a
> new laptop and went about installing all the usual bits of software,
> Emacs and Cygwin. Things mostly work as advertised....however when I
> do M-x shell, I get
[...]
What version of Emacs are you running?
> and my cygwin configuration in my .Emacs is
>
> (setq exec-path (cons "C:/gnu/bin/" exec-path))
> (setq exec-path (cons "C:/cygwin/usr/bin" (cons "C:/cygwin/bin" exec-path)))
> (setq exec-path (cons "C:/MiKTeX2.9/miktex/bin" exec-path))
> (setenv "PATH" (concat
> "C:\\MiKTeX2.9\\miktex\\bin;C:\\cygwin\\bin;C:\\cygwin\\usr\\bin;C:\\gnu\\bin\\;"
> (getenv "PATH")))
>
> ;; NT-emacs assumes a Windows command shell, which you change
> ;; here.
> ;;
> (setq process-coding-system-alist '(("bash" . undecided-unix)))
> (setq w32-quote-process-args ?\")
I stopped using these last two commands above.
> (setq shell-file-name "/usr/bin/bash")
> ;;(setq shell-file-name "C:/cygwin/usr/bin/bash")
> (setenv "SHELL" shell-file-name)
My version looks like the one you commented out, ie:
(setq shell-file-name "C:/cygwin/bin/bash.exe")
> (setq explicit-shell-file-name shell-file-name)
> ;; This removes unsightly ^M characters that would otherwise
> ;; appear in the output.
> ;;
> (add-hook 'comint-output-filter-functions
> 'comint-strip-ctrl-m)
I also stopped using the line above. Not sure if something changed in
Emacs 23.x or Cygwin but when I have problems like these, I start Emacs
with "emacs -q" and start adding lines from my ~/.emacs back till the
problem returns (actually, it just means evaluating lines or sections of
code till something blows up). Good luck.
Sarir
--
Sarir Khamsi
software guy
sarir.kha...@raytheon.com
