Necro-post since this is the appropriate location:

I was thinking it might be neat to be able to execute Grammer programs that are stored in Groups. I'm not sure that it would be useful, though.

Some other features that might be cool:

• Viewing and creating DoorsCS-style folders in Grammer's main menu.
• Archiving/Unarchiving from the main menu.
• Add some useful settings like pretty much all other shells have (enable lowercase, for example).
• Add a simple source viewer in the main menu (not an editor, just something to preview a file).

These aren't ideas that are really necessary, so I might not even add them. Or maybe I need a way to add "hooks" for the main menu so that people can download extensions?

I'd love some feedback, but there aren't many active Grammer users anymore.

Oh, I mean just Grammer's own "hook" system where it calls external routines (in appvars) at various stages of menu rendering. The plan was to have a way for external packages to kind of register with Grammer, with pertinent info stored in Grammer's appvar so that multiple hooks and stuff could be registered. But, that got complicated when I tried it last year

So my intent was a "parser hook" kind of feature. So when Grammer was getting ready to parse a token, it would first pass it through a third-party program in case they would alter parsing. Now I think it might be useful on the main menu during, say, the filtering step (when it is figuring out which programs to display), or for keypresses or something.

The Menu( Command Feature Request

Menu(ᵒx,y,w,"Item 1"[Lbl pointer],"Item 2"[Lbl Pointer],etc...

If that's to hard then add ⁺ to it maybe?

Another Idea:
Menu('x,y,w,[Lbl pointer]*

*The Lbl would have a description, in the form of a String, that tells the menu what the name should be. If there is no description then the name of the label is used.