Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Documentation Suggestion for @FULL[] Documentation

Jun
760
16
Rex, I would suggest making explicit in the documentation (and perhaps with an example) that @FULL parses directory aliases (and any other special formats that I don't know about).

echo %@full[dropbox:]
C:\users\jay\dropbox\
 
This isn't specific to @FULL.

@FULL calls the same filename expansion code used everywhere else in TCC, so it gets directory aliases, home directories, shell folders, URLs, etc. I don't know that it would be especially useful to explicitly mention that in several hundred places in the help.
 
This isn't specific to @FULL.

@FULL calls the same filename expansion code used everywhere else in TCC, so it gets directory aliases, home directories, shell folders, URLs, etc. I don't know that it would be especially useful to explicitly mention that in several hundred places in the help.

If that's the case, then it ought to be mentioned in the general discussion of functions, but I did not find anything there.

Moreover, if it would not be especially useful to mention it in the FULL function, why is it mentioned in the similar TRUENAME function, where the following paragraph appears?

@TRUENAME supports directory aliases.

Meanwhile, the FULL function help does say:

The path can include relative path operators like "...\".

Personally, I think that both FULL and TRUENAME should mention both supported features of the path, since those features are probably a significant (if not the main) reason for using those functions. It might be helpful to have cross-references between the two functions and an explanation of how they differ.
 
Back
Top