Hi Amit Agarwal,
I've already admitted that I was badly mistaken about the "do while ..".
1) your presentation: still indentation is missing
2) What is the real goal? What do we want?
1) Your presentation:
That you present a big "box" showing the (no longer formatted code)
will cause trouble. Even though the box is "huge" now formatting is
still gone. There is no way sending patches this way.
If I see code which is not indented I instantly think that you don't
care about your code (so I start looking for more issues).
So rather then doing your own thing use a service such as github which
will allow users to comment your code, fork and send patches or use an issue
tracker.
Reading like this turns me off because missing indentation is always causing
much more work to understand it.
download_list()
{
downloaded=1
if [ ! -f $tmp_file ]
then
wget -O $tmp_file
'http://www.vim.org/scripts/script_search_results.php?&show_me=4000&result_ptr=0'
-o /dev/null
else
echo "using the existing $tmp_file"
fi
}
And thats the first impression a visitor gets. So use <pre> </pre> or such
rather than whatever you did or use github, gitorious, or any of the other
public code hosting services.
2) What is the real goal? What do we want?
What's most important to know?
Can you describe briefly what your script does what you didn't find on
vim.sf.net?
Eg why do you prefer your script over using the home page (vim.sf.net)?
I'm asking because your script identifies flaws of the homepage we should fix.
You should not have to parse HTML in order to get the info. We should create an
API. (PyPi, RubyGems, .. they all have it. Only Vim is still xx years old in
this regard). We should move forward or people will choose other tools.
Also I'd like to work towards having one Vim plugin handling all the
needs of todays users about script querying and installation.
vim-addon-manager is the result of my last attempt and I think it gets
the job done much better than anything which was available before ti.
It still is very weak: You have to browse vim.sf.net to find out which plugins
to install and I'm pretty sure there are more issues.
Would you be interested integrating your ideas into VAM
(or a similar plugin) so that it also runs on Windows and that more
users will have access to it naturally?
Instead of parsing HTML it should be based on a specific API call such as
vim.sf.net/api.php?query-all-scripts-matching-word=XY
or the like. The result could be json which can be prased by Vim:
https://github.com/MarcWeber/vim-addon-json-encoding
Then Vim buffers and highlighting could be used to present the query result to
users?
Please talk about what made you write your script - so thaw can slowly
improve the overall situation for all users.
I mean vim.sf.net having pages talking about Vim 5 (About Vim -> "for
vim 5 users"). This shows that its partially updated maybe no longer fitting
the needs of todays users. If that's the case we should collect thoughts and
improve the situation.
If you need help with github or the like you can contact me anytime (I'm also
on irc very often).
Blogs are nice - but they are bad at hosting code. They should be used to talk
about code referring to code hosted somewhere else.
Marc Weber
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
