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
{{ message }}
This repository has been archived by the owner on Aug 12, 2018. It is now read-only.
When working on Windows, I like to use notepad2-mod for quick edits. This is where I just encountered a very weird behavior:
When opening one particular file, notepad2 (current portable x64 release 4.2.25.995) always inserts the current localized time and date, like 19:30 14.07.2017, with line breaks before and after, and moves the caret to the last line. I narrowed it down to the file content starting with .log, and it happens regardless of filename and encoding. I can only assume this is not intended.
The text was updated successfully, but these errors were encountered:
Well, I must correct you. This behaviour IS intended ;-)
You can find it mentioned in the notepad2.txt:
New in Version 2.1.19 (released April 10, 2008)
...
- Original Notepad .LOG feature
...
As you may have guess by now, the MS Notepad had this hidden "feature" since at least WinXP.
Just google for "notepad timestamp" and you may find a bunch of how-tos...
I see. Yet, in Windows Notepad, this only works if the file starts with .LOG (all uppercase). It was quite a surprise to stumble upon this "feature" when opening an SCSS file that contains styles for the .logo 😉
Maybe the casing should be taken into consideration. Anyway, many thanks for the explanation!
When working on Windows, I like to use notepad2-mod for quick edits. This is where I just encountered a very weird behavior:
When opening one particular file, notepad2 (current portable x64 release 4.2.25.995) always inserts the current localized time and date, like
19:30 14.07.2017
, with line breaks before and after, and moves the caret to the last line. I narrowed it down to the file content starting with.log
, and it happens regardless of filename and encoding. I can only assume this is not intended.The text was updated successfully, but these errors were encountered: