somewhat OT ... in parts

[Polytropon]

On Wed, 2 Jan 2013 18:53:05 -0800, Gary Kline wrote:
> 	one reason ive stuck with vim-as-vi was of the colors that vim 
> 	defaults to.  I'v fought the dark/crap/puke brown  /<search>
> 	color that seems to be the default on my linux desktop.  it's hard
> 	to see my block cursor when I search for words.  und`zo, today I 
> 	spend a couple hours tracking down this color feature in vim.  was
> 	pleased to find that there was a blue-tone color set.  my joints
> 	are complaining so I'll ask if any of you can give me the right 
> 	terms to google for.  I'd like to find a lighter blue or play 
> 	around with the colors.  {am assuming that vim is the same across
> 	the linux and berkeley distributions.}

In case you're using gvim (a GUI "enclosing" for vim) you can
do the following: Load some text or source code, :syntax on,
then in the menu: Edit -> Color Scheme, and pin the resulting
menu next to the editor window; click the different schemes
to check if one of the predefined 17 schemes looks usable to
you; when done, unpin the menu. This approach is just for
testing and "looking around" in the first place, not for
actual permanent use. :-)



> 	PS:  OH; the offtopic thing.  I'm done, or =very= close with my
> 	voice by computer program.  It's in C with gtk and AFAICT works
> 	only on linux.  ive got a few months of cleaning up before 
> 	release 0.51 will be finished.  in the FBSD world, this would
> 	fit into the accessibility directory.  now, the speech-impaired
> 	who can type will be able to communicate with anyone.  VBC requires
> 	espeak and gvim.  

There are both gvim and /usr/ports/audio/espeak in ports, and
Gtk is also in there. What would cause this software to refuse
working on FreeBSD?




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...