jed-users mailing list

[2002 Date Index] [2002 Thread Index] [Other years]
[Thread Prev] [Thread Next]      [Date Prev] [Date Next]

Re: 0.99-16 pre-release available


On Wed, 2 Oct 2002 23:58:56 -0400 wrote "John E. Davis" <davis@xxxxxxxxxxxxx>:

> A source-only 0.99-16 pre-release is now available for testing:
>    
>   ftp://space.mit.edu/pub/davis/jed/v0.99/pre-0.99-16.tar.gz
> 
> Please let me know if you find any problems.


CUA-mode is out of date and has some problems:
It doesnot define the _Reserved_Key_Prefix
It doesnot provide a cua.hlp file but sets it as help file.

I wonder, if it could be replaced with my updated version (no objection from
the original author Reuben Thomas).


> Changes since B0.99-15

> 24. lib/comments.sl: Add support for java comments (Nathan Smith
>     <nsmith@xxxxxxxxxxxx>)

When I wrote comments.sl, my main intention was to make it "a tool for mode
designers". Actually, there is no need to change comments.sl to
implement comments in a new mode. Just do

   require("comments");
   set_comment_info (modename, "# ", "", 7);


The intention was to move all comment-string definitions to the
mode-defining files, i.e the lines

   % for some modes we have comment string definitons here
   set_comment_info ("html", "<!-- ", " -->", 0);
   set_comment_info ("sgml", "<!-- ", " -->", 0);
   set_comment_info ("docbook", "<!-- ", " -->", 0);
   ...

  in comments.sl are only there for backward compatibility.
  
  
Thinking about comments.sl, I wondered if there is a chance to get some
redundancy removed:

Comment strings are currently defined twice for each mode:
  
  define_syntax ("#", "", '%', modename);             % Comments
  
and
  
  set_comment_info (modename, "# ", "", 7);

If it were possible, to obtain the comment string(s) set with define_syntax
by a function, we could do without the double definition and gain more
consistency.

Feature wish: a function

  String = get_syntax(Integer type, String modename);
(or
  String, String = get_syntax(Integer type, String modename);
in cases where begin- and end-string are given.

PS:
I plan some extensions to comments.sl:

  boc(), eoc()   % begin/end of comment
  mark_comment   % mark comment as a region
  format_comment % format (wrap) the comment

Is there already some work done in this region (just to spare double work)?


--
G.Milde at physik.tu-dresden.de


[2002 date index] [2002 thread index]
[Thread Prev] [Thread Next]      [Date Prev] [Date Next]