|
|
> Today I found a topic, which gives a clean description about this:
> http://www.gnu.org/software/emacs/windows/faq7.html#subproc-buffer
>
> The output of PDB is buffered (by python.exe, not emacs) and cannot
> been displayed.
>
> Now it works with this command:
> python -u -m pdb test.py
>
> -u : unbuffered binary stdout and stderr (also PYTHONUNBUFFERED=x)
> see man page for details on internal buffering relating to '-
> u'
Perhaps then we should make the change below. Does this workd for you?
Does it work for anybody else with Python on Windows?
--
Nick http://www.inet.net.nz/~nickrob
*************** and source-file directory for your debug
*** 1622,1628 ****
output))
! (defcustom gud-pdb-command-name "pdb"
"File name for executing the Python debugger.
This should be an executable on your path, or an absolute file name."
:type 'string
--- 1622,1631 ----
output))
! (defcustom gud-pdb-command-name
! (if (eq system-type 'windows-nt)
! "python -u -m pdb"
! "pdb")
"File name for executing the Python debugger.
This should be an executable on your path, or an absolute file name."
:type 'string
_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@xxxxxxx
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
|
|