From: Jeff D. <je...@du...> - 2000-06-28 05:31:49
|
Hello Everyone: I have a dumb question. Is there a good FAQ on getting Java up and running on Linux. I just downloaded the Sun 1.3 JDK Beta this morning as an RPM. Once I ran it I couldn't get Java to run. I sure I need to setup something in my .profile or some other config file. I just couldn't find a pointer to the right information. I'm downloading IBM JDK 1.3, so I'll try it. If someone could drop me a pointer what I need to look for I would appreciate it. Sorry, for the off topic posting. Thanks, Jeff |
From: Slava P. <sp...@gj...> - 2000-06-28 07:06:50
|
Jeff Duska wrote: > > Hello Everyone: > > I have a dumb question. Is there a good FAQ on getting Java up and running > on Linux. I just downloaded the Sun 1.3 JDK Beta this morning as an RPM. > Once I ran it I couldn't get Java to run. I sure I need to setup something > in my .profile or some other config file. I just couldn't find a pointer to > the right information. Could you describe the problem in more detail? Slava |
From: Jeff D. <je...@du...> - 2000-06-28 11:47:58
|
Sure after I install Java, I sure I need to setup something like the path statement in DOS/Windows world. I think this needs to go in the some file in my home directory. I'm not sure where this needs to be, plus I cann't seem to figure out where the heck it put the thing! I must say my *nix skill are rustier than I thought. It good thing I'm setting this up get back in practice with bash on Linux and BeOS. I've clearly say in my safe protected Windows controlled world far too long. :) Thanks for the help, Jeff > -----Original Message----- > From: jed...@li... > [mailto:jed...@li...]On Behalf Of Slava > Pestov > Sent: Wednesday, June 28, 2000 3:02 AM > To: jed...@li... > Subject: Re: [ jEdit-devel ] OT: Dumb Questions on jEdit/Java on Linux > > > Jeff Duska wrote: > > > > Hello Everyone: > > > > I have a dumb question. Is there a good FAQ on getting Java up > and running > > on Linux. I just downloaded the Sun 1.3 JDK Beta this morning as an RPM. > > Once I ran it I couldn't get Java to run. I sure I need to > setup something > > in my .profile or some other config file. I just couldn't find > a pointer to > > the right information. > > Could you describe the problem in more detail? > > Slava > > -- > ----------------------------------------------- > jEdit Developers' List > jEd...@li... > http://lists.sourceforge.net/mailman/listinfo/jedit-devel |
From: Slava P. <sp...@gj...> - 2000-06-29 05:08:46
|
Jeff, The command to set the path is: export PATH=$PATH:<directory to add to path> If you want it to be set every time you log in, on RedHat you can create a file in the /etc/profile.d directory, named, say 'java.sh', and place the command there. You will also need to make the file executable: chmod +x /etc/profile.d/java.sh Slava Jeff Duska wrote: > > Sure after I install Java, I sure I need to setup something like the path > statement in DOS/Windows world. I think this needs to go in the some file in > my home directory. I'm not sure where this needs to be, plus I cann't seem > to figure out where the heck it put the thing! I must say my *nix skill are > rustier than I thought. It good thing I'm setting this up get back in > practice with bash on Linux and BeOS. I've clearly say in my safe protected > Windows controlled world far too long. :) > > Thanks for the help, > > Jeff > > > -----Original Message----- > > From: jed...@li... > > [mailto:jed...@li...]On Behalf Of Slava > > Pestov > > Sent: Wednesday, June 28, 2000 3:02 AM > > To: jed...@li... > > Subject: Re: [ jEdit-devel ] OT: Dumb Questions on jEdit/Java on Linux > > > > > > Jeff Duska wrote: > > > > > > Hello Everyone: > > > > > > I have a dumb question. Is there a good FAQ on getting Java up > > and running > > > on Linux. I just downloaded the Sun 1.3 JDK Beta this morning as an RPM. > > > Once I ran it I couldn't get Java to run. I sure I need to > > setup something > > > in my .profile or some other config file. I just couldn't find > > a pointer to > > > the right information. > > > > Could you describe the problem in more detail? > > > > Slava > > > > -- > > ----------------------------------------------- > > jEdit Developers' List > > jEd...@li... > > http://lists.sourceforge.net/mailman/listinfo/jedit-devel > > -- > ----------------------------------------------- > jEdit Developers' List > jEd...@li... > http://lists.sourceforge.net/mailman/listinfo/jedit-devel |
From: Jeff D. <je...@du...> - 2000-06-29 05:34:00
|
Thanks for the info. I just installed Mandrake 7.1, but I setup as a server. I think this was a mistake. It setup the security and the configuration different than I was expecting. I had no rights unless I was root. :( I starting over with the Windows dummy settings, so I can refresh my *inx skills. They are very rusty. :( Thanks, Jeff Duska > -----Original Message----- > From: jed...@li... > [mailto:jed...@li...]On Behalf Of Slava > Pestov > Sent: Thursday, June 29, 2000 1:04 AM > To: jed...@li... > Subject: Re: [ jEdit-devel ] OT: Dumb Questions on jEdit/Java on Linux > > > Jeff, > > The command to set the path is: > > export PATH=$PATH:<directory to add to path> > > If you want it to be set every time you log in, on RedHat you can create > a file in the /etc/profile.d directory, named, say 'java.sh', and place > the command there. You will also need to make the file executable: > > chmod +x /etc/profile.d/java.sh > > Slava > > Jeff Duska wrote: > > > > Sure after I install Java, I sure I need to setup something > like the path > > statement in DOS/Windows world. I think this needs to go in the > some file in > > my home directory. I'm not sure where this needs to be, plus I > cann't seem > > to figure out where the heck it put the thing! I must say my > *nix skill are > > rustier than I thought. It good thing I'm setting this up get back in > > practice with bash on Linux and BeOS. I've clearly say in my > safe protected > > Windows controlled world far too long. :) > > > > Thanks for the help, > > > > Jeff > > > > > -----Original Message----- > > > From: jed...@li... > > > [mailto:jed...@li...]On Behalf Of Slava > > > Pestov > > > Sent: Wednesday, June 28, 2000 3:02 AM > > > To: jed...@li... > > > Subject: Re: [ jEdit-devel ] OT: Dumb Questions on jEdit/Java on Linux > > > > > > > > > Jeff Duska wrote: > > > > > > > > Hello Everyone: > > > > > > > > I have a dumb question. Is there a good FAQ on getting Java up > > > and running > > > > on Linux. I just downloaded the Sun 1.3 JDK Beta this > morning as an RPM. > > > > Once I ran it I couldn't get Java to run. I sure I need to > > > setup something > > > > in my .profile or some other config file. I just couldn't find > > > a pointer to > > > > the right information. > > > > > > Could you describe the problem in more detail? > > > > > > Slava > > > > > > -- > > > ----------------------------------------------- > > > jEdit Developers' List > > > jEd...@li... > > > http://lists.sourceforge.net/mailman/listinfo/jedit-devel > > > > -- > > ----------------------------------------------- > > jEdit Developers' List > > jEd...@li... > > http://lists.sourceforge.net/mailman/listinfo/jedit-devel > > -- > ----------------------------------------------- > jEdit Developers' List > jEd...@li... > http://lists.sourceforge.net/mailman/listinfo/jedit-devel |
From: Slava P. <sp...@gj...> - 2000-06-29 05:54:55
|
Jeff Duska wrote: > > I had no rights unless I was root. :( This is one of the advantages of Linux; when running as an ordinary user, you can't mess up the system. I would not recommend doing all your work as root... Slava |
From: Jeff D. <je...@du...> - 2000-06-29 06:01:50
|
I know. I had it setup a Apache web sever. I did some customizations settings in the setup. I think I screwed them up. It was quick reinstall than do all the chmod to the various directories my user id should have ad access to. I fully understand that you don't want to be root or su. I should be do ls in usr/bin directory where java was. This why couldn't find the java command. At least thats my story and I'm sticking to it. ;) > -----Original Message----- > From: jed...@li... > [mailto:jed...@li...]On Behalf Of Slava > Pestov > Sent: Thursday, June 29, 2000 1:50 AM > To: jed...@li... > Subject: Re: [ jEdit-devel ] OT: Dumb Questions on jEdit/Java on Linux > > > Jeff Duska wrote: > > > > I had no rights unless I was root. :( > > This is one of the advantages of Linux; when running as an ordinary > user, you can't mess up the system. I would not recommend doing all > your work as root... > > Slava > > -- > ----------------------------------------------- > jEdit Developers' List > jEd...@li... > http://lists.sourceforge.net/mailman/listinfo/jedit-devel |
From: Jeff D. <je...@du...> - 2000-06-29 05:57:24
|
I'm having kind of a bummer of night, so I really can't sleep. (Long story about sick cat, drunk and wild women ]:) , a few too many shots of tequila.) Anyhow, I was using jEdit today to do some HTML editing and a few questions came up. I'm not so sure that they are questions as they may be suggestions for the next major release like 3.0 or 2.9. I was wondering why Buffers is was chosen instead of Windows? Why is it in front of the File menu? In the Windows world this is kinda odd. IThis seems like Emacs from Unix. My questions is it possible to create a look and feel that would be more like Windows? You might even call this a jEdit Skin. You might say what the hell is big deal? Well, I have two projects where I think this could cause some confusion. One is KorfeBasic, which is my idea of VB on top of Java VM like jPython. I'd like this to have a VB/VisualStudio mode where is looks and acts almost identical to VB/Visual Studio. I have planned to have jEdit as the editor. As such, it would be nice to customize the look and feel of jEdit without changing the code. The last thing I want is to branch off and miss important bug fixes and ect. The other project is my job that I currently get paid for. I'm writting custom VB application. They need to edit files. Typcially, the users would work with something like Notepad. I suggested that we could include jEdit. The one problem I saw was the unfamilar menus. The plug-in api is the other, because it wouldn't let us create our internal corporate plug-in without be using GPL. Now, I don't want to start the GPL vs BSD debate again. Each side as pluses and each side has minues. Instead I'd like to suggest a compromise that I think would work really well and everyone would be happy. Could we define the Plug-IN API as LGPL? This would be enough for what I want to do. Here if anyone wants to use jEdit they must contribute the code in GPL. If they want to create a commerical add-on they can without using GPL. Current plug-in developers could release plug-ins in GPL, so that they could protect thier work. People like myself that working on projects that will have a hard time with GPL could use the Plug-In API to parts we have problems. In this case, it is the API to CNC machine communication software which the client doesn't own source code. There is no way to go GPL here. But, if I could use jEdit in project as the standard external editor. There would be no issue with me making jEdit bug fixes, patches, new features and etc on company time. ;) Just plug-ins to work with the various third party tools would be commerical. Next, I was wondering on statement completion for modes. How is this progressing? Will it support things like HTML, i.e. pressing "<" key would show list of tags like VB, Delphi, InterDev, or HomeSite 4.5 to name a few? Who created the VBScript syntax mode? I'd like to run some ideas by you about this, KorfeBasic and a few other VB things. Sorry for the long email, but I want to cover these issues while they were fresh or the tequila was still fresh. ;) Jeff |
From: Slava P. <sp...@gj...> - 2000-06-29 06:13:05
|
Jeff Duska wrote: > I was wondering why Buffers is was chosen instead of Windows? Why is it in > front of the File menu? In the Windows world this is kinda odd. IThis seems > like Emacs from Unix. My questions is it possible to create a look and feel > that would be more like Windows? You might even call this a jEdit Skin. Ths can be done already. Just add the following to your jEdit user properties file: buffers.label=Windows view.mbar=file edit search utils macros plugins windows help-menu But 'Windows' is not a very good name, since you are not dealing with actual windows. > The other project is my job that I currently get paid for. I'm writting > custom VB application. They need to edit files. Typcially, the users would > work with something like Notepad. I suggested that we could include jEdit. > The one problem I saw was the unfamilar menus. The plug-in api is the other, > because it wouldn't let us create our internal corporate plug-in without be > using GPL. I think we can add an exception to the license stating that plugins need not be Open Source. > Next, I was wondering on statement completion for modes. How is this > progressing? Will it support things like HTML, i.e. pressing "<" key would > show list of tags like VB, Delphi, InterDev, or HomeSite 4.5 to name a few? This should be done in a future CodeAid release... it doesn't belong in the jEdit core. > Who created the VBScript syntax mode? I'd like to run some ideas by you > about this, KorfeBasic and a few other VB things. Andre Kaplan created it. Slava |
From: mike d. <md...@st...> - 2000-06-29 07:23:01
|
On Thu, 29 Jun 2000, Slava Pestov wrote: > I think we can add an exception to the license stating that plugins need not > be Open Source. here is an example exception that someone suggested for allowing GPL'd programs to explicitly state their licensing position w.r.t. to QPL. As a special exception, you have permission to link this program with the Qt library and distribute executables, as long as you follow the requirements of the GNU GPL in regard to all of the software in the executable aside from Qt. the GUILE exception looks like this: As a special exception, the Free Software Foundation gives permission for additional uses of the text contained in its release of GUILE. The exception is that, if you link the GUILE library with other files to produce an executable, this does not by itself cause the resulting executable to be covered by the GNU General Public License. Your use of that executable is in no way restricted on account of linking the GUILE library code into it. This exception does not however invalidate any other reasons why the executable file might be covered by the GNU General Public License. This exception applies only to the code released by the Free Software Foundation under the name GUILE. If you copy code from other Free Software Foundation releases into a copy of GUILE, as the General Public License permits, the exception does not apply to the code that you add in this way. To avoid misleading anyone as to the status of such modified files, you must delete this exception notice from them. If you write modifications of your own for GUILE, it is your choice whether to permit this exception to apply to your modifications. If you do not wish that, delete this exception notice. our exception could be something like: As a special exception, you have permission to create and distribute plugins written and compiled against jEdit's Plugin API (as well as other accessible public APIs) without the requirement that the resulting code or executable be covered by the GNU General Public License. This exception does not however invalidate any other reasons why the executable file might be covered by the GNU General Public License. If you write modifications of your own for jEdit, it is your choice whether to permit this exception to apply to your modifications. If you do not wish that, delete this exception notice. Note that modifications for which the author declines to maintain this exception will not be considered for reintegration into the main jEdit code base. i'm not sure this is legally sound or that it says exactly what we're looking for, but it's a start. i believe that the GPL with something like this exception will allow proprietary plugins to be released without fear of "viral contamination" from jEdit's use of the GPL. -md |
From: Slava P. <sp...@gj...> - 2000-06-29 09:30:47
|
Mike, I think it would be better if the first paragraph read: As a special exception, you have permission to create and distribute jEdit plugins without the requirement that the resulting code or executable be covered by the GNU General Public License. A "plugin" is defined as a set of classes, optional for jEdit's operation, stored in a JAR file loaded by the "org.gjt.sp.jedit.JARClassLoader" class. Otherwise, someone could just put jEdit code in a non-GPL'd app and have that call our public APIs. My version only applies to genuine plugins. Maybe the reference to the JARClassLoader is too technical; perhaps it should be changed to "[...] loaded from the system or user plugin directory by jEdit's plugin subsystem". Slava mike dillon wrote: > As a special exception, you have permission to create and distribute > plugins written and compiled against jEdit's Plugin API (as well as other > accessible public APIs) without the requirement that the resulting > code or executable be covered by the GNU General Public License. > > This exception does not however invalidate any other reasons why > the executable file might be covered by the GNU General Public License. > > If you write modifications of your own for jEdit, it is your choice > whether to permit this exception to apply to your modifications. > If you do not wish that, delete this exception notice. Note that > modifications for which the author declines to maintain this exception > will not be considered for reintegration into the main jEdit code base. |
From: mike d. <md...@st...> - 2000-06-30 00:33:31
|
On Thu, 29 Jun 2000, Slava Pestov wrote: > I think it would be better if the first paragraph read: > > As a special exception, you have permission to create and distribute > jEdit plugins without the requirement that the resulting code or > executable be covered by the GNU General Public License. A "plugin" > is defined as a set of classes, optional for jEdit's operation, > stored in a JAR file loaded by the "org.gjt.sp.jedit.JARClassLoader" > class. > > Otherwise, someone could just put jEdit code in a non-GPL'd app and > have that call our public APIs. My version only applies to genuine > plugins. sounds good. my original idea was to talk about extending from org.gjt.sp.jedit.EditPlugin, but i wanted to make it clear that it was legal for plugins to user other parts of jEdit as well. your version seems to convey that fine. -md |
From: Andre K. <ak...@vi...> - 2000-07-01 15:12:34
|
Jeff Duska wrote: > I was wondering why Buffers is was chosen instead of Windows? Why is it in > front of the File menu? In the Windows world this is kinda odd. IThis seems > like Emacs from Unix. My questions is it possible to create a look and feel > that would be more like Windows? You might even call this a jEdit Skin. > > You might say what the hell is big deal? Well, I have two projects where I > think this could cause some confusion. One is KorfeBasic, which is my idea > of VB on top of Java VM like jPython. I'd like this to have a > VB/VisualStudio mode where is looks and acts almost identical to VB/Visual > Studio. I have planned to have jEdit as the editor. As such, it would be > nice to customize the look and feel of jEdit without changing the code. The > last thing I want is to branch off and miss important bug fixes and ect. For me, these changes should be scripted. Provided you have a script that dumps all jEdit properties in a BeanShell script, you could customize the jEdit skin to your own needs. Writing such a script is left as an exercise to the reader. It could be used for: - i18n - site deployment - customized keymaps (emacs, vi, etc.) > Next, I was wondering on statement completion for modes. How is this > progressing? Will it support things like HTML, i.e. pressing "<" key would > show list of tags like VB, Delphi, InterDev, or HomeSite 4.5 to name a few? First finish CodeAid. Everything is in CodeAid to do HTML statement completion. > Who created the VBScript syntax mode? I'd like to run some ideas by you > about this, KorfeBasic and a few other VB things. As Slava mentioned, I created the VBScript mode. It was conceived as a part of the asp mode. To create it I used the VBScript 5 reference documentation available at http://msdn.microsoft.com/scripting If you have a VB reference documentation, it would be very easy to write a vb.xml mode Andre |