You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Andreas Pieber (JIRA)" <ji...@apache.org> on 2011/01/08 08:48:46 UTC

[jira] Updated: (KARAF-359) Add log:stash command

     [ https://issues.apache.org/jira/browse/KARAF-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Pieber updated KARAF-359:
---------------------------------

         Priority: Trivial  (was: Major)
    Fix Version/s:     (was: 2.2.0)

Yes, log:clear does the job (mostly), but the difference to log:stash would be that log:stash affects the -n param of log:display. Limiting it to the number of log-statements between stash and stash clear which can be above the e.g. default 500 line limit.

> Add log:stash command
> ---------------------
>
>                 Key: KARAF-359
>                 URL: https://issues.apache.org/jira/browse/KARAF-359
>             Project: Karaf
>          Issue Type: New Feature
>          Components: console
>            Reporter: Andreas Pieber
>            Priority: Trivial
>
> When I trace down a problem I make extensive use of log:display. Basically it works really great, but sometimes I would wish to see only the log between my latest action and the next log:display
> Something like
> {code}
> log:stash
> // DO ACTION HERE
> log:display (shows all the log happend between the last log:stash and the time I do log:display)
> log:stash clear (remove the marker set by log:stash)
> {code}
> IMHO we could use the syntax of git stash here mostly. Named stashes could be an extension to this feature but I don't think it's required.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.