- not built -

bug 82462, break in scripts that arent loaded yet

messages related to fbreak and fclear commands


git-svn-id: svn://10.0.0.236/trunk@96336 18797224-902f-48f8-a5cc-f745e15eee43

mozilla/extensions/venkman/resources/locale/en-US/venkman.properties

@@ -11,7 +11,7 @@ err.failure        = Unclassified failure.
 msg.err.nostack         = No stack
 msg.err.nosource        = No source for current script
 msg.err.nocommand       = No such command, ``%1$S''
-msg.err.notimeplemented = Sorry, ``%1$S'' has not been implemented
+msg.err.notimplemented  = Sorry, ``%1$S'' has not been implemented
 msg.err.ambigcommand    = Ambiguous command, ``%1$S'', %2$S commands match [%3$S]
 msg.err.bp.noscript     = No scripts loaded for ``%1$S''
 msg.err.bp.noline       = No scripts loaded for ``%1$S'' contain line %2$S
@@ -58,6 +58,7 @@ msg.eval.threw       = Caught exception: %1$S
 msg.hello            = Welcome to ``venkman'', the JavaScript debugger. Visit chrome://venkman/content/tests/testpage.html for a sample debugging target.
 msg.tip.help         = Use ``help <command-name>'' for help on specific commands.
 msg.no.breakpoints.set = No breakpoints set.
+msg.no.fbreaks.set   = No future breakpoints set.
 msg.noproperties     = %1$S has no properties.
 msg.no-commandmatch  = No commands match ``%1$S''.
 msg.commandmatch     = Commands matching ``%1$S'' are %2$S.
@@ -67,8 +68,13 @@ msg.propsd.header    = Properties of %1$S in debugger scope:
 msg.bp.header        = %1$S breakpoints set:
 msg.bp.line          = #%1$S %2$S:%3$S (%4$S scripts match)
 msg.bp.created       = Breakpoint at %1$S:%2$S created (%3$S scripts match)
-msg.bp.disabled      = Breakpoint at %1$S:%2$S disabled (%3$S scripts match)
+msg.bp.disabled      = Breakpoint at %1$S:%2$S deleted (%3$S scripts match)
 msg.bp.exists        = Breakpoint at %1$S:%2$S already set
+msg.fbp.header       = %1$S future breakpoints set:
+msg.fbp.line         = #%1$S %2$S:%3$S
+msg.fbp.created      = Future breakpoint at %1$S:%2$S created
+msg.fbp.disabled     = Future breakpoint at %1$S:%2$S deleted
+msg.fbp.exists       = Future breakpoint at %1$S:%2$S already set
 msg.source.line      = %1$S: %2$S
 
 ## commands ##
@@ -77,7 +83,7 @@ cmd.break.params = [<file-name> <line-number>]
 cmd.break.help   = Set a breakpoint in the file named <file-name> at the line number <line-number>.  <file-name> can be a substring of the actual filename.  If no parameters are specified all active breakpoints will be listed.  See also: clear.
 
 cmd.clear        = clear
-cmd.clear.params = (<index>) | (<file-name> <line-number>)
+cmd.clear.params = <index> | <file-name> <line-number>
 cmd.clear.help   = Clears breakpoint at index <index>, or all breakpoints matching <file-name> and <line-number>.  <file-name> can be a substring of the actual filename.  See also: break.
 
 cmd.commands        = commands
@@ -96,6 +102,14 @@ cmd.evald         = evald
 cmd.evald.params  = <script>
 cmd.evald.help    = Evaluates <script> in the debugger's scope.  See also: eval.
 
+cmd.fbreak        = fbreak
+cmd.fbreak.params = [<file-pattern> <line-number>]
+cmd.fbreak.help    = Sets a ``future'' breakpoint.  Any time a script whose file name matches <file-pattern> is loaded, a breakpoint a <line-number> is set.  Setting a breakpoint at line 1 will cause the debugger to break when the script is loaded.  fbreak with no parameters will list all future breakponts.  See also: break, fclear
+
+cmd.fclear        = fclear
+cmd.fclear.params = <index> | <file-pattern> <line-number>
+cmd.fclear.help   = Clears ``future'' breakpoint at index <index>, or the future breakpoint matching <file-pattern> and <line-number>.  See also: clear, fbreak.
+
 cmd.frame        = frame
 cmd.frame.params = [<frame-number>]
 cmd.frame.help   = Sets the current frame to the one numbered <frame-number>, and displays a summary of the frame.  If <frame-number> is not provided, a summary of the current frame will be displayed.  Use the where command to list available frames and frame numbers.