On Nov 2, 2006, at 7:28 AM, Allan Odgaard wrote:
On 2. Nov 2006, at 13:03, Hans-Joerg Bibiko wrote:
[...] is there a way to save what I did in the bundle editor explicitly?
Close the bundle editor, that flushes everything to disk.
An other thing is that if change something in a command I have to click at an other command for instance in order to save my changes. Is this also correct?
Yes -- it did previously commit changes in the bundle editor prior to running commands etc., but that functionality was sacrificed in the name of abstraction (in the code base), it will likely be back.
Can you add an explicit Save button too? That way we can be sure that we know what's going on and know that our changes have been applied.
I've just recently moved to doing all of my big command editing as a file and then using the command to call that file. Simply because I can never tell if my changes have been saved and applied.
thomas Aylott — design42 — subtleGradient — CrazyEgg