Hi,
if I'm writing a new command or whatever with the bundle editor and I did a mistake it could happen that TM crashes immediately after executing what I did. After reopen TM I have the problem that all changes I made within the bundle editor are gone. I realized that TM only saves all changes if I quit TM.
Is this right? And if yes, is there a way to save what I did in the bundle editor explicitly?
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?
Maybe it would be useful to have a button within the bundle editor for saving??
Cheers,
Hans
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.
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
On 2. Nov 2006, at 21:04, thomas Aylott wrote:
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 can make the close gadget indicate status (unsaved changes) -- but I think a save button is the wrong solution (and a step back) -- I can do frequent flushes or so maybe in 2.x when I revamp the bundle editor.
-
Allan Odgaard -
Hans-Joerg Bibiko -
thomas Aylott