[Matplotlib-devel] matplotlib limitations and design flaws
Ryan May
rmay31 at gmail.com
Wed Feb 10 12:12:20 EST 2016
A point in favor of not using block comments is that it is *much* harder to
exclude block commented code from greps/regex. If you comment every line,
that makes excluding those lines trivial.
Ryan
On Wed, Feb 10, 2016 at 9:41 AM, Joe Kington <joferkington at gmail.com> wrote:
>
> Ctrl + / should comment out a chunk of text on most editors that I've
>> used (Save for e.g., vim).
>>
>
> And it's pretty trivial to set up in vim (note that you'd tupically
> customize comment marker on a per-language basis through an autocmd
> function). This maps commenting out a block to "-" and uncommenting to "_":
>
> " Clear all comment markers (one rule for all languages)
> map _ :s/^\/\/\\|^--\\|^> \\|^[#"%!;]//<CR>:nohlsearch<CR>
> "Insert comment markers (assumes # unless overridden)
> map - :s/^/#/<CR>:nohlsearch<CR>
>
> There are also smarter options through various plugins, as well.
>
> At any rate, block commenting isn't something I've ever missed or felt was
> a limitation in any way, though that's just my $0.02.
>
> Cheers,
> -Joe
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
--
Ryan May
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160210/d8dc9c38/attachment.html>
More information about the Matplotlib-devel
mailing list