[Main page]
Page last modified: 11 Dec 97

Let us know your problems by using the form in the download page or sending E-Mail to us.


Please note that the buttonset that is provided in the package is intended mostly as an example. We tried to use as common commands as possible, but someone is bound to not to have a particular command. See the first item.

Table of Contents

  1. When I click a button I get an error "couldn't execute 'xxx': no such file or directory"
  2. When I click the predefined Mail-button I get an error.
  3. When I use the predefined Locate-button, X-Files sometimes locks up.
  4. I get all the time error messages that my version of the executed Unix-command does not support the flag it uses (E.g. cp, rm etc).
  5. After getting an error, I sometimes get immediately an error can't read "env(XF_HOME)": no such element in array.
  6. I have made magnificent changes to a button and suddenly they are no more.
  7. I changed the binding to an extension and now the application will not launch with the file I clicked on.
  8. When I try to launch X-Files, I get application-specific initialization failed: error getting working directory name: permission denied
  9. The Afterstep window manager kills my X-Window session when I try to restart X-Files after editing the resources.
  10. There are sometimes weird characters in an entry-widget.
  11. Hotkeys
  12. Activating the menus with accelerator-keys
  13. X-Files and Solaris
  14. X-Files and wish8.0
  15. Sometimes X-Files hangs
  1. When I click a button I get an error "couldn't execute 'xxx': no such file or directory"
    The program binded to that button either is not in your PATH or does not exist at all. Use the Button Editor to fix the problem either by adding the full path to the command or changing it to another.

  2. When I click the predefined Mail-button I get an error.
    The button is so binded that it mails the selected file(s). Either select a file first or use the Button Editor to change the command.

  3. When I use the predefined Locate-button, X-Files sometimes locks up.
    If the locate does not find anything, it results in error and causes this.
    Oh, by the way, do not use wildcards in locate command, locate searches literals...
    SOLUTION: Use X-Files version 1.40 or higher and set the Quiet-option on for that command.

  4. I get all the time error messages that my version of the executed Unix-command does not support the flag it uses (E.g. cp, rm etc).
    Upgrade to version 1.21 or higher and edit the command in the file ~/.x-files/xfiles.commands_??? The ??? will be your HOSTTYPE, this way the commands can be distinguished when run on different platforms that share the same harddisk.

  5. After getting an error, I sometimes get immediately an error can't read "env(XF_HOME)": no such element in array.
    This one puzzles us. If you could be so kind and mail us a more thorough explanation. This kind of error should not be possible :)
    However, in version 1.30 we have tried another approach, hopefully that will fix this.

  6. I have made magnificent changes to a button and suddenly they are no more.
    It could be one of several reasons.
    Do not change the button under editing unless you have applied/saved the changes.
    In versions prior 1.21, if you have applied the changes and then close the Button Editor, you do not get a reminder of unsaved changes.
    You have edited the buttons-configuration file by hand and have messed up the indices.

    NOTE!! Remember that when editing buttons, you do not necessarily have to save the changes separately for every button. You can edit several buttons, applying each one separately and save all the changes together.


  7. I changed the binding to an extension and now the application will not launch with the file I clicked on.
    You left out the operator %f from the command. The file(s) will be in that place when executing the command.

  8. When I try to launch X-Files, I get application-specific initialization failed: error getting working directory name: permission denied
    This is a limitation in the wish. You do not have the proper permissions (read & execute) for that directory or its parent directories.

  9. The Afterstep window manager kills my X-Window session when I try to restart X-Files after editing the resources.
    This is a bug in the window manager.

  10. There are sometimes weird characters in an entry-widget. I cannot delete them but they disappeared after scrolling the text in the entry.
    This is a bug in the wish4.1 (at least in some platforms). We have made a temporary fix for this but cannot guarantee it works on every platform.

  11. Hotkeys
    If the hotkeys behave strangely, make sure you do not have previous bindings for them in your window manager.

  12. Activating the menus with accelerator-keys
    Version 4.2 of wish seems to have a bug with this. It is fixed with the latest patchlevel (4.2p2).

  13. X-Files and Solaris
    On Solaris, when starting X-Files you get an error about "(block / 2)", you must go to the directory ~/.x-files/ and edit the file xfiles.commands???. There change the line that says
    set xf(DISKFREE) {df}
    to
    set xf(DISKFREE) {df -k}

  14. X-Files and wish8.0
    X-Files and wish8.0 are not entirely compatible, yet. Problems occur at least with the pop-up menu and the width of the listings. We plan to make X-Files v2.0 with Tcl/Tk 8.0, so please be patient. (X-Files v2.0 is the next major release after v1.40 and it has also FTP-support!)

  15. Sometimes X-Files hangs
    Sometimes, after clicking an ActionButton or trying to execute extension binding, X-Files freezes totally. This happens if the program you are trying to run requires some input from you. Since we do not have any input stream to that process, it waits forever. X-Files v2.00 will have improved handling for this kind of situations.

Known bugs

[Main page]