#Computer science word vs word vim how to#
#Computer science word vs word vim install#
#Computer science word vs word vim upgrade#
#Computer science word vs word vim plus#

I think it would be cheaper in the long run to help subsidize student computer purchases than suffer with the frustration of not being able to teach students what they need to know, and the cost of the frustration and time that gets lost because we're not able to use the computers that we have.

#Computer science word vs word vim plus#

Plus the students would be much better equipped for life in the outside world.

#Computer science word vs word vim upgrade#

This would save science programs from the problem of having to upgrade and maintain equipment.

#Computer science word vs word vim how to#

They don't have to be frustrated with wondering where programs are and how to select one line of text. vim-startify:link: The fancy start screen for Vim. Underlines the word under the cursor (by itchyny) Vim vim-plugin vim-script.

#Computer science word vs word vim install#

If students have their own computers, they can install software and they can even run programs! Plus they bring a mouse! Or, they can adjust the touch pad their own way and become accustomed to using it. vim-cursorword VS vim-startify Compare vim-cursorword vs vim-startify and see what are their differences. I've decided that the schools who require students to buy laptops have found the best answer to this problem. There isn't money for upgrading the equipment once it's in place and the IT groups are not keen about taking care of equipment that's outside of their control.

The grants cover one-time only purchases. When these programs do get money to purchase computers, it seems to me that the equipment often rots. Biotechnology and other life science programs tend not to have IT budgets, since it already costs too much to buy supplies. Hopefully, we can use it in the next class.Īt the end of the night, I suggested that any students that have laptops would best off bringing their own.Īnd that I think is the lesson from this tale. I forgot to ask for the program that I wanted to use, ahead of time, and the guy who came to install the program wasn't able to access it, unless he logged in as an administrator.

Įven if the computers had worked better, we weren't allowed to do much. This community college has very nice computer labs, but the biotech lab has little laptops that were purchased with a grant and do not work very well. To quote Yogi Berra it was ' dÃ©jÃ vu all over again.' Life might be easier, but every now and then I can't help venturing back into the classroom. But it's harder to escape the past than I thought. Apparently, it was our IT deptartment's policy to only install software on the network, not the computers, and so they only installed one copy for a single user, never mind that I ordered a copy for each computer.Įventually we got that issue resolved, and I decided that computers were so much fun, that I now work in a software company. The students turned them on and tried opened up Excel. Our first problem came when we tried to use the computers. Little I did know, I'd taken on more trouble. Frustrated with this state of affairs, I decided to take matters into my own hands and get computers in the biotech lab. The trouble for me though, was that I would send students off to the computer lab to do assignments, but when they needed help with using a program, like Excel, or Word even, the people in the computer lab couldn't help them. If you can get access to the facilities, using their classrooms can be nice. They can find extra mice and wireless cards, and reprogram keyboards if need be. They can buy new computers on a regular basis and dispose of the old ones. There are certainly advantages in using the school sanctioned computer labs. Our major battle was whether or not we'd be allowed to use Macs. Instructors also had a centralized computer lab, but over the years, we gained the right to have computers in our offices. Like many colleges, we had a few centralized computer labs, tightly controlled by IT (aka the IT nazis), where students were supposed to go to do their computing. (See :help 'packpath' and :help 'runtimepath' for more information on these paths.It's hard to teach bioinformatics when schools work so hard to keep us from using computers.īack in my days as a full-time instructor, I fought many battles with our IT department. If you're writing to the system location because you want the plug-in to be available to all users in your system, you can still use packages, just use the appropriate location, which it seems would be /usr/share/nvim/site/pack in NeoVim ( /usr/share/vim/vimfiles/pack in Vim 8), and same scheme of creating a subdir (any name) and then start/ under it. This would probably fix the plug-in, since it looks like it's failing to find the Python code, most likely because it's expecting to find it at the root of a plug-in directory, rather than somewhere inside a subdirectory of plugin. Then unpack or git clone the plug-in tree there, so you get ~/.vim/pack/Soap/start/vim-ghost-master and then you get the plug-in directories ( autoload, plugin, python3) all there. Simply create a directory ~/.vim/pack/ something/start, where 'something' is literally anything, perhaps use your nickname 'Soap'.

Just use packages to install Vim plug-ins.