Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • dailybuild_linux-x64
  • dailybuild_win32
  • sqlite
  • rip_abstraction
  • dailybuild_macos-armv8
  • dd_file_lister_filanem_in_desc_color
  • mode7
  • dd_msg_reader_are_you_there_warning_improvement
  • c23-playing
  • syncterm-1.3
  • syncterm-1.2
  • test-build
  • hide_remote_connection_with_telgate
  • 638-can-t-control-c-during-a-file-search
  • add_body_to_pager_email
  • mingw32-build
  • cryptlib-3.4.7
  • ree/mastermind
  • new_user_dat
  • sbbs320d
  • syncterm-1.6
  • syncterm-1.5
  • syncterm-1.4
  • sbbs320b
  • syncterm-1.3
  • syncterm-1.2
  • syncterm-1.2rc6
  • syncterm-1.2rc5
  • push
  • syncterm-1.2rc4
  • syncterm-1.2rc2
  • syncterm-1.2rc1
  • sbbs319b
  • sbbs318b
  • goodbuild_linux-x64_Sep-01-2020
  • goodbuild_win32_Sep-01-2020
  • goodbuild_linux-x64_Aug-31-2020
  • goodbuild_win32_Aug-31-2020
  • goodbuild_win32_Aug-30-2020
40 results

main.cpp

Blame
    • rswindell's avatar
      f226f1c5
      Reversed the ungetkey() overhaul of Sept-2-2005 (included in v3.13a), this new · f226f1c5
      rswindell authored
      method would insert keys at end of the input ring buffer. This was fine if
      there weren't already chars in the buffer. But if there were already chars in
      the input buffer, ansi_getxy() would then move keys to the end of the input
      buffer until it found the <ESC>[y;xR response it was looking for. This garbled
      the user's input in split-screen chat as reported by JasHud and others.
      If there was a RingBufInsert() routine, we could use that instead, but this
      separate "ungetkey" buf will do for now.
      f226f1c5
      History
      Reversed the ungetkey() overhaul of Sept-2-2005 (included in v3.13a), this new
      rswindell authored
      method would insert keys at end of the input ring buffer. This was fine if
      there weren't already chars in the buffer. But if there were already chars in
      the input buffer, ansi_getxy() would then move keys to the end of the input
      buffer until it found the <ESC>[y;xR response it was looking for. This garbled
      the user's input in split-screen chat as reported by JasHud and others.
      If there was a RingBufInsert() routine, we could use that instead, but this
      separate "ungetkey" buf will do for now.