[Date Prev][Date Next][Thread Prev][Thread Next] [Search] [Date Index] [Thread Index]

Re: [MacPerl] Text editors?



Richard Cook wrote:

> When I set mac perl's EDITOR to TexEdit+
> <http://www.nearside.com/trans-tex/>, I can edit the current script by
> typing com-shift-e, which simply opens a copy in TE+. What I'd like is a
> direct way to ... actually run the script from within TE+. ...
> What editors do people prefer? I'm
> mainly interested in being able to see invisibles, check byte values,
> add/strip comments ... Any suggestions, recommendations?

Me too prefer TOM BENDERS TexEdit Pro; it is a great help to me.
Advantages: Shape Colors; e.g.:
-- (two versions of 1 sub -> 1 dark blue, 1 light blue; )
-- unimportant comments etc.: make them small size and light grey
-- make important keywords bold.
++ in short: Its easyer with all those traffic lights if
          I am no longer color blind!!!

Now how connect to MacPerl?
You have to have an Apple Script as follows
and put it into TexEdit’s script folder;

*****
tell application "TexEdit"
   activate
   copy contents of window 1 to MyScript
end tell

tell application "MacPerl"
   activate
   set MyResult to Do Script MyScript mode Batch
end tell

tell application "TexEdit"
   activate
   copy MyResult to beginning of contents of window 1
   --  actually the previous line should read:
   --          make new window an piut it there, or something like this
end tell
*****

name the script
   perl_it  \F1  (or something like that; in German: rechne \F1),
so you can invoce it by one Keystroke F1
(or  make a construction with help of QuicKeys and use
your favorite keystroke; I use Apple+1 both in MP an TE).

= = = = = =
It is a very great thing to do the connection
   FileMaker <=> AppleScript <=> MacPerl.
For this see
http://bumppo.net/search/macperl.html, search for Lindenthal;
then look for
   FM <=> AS <=> MP.
Chris Nandor (thanks!) answered:

>See MacPerl.Frontend:
>"mode" [MODE] (opt): A mode [MODE], one of Local [LOCL],
>    Batch [BATC],  Remote [RCTL], or Duplex [DPLX].

> - Batch mode redirects standard output and error to the reply apple
>  event. Standard output is put into the direct parameter of the reply,
>  while standard error is put into element [diag] of parameter [OUTP].
>So:
>    do script SKRIPT mode Batch
>should work.  This should have been covered in the book, but wasn't.
> Oh well.  :-)

=========

BUT WHY do I  NOT  use TE <=>MP each and every day?
Because I did not yet manage to redirect the error messages to
a new TE-Window; maybe it is very simple; wonder how the
BBEdit people do this.
Thus: I did use TE<=>MP  when I had very long (>32k),
very difficult MP scripts and when I at the same time
avoided difficult errors and error messages.

-- Ask me, and I will give you my Filemaker Database with many
tiny MacPerl scripts.
 

Detlef Lindenthal <detlef@lindenthal.com>