From: Mike M. <ma...@um...> - 2009-01-31 19:13:19
|
When I installed jEdit 4.3pre16 on my Vista PC, I told the install program to start the jEdit server each time I started Windows. This seems to have led to several problems, which Shlomy Reinstein has helped me figure out offline--but he suggested bringing this issue back to the mailing list now. One problem is that having the server running *appears* to prevent me from saving some of the changes in the Appearance portion of the Options menu. Specifically, when both the server and jEdit itself are running, I can click on any of the choices under "Swing look and feel", and click "OK", then restart jEdit, the change has been forgotten--both the menu and jEdit itself have the original L&F. Now I do understand that you have to restart jEdit for look and feel changes to take effect, but my point is that if the server is running, then changes do *not* take effect when I re-start the jEdit program itself. If on the other hand the server is not running, then the changes work fine. Another problem is that the server appears to prevent passwords from being remembered in the FTP plugin across Windows sessions (I'm using this plugin in SFTP mode). That is, although I have checked the "Save Password" box in this dialog, it fails to remember the password if I log out of Windows (or re-boot Windows). The "Save password" toggle does work if the server is not running. Finally, I'd like to say a word or two about the server itself. While there are individual "shortcuts" in the jEdit Start Menu folder for "jEdit", "Quit jEdit Server", and "Start jEdit Server", none of these links appears to be used in the Windows Startup folder; in fact, I never did figure out where the command resides that starts the server at Windows bootup or login. It does not appear to be possible to turn off the server mode except by uninstalling and reinstalling jEdit. I would have preferred to have some other means (probably a check box in the Options menu) to change this. There's a thread on the old jEdit "community" site at http://community.jedit.org/?q=node/view/3505 about this; afaict, the second comment, from Robert Schwenn, is correct--at least about the uninstall/reinstall method, I didn't try the RegEdit method--and the third comment, by dwomack, does not help: using a different command line to start jEdit does *not* prevent the server from starting at Windows login. Also, it would be nice (possibly impractical) to include 'jedit' in the name of the server process. For a long time, I didn't think the jEdit server was running, until Shlomy told me the process was named 'javaw.exe'--I had seen that process, but assumed it was just some generic Java process. As a work-around to these problems, I've un- and re-installed jEdit, telling it not to start up the server. Now jEdit seems to be behaving itself again. I can submit a bug report, but I thought I'd post here first, in case there's something I'm mis-understanding. -- Mike Maxwell ma...@um... When he approached fundamental questions of astrophysics, Eddington did not try first to establish basic laws from which conclusions could be deduced (as Newton had done and as his rival James Jeans insisted on doing), rather he built a web of approximations whose results could be compared with nature. --review by Owen Gingerich of Practical Mystic: Religion, Science, and A.S. Eddington |
From: Shlomy R. <sre...@gm...> - 2009-01-31 19:33:43
|
> One problem is that having the server running *appears* to prevent me > from saving some of the changes in the Appearance portion of the Options > menu. Specifically, when both the server and jEdit itself are running, > I can click on any of the choices under "Swing look and feel", and click > "OK", then restart jEdit, the change has been forgotten--both the menu > and jEdit itself have the original L&F. Now I do understand that you > have to restart jEdit for look and feel changes to take effect, but my > point is that if the server is running, then changes do *not* take > effect when I re-start the jEdit program itself. If on the other hand > the server is not running, then the changes work fine. > I think this should be considered a bug in jEdit, which should be reported in the SourceForge tracker. > Finally, I'd like to say a word or two about the server itself. While > there are individual "shortcuts" in the jEdit Start Menu folder for > "jEdit", "Quit jEdit Server", and "Start jEdit Server", none of these > links appears to be used in the Windows Startup folder; in fact, I never > did figure out where the command resides that starts the server at > Windows bootup or login. It does not appear to be possible to turn off > the server mode except by uninstalling and reinstalling jEdit. I would > have preferred to have some other means (probably a check box in the > Options menu) to change this. There's a thread on the old jEdit > "community" site at http://community.jedit.org/?q=node/view/3505 about > this; afaict, the second comment, from Robert Schwenn, is correct--at > least about the uninstall/reinstall method, I didn't try the RegEdit > method--and the third comment, by dwomack, does not help: using a > different command line to start jEdit does *not* prevent the server from > starting at Windows login. I think that: 1. jEdit should provide some GUI for the user to check the configuration (e.g. to tell if jEdit is using a server or not). Maybe it can be part of the help -> about, which shows the jEdit version and java version. 2. If the shortcuts to start/stop jEdit server do not work, they should be reported as bug in the SourceForge tracker. 3. The fact that the jEdit process shows up as 'java' (or 'javaw') in the Task Manager can really be a problem sometimes. Quite frequently I have several java apps running in my system, and if for some reason one of them hangs, and I need to take it down, I cannot do it just by looking in the Task Manager because all are 'java'. This can be worked-around simply using a jEdit executable that wraps up the java process. I think something similar is done by eclipse - when you run eclipse, it's a java process but you see 'eclipse.exe' in the task manager. I offered Mike to use the freeware tool "process explorer" to check which Java process is the jEdit process, but this is a tiring, redundant effort for such a task. What do others think? Shlomy |
From: Robert S. <Robert@Schwenn-R.de> - 2009-02-01 21:08:02
|
Shlomy Reinstein wrote: > > I think that: > 1. jEdit should provide some GUI for the user to check the > configuration (e.g. to tell if jEdit is using a server or not). Maybe > it can be part of the help -> about, which shows the jEdit version and > java version. > > Shlomy > I filed it as a feature request #2555956 Robert |
From: Robert S. <Robert@Schwenn-R.de> - 2009-02-01 00:32:35
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> <tt>Hi,<br> <br> just want to try to clarify things a bit.<br> <br> In short, You can imagine:<br> 1. the jEdit server as the main application that works *invisible* in the background, and <br> 2. the jEdit views (visible windows) as the clients.<br> <br> This is the normal behavior:<br> - First start of jEdit starts the server.</tt><tt><br> - Further jEdit launches only open new views.<br> - When the last view is closed, the jEdit server is terminated.<br> <br> When jEdit is started with the command line option "<strong class="userinput"><code>-background"</code></strong></tt><tt>, then the server is NOT terminated automatically, when</tt><tt> the last view is closed. Instead, You have to invoke "File -> Exit"!<br> </tt><tt><br> </tt><tt>When jEdit is first started with the command line options "<strong class="userinput"><code>-background"</code></strong></tt><tt> and "<b>-nogui</b>", then only the jEdit server is started and no view is opened. This means that You don't see anything (but splash ?), but jedit *is* running and the activity.log file *is* locked.<br> <br> <strong class="userinput"><code></code></strong>When telling the Windows installer to automatically start the jEdit server at Windows startup, jEdit is started with these two options. Actually, there is no easy way to change the startup behavior, once jedit is installed (except editing the registry). BTW, I can't see a good reason to use this startup option. Of course the first start of a visible </tt><tt>jEdit view is faster, but Windows startup takes more time. And sometimes problems rise that users can't understand.</tt><br> <tt><br> </tt><tt><br> Robert<br> <br> </tt> </body> </html> |
From: Mike M. <ma...@um...> - 2009-02-01 04:20:51
|
Robert Schwenn wrote: > ...I can't see a good reason to use this startup option. Of course > the first start of a visible jEdit view is faster, but Windows > startup takes more time. And sometimes problems rise that users can't > understand. Thanks--I think my take-home message is exactly that: don't install jEdit with the server option. I thought it would be faster at startup (and I probably have enough memory), but you hit the nail on the head: "sometimes problems rise that users can't understand." At least this user. -- Mike Maxwell ma...@um... |
From: Robert S. <Robert@Schwenn-R.de> - 2009-02-01 00:43:10
|
Shlomy Reinstein wrote: > I think that: > 1. jEdit should provide some GUI for the user to check the > configuration (e.g. to tell if jEdit is using a server or not). Maybe > it can be part of the help -> about, which shows the jEdit version and > java version. > Could be difficult because of platform dependence. It's necessary to read the Windows registry for that. > 2. If the shortcuts to start/stop jEdit server do not work, they > should be reported as bug in the SourceForge tracker. > The links do work. But they are not intended to change the automatically startup behavior. An additional link should be added for this. > 3. The fact that the jEdit process shows up as 'java' (or 'javaw') in > the Task Manager can really be a problem sometimes. Quite frequently I > have several java apps running in my system, and if for some reason > one of them hangs, and I need to take it down, I cannot do it just by > looking in the Task Manager because all are 'java'. This can be > worked-around simply using a jEdit executable that wraps up the java > process. I think something similar is done by eclipse - when you run > eclipse, it's a java process but you see 'eclipse.exe' in the task > manager. > I offered Mike to use the freeware tool "process explorer" to check > which Java process is the jEdit process, but this is a tiring, > redundant effort for such a task. What do others think? > > Shlomy > > |
From: Mike M. <ma...@um...> - 2009-02-01 04:25:31
|
Robert Schwenn wrote: > Shlomy Reinstein wrote: > ... >> 2. If the shortcuts to start/stop jEdit server do not work, they >> should be reported as bug in the SourceForge tracker. >> > The links do work. But they are not intended to change the automatically > startup behavior. An additional link should be added for this. It's probably my fault for implying that the link doesn't work to stop the server; I actually never tried it. I wanted something that would prevent the auto-start behavior, and since there are presently no links for that, in the end I un- and re-installed jEdit, this time not choosing the server option. Thanks to all for the help tracking this down! -- Mike Maxwell ma...@um... |
From: Shlomy R. <sre...@gm...> - 2009-02-01 06:49:57
|
On Sun, Feb 1, 2009 at 2:42 AM, Robert Schwenn <Ro...@sc...> wrote: > Shlomy Reinstein wrote: >> I think that: >> 1. jEdit should provide some GUI for the user to check the >> configuration (e.g. to tell if jEdit is using a server or not). Maybe >> it can be part of the help -> about, which shows the jEdit version and >> java version. >> > Could be difficult because of platform dependence. It's necessary to > read the Windows registry for that. > I do not think it's right, because some of the jEdit startup code checks whether it should use a server or not, and acts accordingly. So, there should be a way for jEdit to know whether it's running as a server without looking in the registry. I'll take a look into it later. Shlomy |
From: Robert S. <Robert@Schwenn-R.de> - 2009-02-01 18:17:30
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Shlomy Reinstein wrote: <blockquote cite="mid:fa5...@ma..." type="cite"> <pre wrap="">On Sun, Feb 1, 2009 at 2:42 AM, Robert Schwenn <a class="moz-txt-link-rfc2396E" href="mailto:Ro...@sc..."><Ro...@sc...></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Shlomy Reinstein wrote: </pre> <blockquote type="cite"> <pre wrap="">I think that: 1. jEdit should provide some GUI for the user to check the configuration (e.g. to tell if jEdit is using a server or not). Maybe it can be part of the help -> about, which shows the jEdit version and java version. </pre> </blockquote> <pre wrap="">Could be difficult because of platform dependence. It's necessary to read the Windows registry for that. </pre> </blockquote> <pre wrap=""><!----> I do not think it's right, because some of the jEdit startup code checks whether it should use a server or not, and acts accordingly. So, there should be a way for jEdit to know whether it's running as a server without looking in the registry. I'll take a look into it later. Shlomy <tt> </tt></pre> </blockquote> <tt>Yes, of course jedit knows if it's using a server actually. But jedit can't tell You whether or not Windows will start the invisible jedit server automatically at Windows startup - and this seems to be the critical part for most users to understand.<br> <br> Robert<br> </tt><br> </body> </html> |