On Monday, August 3rd, 2026 at 10:08, Aleksandra Fedorova <[email protected]> 
wrote:

> P.S.: Please refrain from going deep into an argument about a specific
> tip or rule (tabs vs spaces, etc).

  This is perhaps the one rule that I am absolutely incapable of
following, for I do not have `set ruler` in my VIM config!

  I'm sure that there is an implicit rule against very bad
top-posting, which I've been called out on.

https://en.wikipedia.org/wiki/Posting_style

  Personally, I don't mind either way, however, if there is an
actual rule to be devised from this, it would be to trim some of
your quoted material, so that you don't end up being sentenced by
the email high guard. :-)

  As you can see, I usually place two spaces at the start of each
paragraph, as well. Although that is a stylistic choice which isn't
enforced in any way, shape, or form. On pure text emails, I believe
it is important to issue a line break before you reach 81 columns.
This is so that those people who still use archaic VT100 terminals,
can read your email, without it looking funny. Although there are
other reasons too, monospace text just looks better, if you have a
column length <81.

  Effective communication on the mailing list, in my opinion,
mostly entails of what's necessary for any effective communication
at all. Clear, terse sentences may come to mind, with a high level
of directness. I believe that where you choose to start a new
paragraph, is also important. There are other various stylistic
word choices, which may help for a communicator to be more precise.


Sent with Proton Mail secure email.
-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to