INI tweak for List of Functions

[ivan]

As of right now Help -> List of Functions doesn't do much apart from pasting a list of functions on demand. Now that I'm getting more into scripting, needing to know numbers of functions is very important to me. So I paste the list of those functions into my Notedpad and save it, assign a KS and then reference it that way. Or I just look up the number and then dump the temp text file.

However, doing so renders List of Functions pretty much useless since it's hardly ever accessed again. It also makes a person occupy another KS. Not all is lost though What I think would be great is an INI tweak to allow a user to bind List of Functions to the file where you saved all your functions. Something like this is very nice:

Code: Select all

ListOfFunctions=0
// Set to 0 to copy to clipboard (current), set to 1 to open saved file
ListOfFunctionsFile="PATH"
//PATH represents location somewhere on a computer or WWW

Is something like this possible? Thank you anyway.

[admin]

Not in this century.

[ivan]

Not in this century.

That's a shame, because after using it once and saving that list it becomes practically useless. Oh well, you don't ask you don't get

[sensei]

Not in this century.

shit, that's really a long time :-)

[ivan]

Not in this century.

Actually, it can be this century just not quite how it was initially proposed. Now that you've implemented this:

Code: Select all

v7.70.0004 - 2008-10-21 14:41
    + Scripting got a new function.
      Name:   WriteFile
      Action: Write data to file.
      Syntax: writefile(filename, data, [on_exist], [mode])
        filename: file full path/name;
                  will be created if does not exist yet
        data:     string data to write
        on_exist:
          o:  [default] create new file/if existing: overwrite
          a:  create new file/if existing: append
          n:  create new file/if existing: do nothing
        mode:
          t:  [default] text ASCII (1 byte per char);
              wide chars (upper Unicode) are represented by "?"
          u:  utf16: 2 bytes per char; with LE BOM at file beginning
              LE BOM = Little Endian Byte Order Mark: 0xFFFE
          b:  binary: raw bytes (also 2 bytes per char, but no BOM)
        return: 1 on success, 0 on failure
      Examples:
        ::$a = writefile("C:\Temp\test_A.txt", "text");
          Creates a 4 byte file.
        ::$a = writefile("C:\Temp\test_A2.txt", "text ".chr(20000));
          Creates a 6 byte file.
        ::$a = writefile("C:\Temp\test-U.txt", "text ".chr(20000), ,"u");
          Creates a 14 byte file (2 bytes BOM + 2 * 6).

      Note: WriteFile() is implemented as a function (instead of a
      statement) because the return value will be useful once If/Then
      blocks are implemented. You may, however, call functions without
      using a dummy variable. See here below.

All I need to know is how to dump the list of functions to clipboard and then I can use this:

Code: Select all

writefile ("D:\ListOfFunctions.txt", <clipboard>, o, t)

The question is, however, how to get the contents for LoF?

[Pagat]

Just use #705;
Only downside is, that you'll see the usual two popups when executing the script.

[ivan]

Just use #705;
Only downside is, that you'll see the usual two popups when executing the script.

Ah, many thanks.

Don:
Would it be possible to be able to suppress those 2 pop-up windows if called via a script through a tweak please? I am personally unaware of why people would want to see those windows again and I would have thought they know what the command will do without being told again and again

[admin]

Just use #705;
Only downside is, that you'll see the usual two popups when executing the script.

Ah, many thanks.

Don:
Would it be possible to be able to suppress those 2 pop-up windows if called via a script through a tweak please? I am personally unaware of why people would want to see those windows again and I would have thought they know what the command will do without being told again and again

This is a function that you use not very often. So the popups are (a) useful, and (b) not a big problem if not needed.

[ivan]

This is a function that you use not very often. So the popups are (a) useful, and (b) not a big problem if not needed.

The thought behind it was that if you're calling the function from a script then they won't be useful because you already know what they say and will be mildly irritating (like the pop-up about registering after 30 days every time one wishes to install XYplorer using an installer).