From: Ted <r.ted.byers@rogers.com>
To: help-gnu-emacs@gnu.org
Subject: Using Emacs-22.0.50 as programming editor for Perl
Date: Wed, 11 Jun 2008 08:02:39 -0700 (PDT) [thread overview]
Message-ID: <f6d151f9-cc09-4277-8590-ff2625f8c5e4@34g2000hsf.googlegroups.com> (raw)
I've been using Emacs for a while, as well as programming little Perl
scripts for about the same amount of time. So far, so good. But I
have two issues I have yet to resolve, despite studying the Emacs
documentation (maybe I'm just looking in the wrong part of that
though, or maybe what I'm trying to do isn't discussed there).
1) When I run a script, standard output gets mixed with standard error
iostreams. Is there a simple way to tell Emacs to display each output
stream in its own window? At a minimum, things would be a whole lot
easier if whatever is written to STDOUT is kept separate from whatever
is written to STDERR! I would have thought that these two streams
would be written to separate windows by default.
2) Debugging is a bit of a pain. I can use "perl -d myTestScript.pl"
from a Windows (WXP) commandline window. But when I try the usual
commands, that I'd use from the commandline, within Emacs, nothing
happens most of the time, and sometimes I'd get an error message
saying the command I'd used is obsolete. While it is trivially easy
to step through my scripts using "perl -d myTestScript.pl" from a
Windows (WXP) commandline window, I have yet to step through my code
when I have Emacs use the same command to start a debugging session.
Emacs does display the debugger's prompt, but none of the commands I'd
use in the debugger's own interface seems to work when it is trying to
function within Emacs.
Any suggestions to get either of these issues resolved would be
greatly appreciated.
Thanks
Ted
next reply other threads:[~2008-06-11 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 15:02 Ted [this message]
2008-06-11 19:55 ` Using Emacs-22.0.50 as programming editor for Perl David Kastrup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f6d151f9-cc09-4277-8590-ff2625f8c5e4@34g2000hsf.googlegroups.com \
--to=r.ted.byers@rogers.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.