Update of sr #111195 (group libtool):

                  Status:                    None => Done
             Open/Closed:                    Open => Closed

    _______________________________________________________

Follow-up Comment #6:

[comment #5 comment #5:]
>> the formatting of libtool.texi for when newlines are used.
> 
> The placement of newlines was intentional: For 1-2 years now, in
> documentation, I use "semantic newlines":
> https://lists.gnu.org/r/help-texinfo/2023-05/msg00006.html
> https://lists.gnu.org/r/help-texinfo/2023-05/msg00007.html
> https://discuss.python.org/t/semantic-line-breaks/13874
> It makes it much easier to understand what has changed in a doc commit, when
> paragraphs are not reflown each time a simple change is made.

Thank you for helping me understand.

Semantic newlines would make diffs much easier to understand, but I want to
make it easier to follow. Inserting newlines where there is not a symbol to
break on is harder for me to follow when reading, so I altered [1] the
documentation for your commit [2] to use partial semantic newlines.

I will see how I feel about it as time passes :)

https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=c41501afc371842ceccecd8bd6586f8fb85a37c2
https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=7e8ae8b3f2cd38a7be0285174103a3a8470eed85
https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=017e1cf9b31e0eca8e60e351ff724c74404b537f


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/support/?111195>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to