1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • MUTIL and long filenames

    From xqtr@21:1/111 to All on Saturday, October 20, 2018 14:00:28
    In the last two days, i am seeing that mutil is trying to get a file from fsxnet with long file name, which contains spaces and it breaks down the filename to separate words. The filename is something like "How the radio..." and mutil is trying to get file How, then file The and then file Radio etc. Using spaces in filenames is not advisable in any system. I am sure Avon will fix this :)

    .----- --- -- -
    | Another Droid BBS
    : Telnet : andr01d.zapto.org:9999 [UTC 11:00 - 20:00]
    . Contact : xqtr@gmx.com

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Another Droid BBS # andr01d.zapto.org:9999 (21:1/111)
  • From Avon@21:1/101 to xqtr on Sunday, October 21, 2018 22:53:19
    On 10/20/18, xqtr pondered and said...

    In the last two days, i am seeing that mutil is trying to get a file from fsxnet with long file name, which contains spaces and it breaks down the filename to separate words. The filename is something like "How the radio..." and mutil is trying to get file How, then file The and then
    file Radio etc. Using spaces in filenames is not advisable in any
    system. I am sure Avon will fix this :)

    Hmmm thanks Xqtr... I'm just not sure what this file is, I'm guessing it's
    one I hatched? But no bells are ringing... Will do some digging

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From xqtr@21:1/111 to Avon on Saturday, October 20, 2018 15:58:36
    Hmmm thanks Xqtr... I'm just not sure what this file is, I'm guessing
    it's one I hatched? But no bells are ringing... Will do some digging

    My mistake... the file is not from FsxNet :( Sorry... i just wanted to point out, to all of us, to not use long filenames with spaces in it, cause mutil can't handle them. :)

    .----- --- -- -
    | Another Droid BBS
    : Telnet : andr01d.zapto.org:9999 [UTC 11:00 - 20:00]
    . Contact : xqtr@gmx.com

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Another Droid BBS # andr01d.zapto.org:9999 (21:1/111)
  • From nristen@21:1/161 to xqtr on Tuesday, October 23, 2018 09:09:52
    Hmmm thanks Xqtr... I'm just not sure what this file is, I'm guessing it's one I hatched? But no bells are ringing... Will do some digging

    My mistake... the file is not from FsxNet :( Sorry... i just wanted to point out, to all of us, to not use long filenames with spaces in it, cause mutil can't handle them. :)

    I have seen this in the past several times too and again recently on other
    nets than fsxnet. I have wondered if it would be possible somehow to enclose the filename in quotes or something to avoid this problem.

    I also wondered if this is something that is only experienced with those running on the Linux OS.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: The Search BBS (21:1/161)
  • From xqtr@21:1/111 to nristen on Tuesday, October 23, 2018 21:10:24
    I have seen this in the past several times too and again recently on
    other nets than fsxnet. I have wondered if it would be possible somehow to enclose the filename in quotes or something to avoid this problem.

    I also wondered if this is something that is only experienced with those running on the Linux OS.

    I am not sure if this is an OS thing or MUTILs fault. A way to be sure that the file will be handled properly in any OS (modern) is to replace the space char, with underscopes _.

    .----- --- -- -
    | Another Droid BBS
    : Telnet : andr01d.zapto.org:9999 [UTC 11:00 - 20:00]
    . Contact : xqtr@gmx.com

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Another Droid BBS # andr01d.zapto.org:9999 (21:1/111)
  • From Avon@21:1/101 to xqtr on Wednesday, October 24, 2018 12:27:32
    On 10/23/18, xqtr pondered and said...

    that the file will be handled properly in any OS (modern) is to replace the space char, with underscopes _.

    Was just going to suggest the same thing :)

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From bcw142@21:1/145 to nristen on Wednesday, October 24, 2018 06:42:21
    On 10/23/18, nristen said the following...

    My mistake... the file is not from FsxNet :( Sorry... i just wanted t point out, to all of us, to not use long filenames with spaces in it, cause mutil can't handle them. :)

    I have seen this in the past several times too and again recently on
    other nets than fsxnet. I have wondered if it would be possible somehow to enclose the filename in quotes or something to avoid this problem.
    I also wondered if this is something that is only experienced with those running on the Linux OS.

    Linux often needs spaces 'escaped' with backslash '\'. You'll find this in many cases. If there was a file for display called 'ASCII THEME' you'd have
    to call it ASCII\ THEME in some cases and "ASCII\ THEME" in others. I'm never clear which is which, I just try both to see which works. That is true of characters other than space as well like \(ASCII\ THEME\). Any special characters would need that.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)