Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 29, 2015 12:01:51 GMT -5
Is there a way to suppress this message, when I open test.exe ?
"File test.exe is not a multiple of LREC 72, EOL=NONE, the last record will be blank padded"
|
|
|
Post by George on Jun 29, 2015 14:13:58 GMT -5
Jonas: No, there's no way.
1) Why are you opening an EXE file? 2) Even having a good reason to look at an EXE file, why would you specify an LRECL of 72?
As soon as you start using SPFLite as a browser for non-text files, getting messages like this is to be expected.
George
[Update]
Robert, we crossed messages. But you are quite right in everything you said. The message is simply a nuisance, ignore it, after all, you KNOW why it's issued. And definitely use BROWSE, EDIT could destroy the file.
George
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 29, 2015 15:15:34 GMT -5
That is why I placed it under "How can I" and not under "Suggestion". I only wanted to be sure not to overlook something like trying MINLEN=72.
|
|
|
Post by nicc on Jun 30, 2015 5:16:57 GMT -5
Could it be that you are not using a specific exe.ini profile? I did not have one, clicked on a .exe file in FM, got prompted for a .ini file and I chose exe.ini and the file displayed with no messages at all. Had some funny goings on when I typed in PC of COLS though!
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 30, 2015 8:18:14 GMT -5
Thanks Robert. I changed LREC to 64. This is good enough. Jonas
PS: I had 72, because I took it over from SPF/Pro.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 30, 2015 9:18:50 GMT -5
I open spflite.exe. Then I fill "ss"" in the first line, "ss" in the last line. Then I edit one file after the other. Sometimes there are dll-files or exe-files in the list.
Although I do nothing with the exe-file, I prefer a Wrap-Around (simulated with R=Fixed, L=64, EOL=NONE) to the default-ini-format. I works ok with L=64.
|
|
|
Post by George on Jun 30, 2015 10:29:34 GMT -5
Jonas: Robert: Why don't we just use the tools available? The File mask was enhanced long ago to handle complex requests, why not just enter *;-*.exe;-*.dll.
If this is a commonly used item, them just create an FLIST with *;-*.exe;-*.dll in the mask field.
Lets not go re-inventing tools that are already in place.
George
|
|
|
Post by George on Jun 30, 2015 13:22:30 GMT -5
Sorry, I'm going to answer no to this. The existing exemption list is referenced in one place only, this request requires changes to the code in every individual FM line command, and I don't feel this is justified just so someone can say "I'm selecting them all, but I don't really want all of them".
And we all know that next would come the request for "How do I override the do-not-open-list when I REALLY want to open it?"
I know, I'm an old curmudgeon and should be more responsive, but somehow this one really gets to me.
George
[Robert] --> Well, this is clearly not getting anywhere. But, to answer your question, "How do I override the do-not-open-list"? You DON'T. If I have EXE in the do-not-open list, and I really, truly want to open an EXE file, then I take EXE out of the do-not-open list ! That is all there is to it.
Of course, the point was for block FM commands like SS, you're grabbing a whole range, and it's not all that far-fetched to say you might not want every single last one of them that gets included in SS. The nice thing about a do-not-open list is that the undesirable files get filtered out so that SS never even sees them.
That brings up an interesting point. In your current FM processing, you ALREADY support filtering, don't you? What if you had some default filters applied? Would that break everything, or is that just another way of phrasing what you already said no to?
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 30, 2015 15:21:28 GMT -5
That's ok, because I never ask for a change.
|
|
|
Post by George on Jul 1, 2015 10:57:09 GMT -5
We provide filtering for File Path requests right on the FM screen.
We provide filtering in FLISTS uniquely for each individual selection line.
We provide filtering for the FF command in the Options FM dialog.
I think we provide plenty of options to assist in removing unwanted files from the FM display. If someone chooses to not used those options and then uses SS / SS to select all files, and gets files open that they really didn't want, is a simple F3 (End) for those files an enormous burden to live with?
I will always do what I can to make users more productive, but adding new options when the existing ones are not even being used, is simply a non-starter.
George
|
|