Tamas Rudnai wrote:
> Anyway, sharing a code here in piclist the problem mostly occurs when
> someone just blindly insert the code as a normal text into the mail
> body. Many of the mail clients just chops off the leading spaces or
> tabs and also the text style is in normal mode which means using a
> proportional typeface font.

Some certainly chop off leading tabs.  Outlook Express appears to do that.
However, I don't think any will chop off leading spaces.  Those are too
often used for legitimate indentation that I can't imagine a client trying
to delete them.

> I do not know what would be the best practice to do but this pastebin
> site is generally not a good idea as it is not getting archived on
> either on the client side nor on any of the piclist's mirrors.

Links to source code you are asking for help with is a bad idea.  Many
people here aren't going to chase down a link, put up with annoying popups,
possible viruses, etc, just to provide free help.  No thanks.

> Maybe an attachment would be sufficient?

That's definitely better than a link, but I'd still rather see the code in
line and properly formatted.  It's difficult to reply in line to a
attachment.  A attachment also makes it too easy for the code to be long.  I
want to see a trimmed down example, preferably a complete but short program
that exhibits the symptom.  Sometimes just the process of producing a
trimmed test case will cause the problem to be found.  This is something
anyone should try before asking 2000 others to look at his problem anyway.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist