IMO, this capability should be fairly robust.  Here I'm thinking of the 
number of spaces between the leading "#" character and the first "@" 
character.  I would prefer that Leo not be sensitive to whether there are 
exactly two such spaces.  I wonder if there is ever any case where someone 
deliberately inserts a leading space before an "@" character, possibly to 
disable it (instead of, e.g., writing "@@" or "#@").

On Sunday, September 19, 2021 at 8:04:43 AM UTC-4 Edward K. Ream wrote:

> For at least two years Leo has been able to read external files formatted 
> with black <https://black.readthedocs.io/en/stable/>.
>
> Indeed, black will change the format of Leo's sentinel lines, inserting 
> two spaces between the comment delimiter and the `@` that signals the start 
> of a sentinel comment.
>
> Imo, starting with Leo 6.5,  Leo should *write* sentinel comments so that 
> black will not reformat sentinel comments. This change will make it 
> possible to make black the default formatting standard for Leo's own code 
> base.
>
> *Compatibility*
>
> Most Leonistas will hardly notice such a change. However, I have waited 
> until now because ancient versions of Leo will not be able to read external 
> files written by Leo 6.5.  I don't think that matters. Nobody using an old 
> version of Leo is likely to want to read an external file written by Leo 
> 6.5.
>
> *Summary*
>
> Writing black-compatible sentinels will simplify beautifying Leo's own 
> code base. 
>
> Please let me know if you can think of a plausible situation in which 
> writing black-compatible sentinels will cause a problem.
>
> I have just created #2194 
> <https://github.com/leo-editor/leo-editor/issues/2194> for this issue.
>
> 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/34fe4aa8-3bc2-4154-9974-a66b416c7922n%40googlegroups.com.

Reply via email to