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

install

  • Clone with SSH
  • Clone with HTTPS
  • Deucе's avatar
    Deucе authored
    Some shell pwd implementations default to the "Logical" PWD, which
    can contain symlinks.  The POSIX standard for /bin/pwd is to return
    the "Physical" PWD with all symlinks resolved.  Some shells don't
    support the -P option the the built-in pwd, so we don't want to
    reply on that.
    
    For some reason, we're redefining the PWD env variable which should
    by the phyical path, but I'm not really interested in tracking down
    all the windy history for this.
    
    Basically, this bit me once, and now it's fixed.
    730d4729
    History
    Name Last commit Last update
    ..