You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What feature are you missing ? And describe the situation where this
feature will be helpful.
Ability to hide/ignore lines based on keyword highlighting rules.
For example, under the "Configure Keyword Highlight" dialog, an option checkbox
(in addition to Foreground/Background color) to ignore/hide particular lines.
It would be nice to be able to weed out some of the un-useful logging.
(In my particular case, I'm looking at HTML log files, so I'd be able to remove
some of bloat of tablerow/tabledata tags.) (Ideally SnakeTail would include
some type of HTML log viewer, but I realize that would be huge commitment to
implement something like that, so instead I'd just like to request a (simpler?)
feature that is more versatile and functional for more users.)
What version of the product are you using? On what operating system?
SnakeTail Version: 1.8.2
OS: Windows 7 64-bit
Original issue reported on code.google.com by abaines...@gmail.com on 11 Jun 2014 at 4:59
The text was updated successfully, but these errors were encountered:
Are you suggesting some regex-matching where html-tags are stripped from a line?
Or some regex-matching where lines containing certain html-tags are made
invisible?
Original comment by sweaty1 on 11 Jun 2014 at 5:31
I can design the regex-matching if the feature is made part of keyword
highlighting.
But the second option, I'd like to regex-match (user entered via keyword
highlighting dialog) html bloat lines and make them invisible (hide/ignore
them) but also so they do not waste line space (I could currently make them
white text on white background, but that wastes large amounts of screen/text
space).
Original comment by abaines...@gmail.com on 11 Jun 2014 at 8:03
Original issue reported on code.google.com by
abaines...@gmail.com
on 11 Jun 2014 at 4:59The text was updated successfully, but these errors were encountered: