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

fseditor.js

Blame
    • deuce's avatar
      c516c6e3
      Go back to the pre-0.75 behaviour of always ending lines with CRLF on output. · c516c6e3
      deuce authored 
      Previously, this was done as Synchronet didn't natively support re-wrapping
to the console screen width (and word_wrap() didn't exist), so fseditor
needed a way to distinguish between "soft" and "hard" CRs when unwrapping.

This is no longer the case, so the space-newline pair for soft CRs is no
longer useful.  Instead, it can now cause an issue where a blank line is
rendered in some terminals when there is a soft CR after a character in the
second-last column.

The space was added for FTS-0001 compatability, but since we will now use
CRLF pairs, this is no longer an issue.
      c516c6e3
      History
      Go back to the pre-0.75 behaviour of always ending lines with CRLF on output.
      deuce authored 
      Previously, this was done as Synchronet didn't natively support re-wrapping
to the console screen width (and word_wrap() didn't exist), so fseditor
needed a way to distinguish between "soft" and "hard" CRs when unwrapping.

This is no longer the case, so the space-newline pair for soft CRs is no
longer useful.  Instead, it can now cause an issue where a blank line is
rendered in some terminals when there is a soft CR after a character in the
second-last column.

The space was added for FTS-0001 compatability, but since we will now use
CRLF pairs, this is no longer an issue.