Re: [jed-users] setting programming style

["John E. Davis" <davis@xxxxxxxxxxxxx>]

Paul Shirley <paul.shirley@xxxxxxxxxxxx> wrote:
>The 'jump to error' support would make a good attack target for this 
>(with a few gratuitous syntax errors in source packages)

Compile_Default_Compiler only has an effect on the regular expressions
used when parsing compiler output.  The variables to worry about are
those that determine what programs get run via, e.g., shell_cmd, etc.
For example, XTerm_Pgm in runpgm.sl is one such variable. 

My suggestion is to require variables that specify programs to be run
in a subshell should have names that end in "_Pgm".  That way, the code in
modehook.sl warn the user if a file's mode statement tries to
modify the value of such a variable.

This convention would also require the name changes:

acompile.sl:
   Shell_Default_Shell  ==> Shell_Default_Shell_Pgm
   Shell_Default_Interactive_Shell  ==> Shell_Default_Interactive_Shell_Pgm

docbook.sl
   Sgml_Compile_PS_Cmd  ==> Sgml_Compile_PS_Pgm
   Sgml_Compile_Pdf_Cmd  ==> Sgml_Compile_Pdf_Pgm
   Sgml_Compile_Html_Cmd  ==> Sgml_Compile_Html_Pgm
   Sgml_View_PS_Cmd  ==> Sgml_View_PS_Pgm
   Sgml_View_Pdf_Cmd  ==> Sgml_View_Pdf_Pgm
   Sgml_View_Html_Cmd  ==> Sgml_View_Html_Pgm

Are there any others?

Thanks,
--John

--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.