Can you export with a custom-set line(s) or instance/shortcut name if you use a named instance inside each export that acts as comment lines, lines that are ignored when being loaded in at least EBV if not also spreadsheet programs and web browser for HTML ones?
An .efu starts with
Filename,Size,Date Modified,Date Created,Attributes
"
It could be
#Property testing 1383a
Filename,Size,Date Modified,Date Created,Attributes
"
Or multiple
#Property testing 1383a
#I hope this explains it more clearly, I wrote somewhat of a full page but then removed all but the TL;DR line that is now the first line.
#This does look cleaner and I always have the original in Clipdiary so no loss really.
Filename,Size,Date Modified,Date Created,Attributes
"
Don't know how it would apply to all formats.
Surely every format has their own version of ignored lines?
Export with instance/shortcut/custom line(s) within the export
-
- Posts: 67
- Joined: Tue Oct 08, 2019 6:42 am
Re: Export with instance/shortcut/custom line(s) within the export
EFU files do not support comments.
You could fudge comments by adding trailing headers, eg:
You could fudge comments by adding trailing headers, eg:
Filename,Size,Date Modified,Date Created,Attributes,#my EFU comment
-
- Posts: 67
- Joined: Tue Oct 08, 2019 6:42 am
Re: Export with instance/shortcut/custom line(s) within the export
Do you mean adding it post-export?
I save as efu, json, csv and html for every export.
There is no way to add a comment at export to any of them?
Either way I think I will start naming the instance inside the exported filenames, haven't because descriptions in the filenames can be long and if I also add instance name it can crash AJC Active Backup. Will have to reduce descriptions then.
Re: Export with instance/shortcut/custom line(s) within the export
There's no option to store the instance name as a comment inside the EFU File.
Store the instance name in the filename.
Store the instance name in the filename.