Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Information, which logfile (path) #74

Open
GoogleCodeExporter opened this issue Apr 14, 2015 · 7 comments
Open

Information, which logfile (path) #74

GoogleCodeExporter opened this issue Apr 14, 2015 · 7 comments

Comments

@GoogleCodeExporter
Copy link

If you add logs with same name (maybe access.log) you can't differ, which log 
are on which location.

There is needed a way to see which logifle you view at the moment.

This may be the first line below the tab... and even there could be an 
additional userdefined string for that (optionaly.. if not choose the 
userstring, the path of the file will be shown).


Original issue reported on code.google.com by [email protected] on 9 Jul 2013 at 3:50

@GoogleCodeExporter
Copy link
Author

Hello, Thank You for the request. I had the same problem and therefor added 
tooltip to show the whole file path. I've attached a screenshot. It should be 
available in the actual old version 0.9.8.8...

Original comment by [email protected] on 10 Jul 2013 at 10:51

  • Changed state: Accepted

Attachments:

@GoogleCodeExporter
Copy link
Author

Nope, on Linux there isn't a tooltip.

Original comment by [email protected] on 10 Jul 2013 at 10:53

@GoogleCodeExporter
Copy link
Author

ok, i will check it on linux...

Original comment by [email protected] on 10 Jul 2013 at 11:24

  • Added labels: Component-UI, OpSys-Linux, Type-Defect
  • Removed labels: Type-Enhancement

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 20 Sep 2013 at 5:06

  • Added labels: Milestone-Release1.0

@GoogleCodeExporter
Copy link
Author

Is still not fixed (I've installed Kepler now). Is there something new on this. 
I realy need this.

Original comment by [email protected] on 19 Nov 2013 at 10:47

@GoogleCodeExporter
Copy link
Author

Sorry no news on this, actually i've no spare time to work at this plugin. I've 
scheduled release 1.0 to 09.12.2013 and try to fix it then...

Original comment by [email protected] on 25 Nov 2013 at 11:40

@GoogleCodeExporter
Copy link
Author

great, looking forward to it. Thanks.

Original comment by [email protected] on 25 Nov 2013 at 3:41

@anb0s anb0s added this to the v1.0 milestone Sep 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants