Tiny Core Linux
Tiny Core Extensions => TCE News => TCE 1.x => Topic started by: Jason W on January 24, 2009, 11:43:51 AM
-
Thanks to dentonlt we now have Vim-7.2:
Title: vim-7.2-bin.tce
Description: vim editor (binaries only) (TESTING)
Version: 7.2
Author: Bram Moolenaar - (Bram _at_ vim.org)
Original-site: www.vim.org
Copying-policy: Proprietary GPL-like (/usr/local/share/vim/vim72/doc/uganda.txt)
Size: 638K
Extension_by: dentonlt (www.dentonlt.com)
Comments: No dependencies. This is just the vim binary.
Help docs and tutorials are in the vim-7.2-docs
extension.
Change-log: First version
Current: 2009/1/23
Title: vim-7.2-bin.tcz
Description: vim editor (binaries only) (TESTING)
Version: 7.2
Author: Bram Moolenaar - (Bram _at_ vim.org)
Original-site: www.vim.org
Copying-policy: Proprietary GPL-like (/usr/local/share/vim/vim72/doc/uganda.txt)
Size: 1014K
Extension_by: dentonlt (www.dentonlt.com)
Comments: No dependencies. This is just the vim binary.
Help docs and tutorials are in the vim-7.2-docs
extension.
Change-log: First version
Current: 2009/1/23
Title: vim-7.2-docs.tce
Description: vim editor (documentation only) (TESTING)
Version: 7.2
Author: Bram Moolenaar - (Bram _at_ vim.org)
Original-site: www.vim.org
Copying-policy: Proprietary GPL-like (/usr/local/share/vim/vim72/doc/uganda.txt)
Size: 8.6M
Extension_by: dentonlt (www.dentonlt.com)
Comments: No dependencies. This is just the vim docs:
help files, tutorials, man pages, syntax files,
translations, and misc. The vim binary
is in the vim-7.2-bin extension.
Change-log: First version
Current: 2009/1/23
Title: vim-7.2-docs.tcz
Description: vim editor (documentation only) (TESTING)
Version: 7.2
Author: Bram Moolenaar - (Bram _at_ vim.org)
Original-site: www.vim.org
Copying-policy: Proprietary GPL-like (/usr/local/share/vim/vim72/doc/uganda.txt)
Size: 8.6M
Extension_by: dentonlt (www.dentonlt.com)
Comments: No dependencies. This is just the vim docs:
help files, tutorials, man pages, syntax files,
translations, and misc. The vim binary
is in the vim-7.2-bin extension.
Change-log: First version
Current: 2009/1/23
-
This works better if you drop .vimrc into your home folder. (adds backspace support,etc, etc)
Here's one by Brian Moolenaar (he should know ;D )
Edit; I commented out line 45-48, since there's no snytax folder included...(which generated errors).
apps/.vimrc][removed due to policy]apps/.vimrc (http://[removed due to policy)
This is a nice addition, since it includes visual mode (great for adding/deleting down columns).
-
I really hate this version....way too much removed. For example, nothing pastes correctly to the clipboard so that you can copy text to anything else. Try this version,which includes .vimrc, the snytax files, spellcheck (:setlocal spell), and even help docs.(type :help <topic>). With this version, when you highlight (e.g, visual mode) something it's ready to paste anywhere.
[removed due to policy]apps/vim_7.1.tce
-
Lack of syntax highlighting takes away a huge part of the application, in my opinion. The first thing I did after downloading compiletc was to install Vim 6.4 in its complete and total everythingness. I don't care about spellcheck, so I neber boygered to uograde to 7.x.
-
I wasn't sure whether 7.1 was compiled by you or me...but when I noticed it had the spellcheck, I figured it must have been mine. I don't know what I did with that bug-free version (the one with 283? fixes ...sure glad Lucky isn't around......
-
I don't care about spellcheck, so I neber boygered to uograde to 7.x.
:)
-
Lack of syntax highlighting takes away a huge part of the application, in my opinion. The first thing I did after downloading compiletc was to install Vim 6.4 in its complete and total everythingness. I don't care about spellcheck, so I neber boygered to uograde to 7.x.
[removed due to policy]apps/vim_syntax.png
-
Oops. I should follow up on this more often.
jpeters/mikshaw - I agree w/ the need for syntax highlighting. I put up the bare-bones extension to give the mini-option. Frankly, I've been using the whole shebang the whole time. Syntax HL is obviously popular - I'll move things around and resubmit. Basic help, too.
JasonW: no offence taken if mine is superceded by jpeters version - he's obviously put some time into it!
-
It would not hurt to have two versions of Vim in the extension area, whether one is a minimal version and the other is a full version or simply just two different version numbers. The same applies to other extensions as well, as we have 4 Mplayers each with a different focus. Why don't we keep this one as a minimal version weighing in at only 600KB and jpeters submit his as the full version at 6MB.
-
I agree with Jason; more variants means more choice for the users. This is hoping that the *info file adequately states what is unique about a given extension, so users don't have to do one-potato-two-potato.
-
Oops. I should follow up on this more often.
jpeters/mikshaw - I agree w/ the need for syntax highlighting. I put up the bare-bones extension to give the mini-option. Frankly, I've been using the whole shebang the whole time. Syntax HL is obviously popular - I'll move things around and resubmit. Basic help, too.
JasonW: no offence taken if mine is superceded by jpeters version - he's obviously put some time into it!
I think it's a fairly simple compile. Actually, default vi works much better then bare-bones, because cut & paste works. I included .vimrc (which goes in $HOME) so it all works immediately...although it's probably best left out so it can be edited. ( or an edited version can be copied from /opt/bootlocal.sh). The newer versions also include GVIM, which many users will prefer.
-
It would not hurt to have two versions of Vim in the extension area, whether one is a minimal version and the other is a full version or simply just two different version numbers. The same applies to other extensions as well, as we have 4 Mplayers each with a different focus. Why don't we keep this one as a minimal version weighing in at only 600KB and jpeters submit his as the full version at 6MB.
OK ...submitted ( I resisted sending gvim to keep down the size a bit )
-
This is hoping that the *info file adequately states what is unique about a given extension, so users don't have to do one-potato-two-potato.
oh yeah, not to trash dsl which i love, but the single most irritating thing for me was that you had 4 things that looked exactly the same- when they occasionally made it very clear which was which, having 4 options was much nicer. i read the entire appendices in the official dsl book, too. that removed some of the mysteries, but there's nothing like an .info file that notes how this version is different from the others. (note: inkscapelite vs. inkscape is very clear.)
-
This is hoping that the *info file adequately states what is unique about a given extension, so users don't have to do one-potato-two-potato.
oh yeah, not to trash dsl which i love, but the single most irritating thing for me was that you had 4 things that looked exactly the same- when they occasionally made it very clear which was which, having 4 options was much nicer. i read the entire appendices in the official dsl book, too. that removed some of the mysteries, but there's nothing like an .info file that notes how this version is different from the others. (note: inkscapelite vs. inkscape is very clear.)
DSL uses almost the same info file as tc.
-
it does, but i believe both have a "notes" line, which is the ideal line to use for clarifying these things. it's up to the person submitting how clear that line is. there are so many familiar faces responsible for tc, perhaps the biggest difference is experience writing .info files.
-
Cool on all that. I've just reviewed the repository, and I'm glad to contribute to the variety. I'm also glad that -somebody- is using this stuff (besides just me).
jpeters: true, though - a mini-vim has few advantages over stock vi ...
I'll play around, see what I can come up with.
off-topic: my hard drive met an unfortunate end yesterday. I've always had plenty of warning, so this was a bit unfortunate. Getting up and running again on another machine will be first task here ...