For using vi, or any app that requires output to the terminal window, include "aterm -e" in the icon's option/shellcommand. (e.g., "aterm -e vi !0! )
Quote
aterm -e vi !0!
Actually you don't need the "vi" Look at the actual Vim icon in the editors folder. The "Link to" field is usually for the link to the actual executeable which is then inserted into the !0! placeholder. Hosting x(a)term or "sudo" is before this placeholder, and runtime options go after the placeholder. Browse around the Apps folder, right click on icon and view options to see how I set this up.
Quote (roberts @ Nov. 02 2007,13:21)
Quote
aterm -e vi !0!
Actually you don't need the "vi"
I was inserting the 'vi' into the commandline for the icon of a file that I wanted to open using the vi editor. I initially thought some of my scripts weren't working from the icon, which require redirecting the output. (vs ROX, which loads without redirecting).Ah a ROX fan. I had created a DSL/ROX prototype. But when it was too big and used to many inodes for my small machines, I abandoned it. So, DSL v4 is my spin of a ROX (rocks) like system. Perhaps I should call DSL v4 the pebbles edition.
Quote (roberts @ Nov. 02 2007,14:13)
So, DSL v4 is my spin of a ROX (rocks) like system.
Looks like a good choice! When it comes right down to it, about 95% of my own routines happen through the terminal window. Maybe there's a fluidity curve here, regarding ease of use and efficiency.
Rocks->Pebbles->Sand->Water Water approaches the ideal of being able to create your own symbols that have the power to have the computer do whatever you want it to. Rocks allow you to use somebody elses symbols to repeat what most people use their computers to do.Next Page...
original here.
