aaptel

`omd.el` was something I made to test the /other/ org-mode GSoC project and has nothing to do with org-sync. You can completely remove it.

I suspect the only way for this ffi to be included in emacs would be to enforce gpl compliance like it's done in emacs when loading modules i.e. checking for...

>Is it acceptable from an FSF perspective to allow a package option to selectively check for this symbol? You have to ask on the emacs-devel mailing list.

Forgot to say, exactly one new email should have been fetched here.

the new email UID is checked in both turbo and non-turbo, but only fetched in non-turbo.

I was googling how to parse ETL files and found this thread. @Zhentar fantastic work!! I've opened an ETL file of mine in 010 with your script and in MessageAnalyzer...

@Zhentar I've noticed that your GUID struct in ETL.bt is only 12 bytes long but GUID are actually 16 bytes long.

Another thing I found out: WMI_HEADER_BUFFER timestamp is the "base" timestamp (in FILETIME format) and all events within (at least for the type EVENT_HEADER) values are offsets to that time....

I wrote a script to extract and convert network traffic from ETL files to PCAP. https://github.com/aaptel/etl2pcap

To anyone looking to parse actual events after getting past the initial basic blocks from @Zhentar description: open the trace in MessageAnalyzer and completely expand the details of the type...