1. 11 Feb, 2022 11 commits
  2. 10 Feb, 2022 6 commits
  3. 09 Feb, 2022 5 commits
  4. 08 Feb, 2022 8 commits
  5. 07 Feb, 2022 4 commits
  6. 06 Feb, 2022 5 commits
    • Rob Swindell's avatar
      Merge branch 'dd_file_lister_new' into 'master' · 9e8dbe4e
      Rob Swindell authored
      Created a file lister (in JS) that lists files in the user's current file directory
      
      See merge request !135
      9e8dbe4e
    • Eric Oulashin's avatar
      Created a file lister (in JS) that lists files in the user's current file · f3925de4
      Eric Oulashin authored
      directory with a lightbar interface, as well as message windows etc.
      
      If the user does not have an ANSI terminal, this lister will run Synchronet's
      stock file lister interface.
      f3925de4
    • Rob Swindell's avatar
      Clear mouse hot spots (if any) before hanging up. · dbf0a87a
      Rob Swindell authored
      <nelgin> Ah, here's a good one. If I ssh to my bbs server, then ssh to my bbs, do whatever then /O to logout, when I left click in the putty window I get "0;98;20M0;98;20m and stuff like that. I have to run reset to get it working properly.
      dbf0a87a
    • Rob Swindell's avatar
      Update comments only. · 0345e9f9
      Rob Swindell authored
      0345e9f9
    • Rob Swindell's avatar
      Fix access-control by terminal cap issue introduced a week ago · f5fed0b2
      Rob Swindell authored
      In commit 3f17c245, I was addressing the issue reported by Nelgin via IRC:
      <nelgin> If you login using a term that doesn't support ansi, it changes your settings - can you set 'em back when done?
      <DigitalMan> if you have auto-term enabled, it doesn't actually change your settings, just what's in use during that session
      <nelgin> I logged in using my BBC emulator which doesn't do ansi, then when I logged in through syncterm, I got the display like it was on the BBC. All my characters replaced with #'s and stuff.
      <nelgin> I had to go back into the user menu to fix it. That is going to confuse users.
      
      However, the chk_ar() function in userdat.c which is used to populate JS objects (e.g. xtrn_area.sec_list[].prog_list[]) uses the user.misc value (cannot call term_supports()), so the current user terminal flags need to be reflected in user.misc always. So the real fix for the originally reported problem is to clear the charset-related terminal settings when logging in with auto-terminal settings enabled (and before the auto-detected charset flags are OR'd in).
      
      I toyed with the idea of storing a copy of the term_supports() result in client_t, which is passed to chk_ar() when appropriate, but decided that was a bit overkill and there were issues with servers that don't have term_supports (e.g. the web server) and properly populating access-controlled areas in the JS object model (e.g. door games that require ANSI). Better to use the last-auto-detected terminal caps than assuming "no" terminal capabilities in that scenario.
      f5fed0b2
  7. 05 Feb, 2022 1 commit