headers
David Reitter | 1 Dec 2006 18:31
Picon
Gravatar

Java and Python debugging

Hi,

can people here recommend technologies for visual source-level  
debugging?

Is JDEE the right thing for Java? The articles I found on Google date  
back to 2001 and older...
Is jdb the latest and greatest?

I need this stuff myself, but I'd also be interested in working  
towards bundling everything that is needed with Aquamacs.

Comments appreciated.

- Dave

--
http://aquamacs.org -- Aquamacs: Emacs on Mac OS X
http://aquamacs.org/donate -- Could we help you? Return the favor and  
support the Aquamacs Project!

---------------------------- Info -----------------------------
List Post: <mailto:macosx-emacs <at> email.esm.psu.edu>
List Archives: <http://dir.gmane.org/gmane.emacs.macintosh.osx>
Permalink | Reply | 1 comment |
headers
David Hunnisett | 1 Dec 2006 19:55
Picon

Re: Java and Python debugging

netbeans ;)
there is a stand alone version of the netbeans debugger. I do wish  
that i could have emacs inside netbeans though
On 1 Dec 2006, at 17:31, David Reitter wrote:

> Hi,
>
> can people here recommend technologies for visual source-level  
> debugging?
>
> Is JDEE the right thing for Java? The articles I found on Google  
> date back to 2001 and older...
> Is jdb the latest and greatest?
>
> I need this stuff myself, but I'd also be interested in working  
> towards bundling everything that is needed with Aquamacs.
>
> Comments appreciated.
>
> - Dave
>
>
>
> --
> http://aquamacs.org -- Aquamacs: Emacs on Mac OS X
> http://aquamacs.org/donate -- Could we help you? Return the favor  
> and support the Aquamacs Project!
>
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Carlton | 1 Dec 2006 22:16
Picon

Re: Command history in the shell buffer

On a related topic, how does one make the shell respond to up-arrow  
and down-arrow the same way as in eshell?
In eshell up and down will show you the command history (just like the  
shell in a Terminal window) but in shell up and down just move the  
cursor up a line. You are forced to use C-p or C-n.

Just wondering why that was chosen for the default.

---------------------------- Info -----------------------------
List Post: <mailto:macosx-emacs <at> email.esm.psu.edu>
List Archives: <http://dir.gmane.org/gmane.emacs.macintosh.osx>
Permalink | Reply | 3 comments |
headers
Ian Eure | 1 Dec 2006 23:26

Re: Command history in the shell buffer

David Carlton wrote:
> On a related topic, how does one make the shell respond to up-arrow
> and down-arrow the same way as in eshell?
> In eshell up and down will show you the command history (just like the
> shell in a Terminal window) but in shell up and down just move the
> cursor up a line. You are forced to use C-p or C-n.
>
You want something like:

(define-key shell-mode-map "[(up)]" 'comint-previous-input)
(define-key shell-mode-map "[(down)]" 'comint-next-input)

I'm not sure if those key symbols are correct or not, so you might need
to tweak that.
> Just wondering why that was chosen for the default.
>
I think it's just because that's the way Emacs has done it for ages.
---------------------------- Info -----------------------------
List Post: <mailto:macosx-emacs <at> email.esm.psu.edu>
List Archives: <http://dir.gmane.org/gmane.emacs.macintosh.osx>
Permalink | Reply | 2 comments |
headers
David Carlton | 1 Dec 2006 23:52
Picon

Re: Command history in the shell buffer

Thanks for all the hints, I'll try them.

On Dec 1, 2006, at 2:26 PM, Ian Eure wrote:

> David Carlton wrote:
>> On a related topic, how does one make the shell respond to up-arrow
>> and down-arrow the same way as in eshell?
>> In eshell up and down will show you the command history (just like  
>> the
>> shell in a Terminal window) but in shell up and down just move the
>> cursor up a line. You are forced to use C-p or C-n.
>>
> You want something like:
>
> (define-key shell-mode-map "[(up)]" 'comint-previous-input)
> (define-key shell-mode-map "[(down)]" 'comint-next-input)
>
> I'm not sure if those key symbols are correct or not, so you might  
> need
> to tweak that.
>> Just wondering why that was chosen for the default.
>>
> I think it's just because that's the way Emacs has done it for ages.

So why does eshell behave differently???
---------------------------- Info -----------------------------
List Post: <mailto:macosx-emacs <at> email.esm.psu.edu>
List Archives: <http://dir.gmane.org/gmane.emacs.macintosh.osx>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ian Eure | 2 Dec 2006 00:00

Re: Command history in the shell buffer

David Carlton wrote:
> Thanks for all the hints, I'll try them.
>
> So why does eshell behave differently???
Because it's a different mode. If you want more shell-like behavior, you
might want to look at term-mode.
---------------------------- Info -----------------------------
List Post: <mailto:macosx-emacs <at> email.esm.psu.edu>
List Archives: <http://dir.gmane.org/gmane.emacs.macintosh.osx>
Permalink | Reply | 0 comments |
headers
Renzo Been | 2 Dec 2006 09:49
Picon

Re: Aquamacs with ProggyFonts?

Hi Marius,

Yes, I have used the ProggyFonts with Aquamacs Emacs. They worked fine
for me. Except when I had to write in German, because the ProggyFonts
do not contain all letters with accents.

In my Preferences.el file the setup for the ProggyFonts would look
something like this:

(custom-set-faces
 '(default ((t (:stipple nil :background "Black" :background-mode dark
:foreground "Green" :inverse-video nil :box nil :strike-through nil
:overline nil :underline nil :slant normal :weight extra-bold :height
180 :width extra-expanded :family "apple-PoggyTinyTTSZ"))))
 '(minibuffer-prompt ((default nil) (nil (:background "black"
:foreground "red"))))
 '(mode-line ((default nil) (nil (:background "black" :foreground "red"))))
 '(mode-line-buffer-id ((default nil) (nil (:background "black"
