enable directory completion for \exec command

[gsalsero]

enable directory completion to allow TAB-ing into subdirectories to find configs.

]\exec c <TAB>
    capt.cfg
    cash.cfg
    cfg-maps/oxodm108a_b2.cfg
    cfg-viewcam/viewcam-ne_duel.cfg
    configs/
    cracky.cfg
    
]\exec co <TAB>
]\exec configs/

]\exec configs/ <TAB>
    cpma/
    osp/
    q3plus/

]\exec configs/o <TAB>
]\exec configs/osp/

]\exec configs/osp/ <TAB>
]\exec configs/osp/all.cfg

[ensiform]

Directory completion works fine already for me, if you want it to fill in the contents on tab with more than 1 result, that is not consistent with the rest of completion code and this introduces a specific behavior only for FS related completion.

Do not enter a slash in dedicated server, unnecessary fwiw.

[gsalsero]

Directory completion works fine already for me, if you want it to fill in the contents on tab with more than 1 result, that is not consistent with the rest of completion code and this introduces a specific behavior only for FS related completion.

Do not enter a slash in dedicated server, unnecessary fwiw.

I haven't been able to get this to work. I tried on Mac/windows/linux dedicated servers and on Mac/windows clients. I created a file baseq3/configs/test.cfg. The contents of that file are simply echo TEST. Then from the dedicated console I type exec co and press tab. The directory name does not complete. Similarly, from the client console I type \exec co and press tab. The directory name does not complete. In both cases, if I manually provide the full path (i.e \exec configs/test.cfg) it does successfully execute it.

I downloaded the latest release for all of them. Curiously though, the dates are different between the OSes. On windows, it reports Oct 26 2024, on linux it reports Nov 11 2024, and on Mac it reports Sep 6 2024

[ensiform]

Are you putting a SPACE after co because if so, that is your issue.

[ensiform]

As for the difference release dates, I think that is due to the fact that runners are borked or the compile date didnt get encoded right? macOS needs new runner images now so it may not have done those.

[gsalsero]

Are you putting a SPACE after co because if so, that is your issue.

no space after co when I TAB.

Here's what I see on the client when I press tab after only typing c

]\exec c
    capt.cfg
    cash.cfg
    cfg-maps/oxodm108a_b2.cfg
    cfg-viewcam/viewcam-ne_duel.cfg
    cracky.cfg

then I type o, press TAB and nothing happens. Just to confirm it can find the test.cfg, I type the rest of the path to test.cfg and press enter.

]\exec configs/test.cfg
execing configs/test.cfg
TEST
]

The TEST output is from test.cfg. That file has one line: echo TEST.

I ran git pull on the master branch just now and rebuilt to make sure I was using the latest code. I am currently at this hash: 3a5601bdae392233e00394d8249d292fb2c3c51d. Still doesn't work for me. I have no idea why it works for you. Plus I tried on 3 different systems and OSes.

[ensiform]

As a test, does it change the behavior in vanilla if the configs are in a pk3 with the desired folder structure for you.