Re: [Jsonpath] Trailing whitespace (Re: PR regarding selectors ...)

[Stefan Gössner <[e-mail]>]

I am very well aware about meaning of trailing whitespace in Markdown. 
But what is new to me is, that whitespace

* in metadata section (YAML)
* in code section

needs to be avoided too. Ok, now I know.
--
sg


Am 11.06.2021 um 23:04 schrieb Carsten Bormann:
> On 11. Jun 2021, at 07:31, Stefan Gössner <[e-mail] 
> <mailto:[e-mail]>> wrote:
>>
>>>> There also was trailing whitespace.)
>>>
>>> hmm .. . this is important to avoid.
>
> Unfortunately, giving a meaning to trailing whitespace is one of the 
> big blunders that John Gruber made when defining markdown.
>
> Kramdown-rfc plays along, but the whole thing is so error-prone that 
> Martin Thomson created a commit hook that stops you from committing 
> changes that introduce trailing whitespace.
>
> Which maybe is a reasonable thing to do, but it creates an interesting 
> failure situation:
> Somebody manages to sneak in a commit that does create trailing 
> whitespace.
> If somebody tries to edit the document updated with that commit, they 
> can’t commit their changes because the commit hook doesn’t let them 
> commit.
>
> Of course, modern editors have easy ways to get rid of trailing 
> whitespace (M-x delete-trailing-whitespace RET in emacs), but the next 
> committer
> (1) first has to diagnose the problem
> (2) needs to find that command that they may not need too often
> (3) litters their PR with all those whitespace changes because they'd 
> lose the changes in the working copy otherwise.
>
> I don’t know a way to avoid trailing whitespace that doesn’t have that 
> problem, or I would already have suggested that change to Martin.
>
> TL;DR, yes, let’s please avoid committing trailing whitespace.
>
> Grüße, Carsten
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
> 	Virenfrei. www.avg.com 
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>