On Sat, Nov 25, 2023 at 7:58 PM Thomas Passin <[email protected]> wrote:
My main reaction is to make sure that Leo's read behavior remains backwards > compatible with the pre-black sentinel format. People with much older > outlines should be able to open them for the indefinite future. All recent versions of Leo can read legacy and blackened sentinels. It's also possible that there is some user code that does something with > sentinels and assumes there will be no space after the leading '#' > character. So perhaps the *--black-sentinels** command line option* > should remain in reverse: *--black-sentinels**=False * would be allowed > but not be the default . The usual convention would be to create a --no-black-sentinels option. However, I see no need for this option. The --black-sentinels options could have broken existing code, but nobody has complained. *Summary* - There is no need to retain --black-sentinels. - There is no need for --no-black-sentinels. - The only likely downsides are the initial diffs. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS3O5ucZVE2Vrfr92bPmrn--CLjU6mg1A8q8%2BzJrmYNyVA%40mail.gmail.com.
