Wondering what the best editor to use to create / edit .prg files. gedit looks OK but isn't xBase aware (not that I can see). Any plugin for it? Any other editor recommendations?
Also how do you associate .prg files with your text editor so that you don't have to go Open with other application| Text Editor
Thanks to anyone who can help
Best Editor to use? Any xBase aware ones? File Associations
- xProgrammer
- Posts: 464
- Joined: Tue May 16, 2006 7:47 am
- Location: Australia
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Doug,
First recommendation is to install gnome-commander which it is very usefull files manager based on Norton Commander (Total commander on Windows).
From a console window do:
sudo apt-get install gnome-commander
Then invoke it:
gnome-commander
simply double click on a PRG file and gedit will be automatically invoked
First recommendation is to install gnome-commander which it is very usefull files manager based on Norton Commander (Total commander on Windows).
From a console window do:
sudo apt-get install gnome-commander
Then invoke it:
gnome-commander
simply double click on a PRG file and gedit will be automatically invoked
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
- xProgrammer
- Posts: 464
- Joined: Tue May 16, 2006 7:47 am
- Location: Australia
Thanks and some feedback
gnome-commander looks good and it solved my problem - but somewhat indirectly. I double clicked on the .prg file and got a similar set of options. However I noticed that the .prg file had permissions of rwx. I removed the x permission and double clicking on the file brings up gedit in both gnome commander and the file browser now.
I tried double clicking on my program to run it but in gnome-commander and got the following error message:
No default application found for the mime-type application/x-executable.
Open the "File types and programs" page in the Control Center to add one.
Sound simple enough but I don't know where the Control Centre is as yet.
Also the terminal session that I launched gnome-commander from gets the following message:
(gnome-commander: 25300) Gtk WARNING **: Ignoring the separator setting
The 2 are presumably related. Anything to do with not having an extension to the filename of the executable? I also cannot launch from the file Browser but launches fine from a terminal (although slight exit problem as reported earlier)
xProgrammer
I tried double clicking on my program to run it but in gnome-commander and got the following error message:
No default application found for the mime-type application/x-executable.
Open the "File types and programs" page in the Control Center to add one.
Sound simple enough but I don't know where the Control Centre is as yet.
Also the terminal session that I launched gnome-commander from gets the following message:
(gnome-commander: 25300) Gtk WARNING **: Ignoring the separator setting
The 2 are presumably related. Anything to do with not having an extension to the filename of the executable? I also cannot launch from the file Browser but launches fine from a terminal (although slight exit problem as reported earlier)
xProgrammer
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Yes, we see what you mean. We can't launch the application from gnome-commander too neither from "Nautilus" (the standard file browser). Lets see if we can find a solutiion.
Its seems its not name related as we use the default extension ".a", the result is the same
>
Also the terminal session that I launched gnome-commander from gets the following message:
(gnome-commander: 25300) Gtk WARNING **: Ignoring the separator setting
>
Thats seems as a gnome-commander specific issue. I don't think its related
Its seems its not name related as we use the default extension ".a", the result is the same
>
Also the terminal session that I launched gnome-commander from gets the following message:
(gnome-commander: 25300) Gtk WARNING **: Ignoring the separator setting
>
Thats seems as a gnome-commander specific issue. I don't think its related