Skip to content
Snippets Groups Projects
Select Git revision
  • dailybuild_linux-x64
  • dailybuild_win32
  • master default protected
  • 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

scfglib1.c

  • Rob Swindell's avatar
    0b782f45
    Allow JS 'user.editor' and '.shell' to be set for non-users (e.g. user #0) · 0b782f45
    Rob Swindell authored
    The request from Nightfox and Accession via DOVE-Net was to be able to set
    a user's external editor even if there's no user logged-in.
    
    These 2 user class properties in the JS object model were a bit special in
    that they *only* wrote to the user database and did not immediately modify
    the in-memory copy of the user_t structure, depending on the re-reading of
    the user.dat/tab file to re-populate the current user_t structure when needed.
    This didn't work if the current user is user #0 (no user).
    
    So, set the current user_t.xedit and user_t.shell accordingly whenever those
    JS properties are assigned a value (a string, the appropriate internal code).
    0b782f45
    History
    Allow JS 'user.editor' and '.shell' to be set for non-users (e.g. user #0)
    Rob Swindell authored
    The request from Nightfox and Accession via DOVE-Net was to be able to set
    a user's external editor even if there's no user logged-in.
    
    These 2 user class properties in the JS object model were a bit special in
    that they *only* wrote to the user database and did not immediately modify
    the in-memory copy of the user_t structure, depending on the re-reading of
    the user.dat/tab file to re-populate the current user_t structure when needed.
    This didn't work if the current user is user #0 (no user).
    
    So, set the current user_t.xedit and user_t.shell accordingly whenever those
    JS properties are assigned a value (a string, the appropriate internal code).