Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at statalist.org.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: st: How to "format" Statalist posts
From
Nicole Boyle <[email protected]>
To
[email protected]
Subject
Re: st: How to "format" Statalist posts
Date
Mon, 2 Sep 2013 15:10:30 -0700
Perfect... Exactly what I needed. Thanks!
Nicole
On Mon, Sep 2, 2013 at 3:04 PM, Nick Cox <[email protected]> wrote:
> The Statalist advice is that people do pay attention to the content
> and presentation of their posts. That's in their own best interests.
> For example, I recently deleted a post that was so badly presented
> that I doubted that a second reading would make clear what the poster
> had in mind.
>
> But what you refer to seems a product of what mailer you use. Yet I
> notice that you use gmail, at least for Statalist, just as I do. That
> seems to produce reasonable line breaks in continuous prose without
> needing attention. I need to be more careful if presenting code, but
> otherwise I don't think gmail is problematic.
> Nick
> [email protected]
>
>
> On 2 September 2013 21:04, Nicole Boyle <[email protected]> wrote:
>> What is the correct way to "format" plain text posts to Statalist? I
>> notice that Statalist contributors that don't manually insert line
>> breaks (perhaps as demonstrated in this very sentence I'm writing now)
>> have text trailing horizontally into infinity. These posts, IMHO, are
>> not very reader-friendly.
>>
>> However, I've also tried to preemptively circumvent this issue by
>> inserting line breaks (via carriage return), but things often don't
>> work out quite like they should; line breaks occasionally seem to
>> appear in places I didn't put them, thereby introducing a different
>> type of reader-unfriendliness.
>>
>> Here's an example that may (or may not, since I won't know until this
>> is permanently posted) demonstrate this, using the previous paragraph:
>>
>> "However, I've also tried to preemptively circumvent this issue by
>> inserting line breaks via carriage return), <CARRIAGE RETURN>
>> but things often don't work out quite like they should; line breaks
>> occasionally seem to <CARRIAGE RETURN>
>> appear in places I didn't put them, thereby <CARRIAGE RETURN>
>> introducing a different type of reader-unfriendliness."
>>
>>
>> So, any tips on how to better post to Statalist?
>>
>> Thanks,
>> Nicole
>> *
>> * For searches and help try:
>> * http://www.stata.com/help.cgi?search
>> * http://www.stata.com/support/faqs/resources/statalist-faq/
>> * http://www.ats.ucla.edu/stat/stata/
> *
> * For searches and help try:
> * http://www.stata.com/help.cgi?search
> * http://www.stata.com/support/faqs/resources/statalist-faq/
> * http://www.ats.ucla.edu/stat/stata/
*
* For searches and help try:
* http://www.stata.com/help.cgi?search
* http://www.stata.com/support/faqs/resources/statalist-faq/
* http://www.ats.ucla.edu/stat/stata/