DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Designing AI for Long-Running Tasks: Looking Beyond More Context
  • How Long-Running ECS Tasks Survive Rolling Deployments Without Duplicating Output
  • MCP for Enterprise Tasks: Making the Rare Frequent Enough to Master
  • Idempotent Output Keying for Long-Running Tasks During Rolling Deployments

Trending

  • Google Cloud KMS vs. AWS KMS: Java Encryption Guide
  • Apache Phoenix: Global Secondary Indexes With Tunable Consistency
  • MQTT, Kafka, NATS, or Zenoh? Choosing Edge-to-Cloud Messaging by Traffic Pattern
  • A Field Guide to AI Agent Frameworks

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

Tip: Using Notepad++ to Read Log Files

I had to read a log file containing a few hundred lines today at work. My first instinct was to open it using my trusty Notepad++.

By 
Dror Helper
·
Jun. 13, 13 · Tutorial
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
68.0K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

I had to read a log file containing a few hundred lines today at work.

My first instinct was to open it using my trusty Notepad++. While the file was not huge it was still difficult to traverse it and my eyes kept jumping between lines. Finding the  errors and warning was proving to be a hard task.

Since each line started with the severity of the message (trace/debug/info/warning/error) all I was missing was basic text highlighting – now where can I find such a tool :)

image

I’ve set out for work - the only question being – how hard would it be (spoiler: easy).

Step 1 – under Language choose Define your language

image

A new dialog will be opened. If you prefer you can dock it to the screen.

Choose Keywords tab

image

Define new keywords for Error, Warning  and any other severity you wish to highlight.

Choose the Styler button and set custom background (or foreground) for each severity.

image

And finally use Save as and name your new “language” – and a new language is born.

image

This is what the log looks like now – easy to read and spot the errors. I only wish I could have marked the whole line but at least now I can tell where the errors are.

image

Not too bad for less than one minute of work.

Dialog (software) Task (computing)

Published at DZone with permission of Dror Helper. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Designing AI for Long-Running Tasks: Looking Beyond More Context
  • How Long-Running ECS Tasks Survive Rolling Deployments Without Duplicating Output
  • MCP for Enterprise Tasks: Making the Rare Frequent Enough to Master
  • Idempotent Output Keying for Long-Running Tasks During Rolling Deployments

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook