Re: [textadept] Design suggestions

From: mitchell <>
Date: Fri, 24 Jun 2011 12:03:38 -0400 (Eastern Daylight Time)

Hi Anton,

On Thu, 23 Jun 2011, anton wrote:

> Hallo MItchell,
> I have some suggestions about design of run and keys modules.
> I suggest to divide the functionality of run into compiling and
> output, and to
> shift the output part to the corresponding language modules (i.e. cpp/
> init.lua , lua/init.lua and so on) In many cases the user simply wants
> a statusbar notification about successful compilation and a detailed
> error message only in case of error.

This is a good suggestion, but I will instead have the run module emit
events when there is compile or run output. Language specific modules can
connect themselves to those events to display output in the statusbar,

> The second suggestion is about keys.lua. IMHO one needs to shift
> functions
> enclose_in_tag
> any_char_mt
> toggle_setting
> show_recent_file_list
> show_style
> to other places like html/init.lua for enclose_in_tags,

Tags are not just hypertext specific like Robert said. I think it's fine
to keep in keys.lua

> show_recent_file_list to gui.lua.

This is not core functionality. I admit it is strange to have in keys.lua,
but I'm not sure where else to put it.

The other functions you mention are fine to stay in keys.lua I think, but
I'm open to more concrete suggestions.


> I think this will make a clearer design.
> My opinion is highly subjective.
> anton
> --
> You received this message because you are subscribed to the Google Groups "textadept" group.
> To post to this group, send email to
> To unsubscribe from this group, send email to
> For more options, visit this group at

Received on Fri 24 Jun 2011 - 12:03:38 EDT

This archive was generated by hypermail 2.2.0 : Thu 08 Mar 2012 - 12:12:24 EST