Bugs item #1083602, was opened at 2004-12-11 21:08
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=581349&aid=1083602&group_id=86916
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Ben Bob (bpeng2000)
Assigned to: Nobody/Anonymous (nobody)
Summary: Dislike "working on region in file ...."
Initial Comment:
These messages are totally meaningless. Why cannot it
be the code actually being executed? I have modified
python-mode.el
==> insert the following line
(setq text-to-be-executed (concat
(mapconcat 'identity (split-string
(buffer-string) "\n") "\n... " )
"\n")
)
===> before this. (line 1700?)
(write-region (point-min) (point-max) file nil
'nomsg))
(if (not py-file-queue)
(py-execute-file proc file)
===> and change
(msg (format "## working on region in file
%s...\n" filename))
===> to (line 1303?)
(msg text-to-be-executed)
so that when I execute a region
a=5
print a
I get in python buffer
>>> a=5
... print a
5
>>>
As a matter of fact, S-mode (for R or S-plus),
matlab-mode all work in
this way and I see no reason why we should tolerate
"working on region
in ..." any more.
Bo
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=581349&aid=1083602&group_id=86916
_______________________________________________
Python-mode mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/python-mode