:foreground "red"))))
 '(mode-line-highlight ((default nil) (nil (:background "black"
:foreground "red"))))
 '(mode-line-inactive ((default (:inherit mode-line)) (((class color)
(min-colors 88) (background dark)) (:background "black" :foreground
"red" :box (:line-width -1 :color "grey40") :weight light)))))
(setq initial-frame-alist '((top . 22) (left . 0) (width . 128) (height . 54)))

Ciao,
Renzo
---------------------------- Info -----------------------------
List Post: <mailto:macosx-emacs <at> email.esm.psu.edu>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Marius Kjeldahl | 2 Dec 2006 10:31
Gravatar

Re: Re: Aquamacs with ProggyFonts?

I see you are using the truetype version, which I guess will be fuzzy at small 
point sizes. Have you or anybody else tried and had any luck using one of the 
bitmap versions?

Thanks,

Marius K.

Renzo Been wrote:
> In my Preferences.el file the setup for the ProggyFonts would look
> something like this:
> 
> (custom-set-faces
> '(default ((t (:stipple nil :background "Black" :background-mode dark
> :foreground "Green" :inverse-video nil :box nil :strike-through nil
> :overline nil :underline nil :slant normal :weight extra-bold :height
> 180 :width extra-expanded :family "apple-PoggyTinyTTSZ"))))
> '(minibuffer-prompt ((default nil) (nil (:background "black"
> :foreground "red"))))

---------------------------- Info -----------------------------
List Post: <mailto:macosx-emacs <at> email.esm.psu.edu>
List Archives: <http://dir.gmane.org/gmane.emacs.macintosh.osx>
Permalink | Reply | 0 comments |
headers
Tony Mannucci | 8 Dec 2006 18:27
Picon
Picon
Favicon

Ipython and Aquamacs

I can't get ipython to work with python-mode.el in Aquamacs OS X Tiger. I have
been able to run it successfully on the X version of emacs that I built
separately. Similarly, it works on a Linux distribution that we have.

The problem occurs with the line indicated below (in .emacs startup file):

(setq load-path (append load-path '("<SOME_PATH>")))
(require 'ipython)   <---- Problem occurs here

The following error is generated:

Debugger entered--Lisp error: (void-variable py-shell-map)
   (define-key py-shell-map (kbd "RET") (quote ipython-send-and-indent))
   eval-buffer(#<buffer  *load*≥ nil "/Library/Application 
Support/Emacs/site-lisp/ipython.el" nil t)  ; Reading at buffer 
position
20680
   load-with-code-conversion("/Library/Application
Support/Emacs/site-lisp/ipython.el" "/Library/Application
Support/Emacs/site-lisp/ipython.el" nil t)
   require(ipython)
   eval((require (quote ipython)))
   eval-expression((require (quote ipython)) nil)
   call-interactively(eval-expression)
   execute-extended-command(nil)
   call-interactively(execute-extended-command)

I placed python-mode.el and ipython.el in
/Library/Application Support/Emacs/site-lisp
as per the ipython instructions for going to python-mode.el. My
(Continue reading)

Permalink | Reply | 1 comment |
headers
David Reitter | 8 Dec 2006 19:32
Picon
Gravatar

Re: Ipython and Aquamacs

Hi Tony

On 8 Dec 2006, at 17:27, Tony Mannucci wrote:

> Debugger entered--Lisp error: (void-variable py-shell-map)
>   (define-key py-shell-map (kbd "RET") (quote ipython-send-and- 
> indent))

chances are that the python-mode that comes with Aquamacs is a newer  
(older, or different) version of the python mode that you're using.  
IIRC, there are several python-modes out there.

> (setq auto-mode-alist (cons '("\\.py$" . python-mode) auto-mode- 
> alist))
> (setq interpreter-mode-alist (cons '("python" . python-mode)
> interpreter-mode-alist))
> (autoload 'python-mode "python-mode" "Python editing mode." t)

leave this out - not needed.

> (require 'ipython)                        ; I added this

OK, since you have your own python-mode, I suggest you simply load  
that python-mode file explicitly before requiring `ipython'. Do this:

(load "...path-to-your/python-mode.el")

before the "require" statement.

Does that help?
(Continue reading)

Permalink | Reply | 0 comments |

Gmane