New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Transformation] Add L/l and c transformations (LEFT/RIGHT, L/R and OPEN/CLOSED) #3094
[Transformation] Add L/l and c transformations (LEFT/RIGHT, L/R and OPEN/CLOSED) #3094
Conversation
any chance of getting this into the mix? Asking for a friend.... :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi,
Removing the "R" formatting command is a breaking change.
I wouldn't approve it.
I added it wrongly in the first commit, initially missed the existing Right-align feature, so I corrected it to L/l. |
I think most of your request have already been implemented (~9 months ago, according to git), so I added 'c' (OPEN/CLOSED) as a non-breaking alternative for 'C'. If you want O/C instead, you could use the 'Ln' justification for example [Plugin#State#c] for OPEN/CLOSED or [Plugin#State#c#L1] to display O/C instead, but that was already possible with the 'C' transformation 😄. |
…ash-check from C justificaion
I understand. |
@giig1967g Does that mean, you now approve of this PR? |
Hi, |
Just a small addition of what seems to be missing but useful.
(Changed form first using R/r to L/l as R is used for right-justify)
Added c for OPEN/CLOSED in addition to C, resolves #2351