Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+automation\s+support\s+to\s+track\s+focus\.\s+WAS\:\s+WriteLog\s+12\.23\s+no\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+automation\s+support\s+to\s+track\s+focus\.\s+WAS\:\s+WriteLog\s+12\.23\s+no\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [WriteLog] automation support to track focus. WAS: WriteLog 12.23 no (score: 1): Author: "support@writelog.com" <support@writelog.com>; Date: Wed, 13 Dec 2017 06:50:30 -0800; I apologize for my cryptic comments, but this feature is for those that want to write their own programs to make WriteLog do things it does not already do. Said another way, its like a tool to soup; /archives//html/WriteLog/2017-12/msg00014.html (8,679 bytes)
2. Re: [WriteLog] automation support to track focus. WAS: WriteLog 12.23 no (score: 1): Author: "Tom Georgens" <tomgeorgens15@gmail.com>; Date: Wed, 13 Dec 2017 08:39:20 -0800; As the user of this function I figured that I would give an example of its use case. I have a home brew station controller that automates nearly every aspect of the station ranging from filters to an; /archives//html/WriteLog/2017-12/msg00015.html (12,204 bytes)

Current List: 1 - 2
Page: [1]