[MERGE][bzr-email] Implement mail sending using smtplib

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marius Gedminas wrote:
> On Fri, Jan 26, 2007 at 11:23:31AM -0600, John Arbash Meinel wrote:
>> No. It was just a mistake. I have my editor set to show trailing
>> whitespace as well, but apparently:
>> let python_highlight_space_errors = 1
>>
>> Doesn't show whitespace only lines. It only shows when you have trailing
>> whitespace at the end of a real line (and I've seen that it doesn't show
>> trailing whitespace in strings either.
> ...
>> Unfortunately you've now pointed out that my vim setup is incomplete.
>> Vim itself seems a little schizo as to whether a blank line gets
>> whitespace indentation or not.
> 
> I use
> 
>     set list listchars=tab:>-,trail:.
> 
> to see tabs and trailing spaces in vim.  I also have
> 
>     highlight NonText		ctermfg=gray guifg=gray term=standout
> 
> to make trailing spaces less visible so I don't confuse them with spaces.
> 
> I also have
> 
>     match Error /\%>79v.\+/
> 
> in an autocommand for *.py files, to highlight long lines.
> 
> HTH,
> Marius Gedminas

Actually, your last bit gave me the clue as to what I wanted. Just
simply doing:

au BufNewFile,BufRead *.py match Error /\s\+$/

Means that it will mark in red any trailing whitespace. Including
whitespace in strings, on standalone lines, etc.

I don't really like the look of 'set list', and I didn't see what
"highlight NonText" really did.

I also have stuff like:
au BufNewFile,BufRead **/bzr/**/*.py setlocal ts=8 sts=4 sw=4 et ai si tw=79

Which sets things up properly to make sure I don't create tabs, and vim
will autowrap (tw=79) for me. I can see a usefulness to adding your
"match Error /\%>79v.\+/", though.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFuj+FJdeBCYSNAAMRAo2BAKDKetZPJdWRXJQo+O8nanCeJONrewCfbzAh
iwqhrOo77zSt0hPSKYngRXE=
=qrL6
-----END PGP SIGNATURE-----