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
I had a look and there weren't any requests for something like this
Hi there, this extension is really really useful for analysing dense hardware crash logs which span multiple files and folders.
There is one small (I know it may be a lot of work) improvement which would make this the perfect extension for reading log files.
If there is a way to add the time stamp for a given log line to the label of a bookmark that would be really helpful.
An example log line
2024-Oct-16 10:06:32.615166: <CoreExec, INFO> CoreConfigClient: Trying to reconnect
If it could auto detect the date and time on the line which is bookmarked and add it next to the Line and column numbers in the bookmarks tab that would be amazing. Picture below indicates where I am referring to.
Thank you again for this amazing extension, it has saved me so much time and makes my job much easier.
The text was updated successfully, but these errors were encountered:
I had a look and there weren't any requests for something like this
Hi there, this extension is really really useful for analysing dense hardware crash logs which span multiple files and folders.
There is one small (I know it may be a lot of work) improvement which would make this the perfect extension for reading log files.
If there is a way to add the time stamp for a given log line to the label of a bookmark that would be really helpful.
An example log line
2024-Oct-16 10:06:32.615166: <CoreExec, INFO> CoreConfigClient: Trying to reconnect
If it could auto detect the date and time on the line which is bookmarked and add it next to the Line and column numbers in the bookmarks tab that would be amazing. Picture below indicates where I am referring to.
Thank you again for this amazing extension, it has saved me so much time and makes my job much easier.
The text was updated successfully, but these errors were encountered: