Custom Query (31 matches)

A Save key or menu command should execute a Save (as expected), not a SmartSave. SmartSave would only save a file if it was changed. The original Save always saves a file.

This was suggested by John Small.

I don't like the idea to support the SMARTSAVE constant any further, because the key def file is already much too complicated. It provides much more options then the original. The additional complexity affords that we should really try to reduce the number of constants to zero.

BTW: SMARTSAVE only applies on the key def, not on the menu items. Of course, they should be synchronous.

Configuration of these tools isn't possible:

o md5 o grep o comparison tool: kdiff3 o comparison tool: gfc o recode o browser o ftp app o email app

First idea was to make config available via epm.env. That was dropped, because it allows no detailed config, like menu item texts or menu item help texts (e.g. for the comparison tools).

Next idea is to create an additional .cfg file.

Esp. the mark commands do unexpected actions if nothing is marked. Additionally, not all commands exist yet.

Moreover, the key assignments for these actions should be reworked. The changes have to be implemented in newmenu and in the popup menu.