Post by Robert on Jun 9, 2023 14:05:04 GMT -5
To simplify the use of the Lines FM command with a block of files, I would like to create an LL.MACRO that inserts the U operand.
However, this is not working. If I directly put LL U on two lines (just plain commands, not using a macro), I get an error message, "No matching line command for: LL". But if I put LL U on one line and just LL on another line, it works.
That means there is no practical way to make a macro for this. I might (with quite some difficulty) try to write a macro to figure out which "LL" was first and which was second, and only add the U for one of them. That would be hard.
What I would like to suggest is that the "matching command" logic only include the command itself, and not any extra operands. That way, you would only use LL for matching purposes, and not the U operand.
===> Some other issues found at the same time:
1. If I issue an L\ command 'near' the top of the FM list, when the list begins with some subdirectory entries, I get an error,
"LINES cannot be used on this type of entry" on each of them. But, if there are non-directory entries, their line counts don't get updated. The "cannot be used" error suppresses everything, even on lines that are not the 'wrong type' in this way.
2. When FM detects a line-command error like the above, it will issue an error but will not clear any of the commands deemed to be in error. It is possible to use a RESET or RES command to get rid of them, but something peculiar happened.
I have assigned a SET value of ALIAS.RE=RESET
I use this a lot because I often reset things, and I like using only two keys.
This works fine in Edit, but in FM, in some conditions this macro will not clear anything, such as the situations described above. It acts like the RE macro wasn't even issued. It seems like there is an issue about when and under what conditions an alias is getting recognized.
However, this is not working. If I directly put LL U on two lines (just plain commands, not using a macro), I get an error message, "No matching line command for: LL". But if I put LL U on one line and just LL on another line, it works.
That means there is no practical way to make a macro for this. I might (with quite some difficulty) try to write a macro to figure out which "LL" was first and which was second, and only add the U for one of them. That would be hard.
What I would like to suggest is that the "matching command" logic only include the command itself, and not any extra operands. That way, you would only use LL for matching purposes, and not the U operand.
===> Some other issues found at the same time:
1. If I issue an L\ command 'near' the top of the FM list, when the list begins with some subdirectory entries, I get an error,
"LINES cannot be used on this type of entry" on each of them. But, if there are non-directory entries, their line counts don't get updated. The "cannot be used" error suppresses everything, even on lines that are not the 'wrong type' in this way.
2. When FM detects a line-command error like the above, it will issue an error but will not clear any of the commands deemed to be in error. It is possible to use a RESET or RES command to get rid of them, but something peculiar happened.
I have assigned a SET value of ALIAS.RE=RESET
I use this a lot because I often reset things, and I like using only two keys.
This works fine in Edit, but in FM, in some conditions this macro will not clear anything, such as the situations described above. It acts like the RE macro wasn't even issued. It seems like there is an issue about when and under what conditions an alias is getting recognized.
