From: Grzegorz R. <gru...@po...> - 2003-05-15 09:25:41
|
Hello All J Users, Okey, I've just downloaded J and it seems exact _The_ Editor which I need. But I've a problem with the email feature. I've edited profs file as in documentation and restarted J. But I still don't see Mailbox Mode. Any Ideas how to gget it work ??? -- G.R.Z.E.C.H.U.: General Robotic Zombie Engineered for Calculation and Hazardous Utility http://republika.pl/grumatow/netykieta.html ***apcoh member #49 |
From: Ludovico M. <lu...@as...> - 2003-05-15 09:43:42
|
J is a wonderful editor, and I'm using it more and more as my default editor for python and php programming. I wonder if anybody has thought of using jython inside of j to enhance python-related functions, such as code completion, etc. Ludo |
From: Peter G. <pe...@ar...> - 2003-05-15 12:58:16
|
> But I've a problem with the email feature. I've edited profs file as in > documentation and restarted J. But I still don't see Mailbox Mode. Any > Ideas how to gget it work ??? You need to add lines similar to these to ~/.j/prefs (or C:\.j\prefs): enableExperimentalFeatures = true enableMail = true userFullName = Peter Graves userMailAddress = pe...@ar... inbox = {annie}inbox smtp = smtp.west.cox.net confirmSend = true Then you should be able to do Alt X, "inbox" (or Ctrl O, "inbox") and open your inbox. (You should also see the Inbox button appear on your toolbar, if you have the toolbar enabled.) The inbox line in the example above is for IMAP; if you use POP, your inbox line should look like this: inbox = pop://pe...@ar... You'll be prompted for your password when it's needed. Note that j's mail feature doesn't really work with local Unix-style mailboxes (although you can open them read-only). Your question reminded me that confirmSend should really be true by default, and I've just made that change in CVS, so starting with 0.18.1.13 you will be able to omit the "confirmSend = true" line. (Actually, mail works fine if confirmSend is false, but if you're just getting started, the confirmation dialog is probably helpful.) -Peter |
From: Grzegorz R. <gru...@po...> - 2003-05-15 14:07:46
|
Peter Graves wrote: > > But I've a problem with the email feature. I've edited profs file as in > > documentation and restarted J. But I still don't see Mailbox Mode. Any > > Ideas how to gget it work ??? > You need to add lines similar to these to ~/.j/prefs (or C:\.j\prefs): .. [cut the prefs file example] Thanks for help, which is nearly exactly the same as in documentation (below of confirmSend key). > Then you should be able to do Alt X, "inbox" (or Ctrl O, "inbox") and > open your inbox. (You should also see the Inbox button appear on your > toolbar, if you have the toolbar enabled.) Sorry, it stil doesn't work. Either with hotkey and I don't see INBOX icon. My profs file contains : # # Windows # # encoding for polish characters defaultEncoding = ISO8859_2 # Mail settings enbleExperimentalFeatures = true enableMail = true # MBox settings userFullName = Grzegorz Rumatowski userMailAddress = gru...@po... # Mail Server settings inbox = {gru...@po...} smtp = smtp.poczta.onet.pl confirmSend = true pop://gru...@po... # Keeps messages on MailServer # Until they will be deleted locally popKeepMessagesOnServer = true popExpungeDeletedMessagesOnServer = true > Note that j's mail feature doesn't really work with local Unix-style > mailboxes (although you can open them read-only). Ok, I'm testin' on Windows now with 0.18.1 version of J and JVM 1.4 from Sun. BTW: A usenet access (news reader) feature would be nice. Maybe, if I'll take closer look at the sourcecode I'd implement it. > -Peter Greetings, Grzegorz |
From: Peter G. <pe...@ar...> - 2003-05-15 15:06:47
|
The main problem is a typo: # Mail settings enbleExperimentalFeatures =3D true ^^^^^ should be enableExperimentalFeatures =3D true ^^^^^^ There's also an inconsistency in this section: # Mail Server settings inbox =3D {gru...@po...} smtp =3D smtp.poczta.onet.pl confirmSend =3D true pop://gru...@po... The first line specifies an IMAP inbox: inbox =3D {gru...@po...} Even so I think it's incorrect; it should probably be inbox =3D {gru...@po...}inbox But later you have the line: pop://gru...@po... which, in terms of a Java properties file, is a value without a key. It should be: inbox =3D pop://gru...@po... ^^^^^^^^ And in the end, there should be exactly ONE inbox line. So -either- inbox =3D {gru...@po...}inbox or inbox =3D pop://gru...@po... but not both. =46rom the rest of the context it seems like you want POP, so the section= should probably look like this: # Mail Server settings inbox =3D pop://gru...@po... smtp =3D smtp.poczta.onet.pl confirmSend =3D true -Peter |
From: Grzegorz R. <gru...@po...> - 2003-05-15 17:40:51
|
Peter Graves wrote: .. [cut off a really good explanations] Hmm, so it seems I was misunderstanding the documentation. Big thanks for the help. Works fine now. > -Peter Greetings, Grzegorz -- Grzegorz Rumatowski http://members.chello.at/grzegorz/ apcoh official site: http://www.apcoh.org/ |
From: Peter G. <pe...@ar...> - 2003-05-15 16:17:20
|
> BTW: A usenet access (news reader) feature would be nice. Maybe, if I'll > take closer look at the sourcecode I'd implement it. Some code for this already exists. Try Alt X, "news news.software.ibm.com", for example. (You need to enable experimental features for this to work.) There are a couple of big deficiencies: It's really a news lurker; there's no way to post... ;) State is not saved, so if you return in a later session, all the messages will appear to be unread, even if you've read them. As well as many smaller deficiencies (no support for killfiles or bozofilters, among other things)... -Peter |
From: Brad B. <br...@gl...> - 2003-05-16 15:19:56
|
I seem to remember that the sidebar directory tree would follow the current directory. In other words, if I'm in my home directory, the /home/<username> folder would be expanded in the sidebar directory tree, and then if I use a directory buffer to navigate to a different folder (or if I use the directory buffer list to select a new buffer), the sidebar directory tree would refresh itself to the new location. That behavior seems to be missing for the last few releases. Or am I just imagining things? Either way, I would find that behavior helpful. Thanks for your work on j. -- _____________________________ Brad Brizendine, CTO, Glyphix |
From: Brad B. <br...@gl...> - 2003-05-16 15:33:51
|
OK, I have a little more detail. I just re-built my prefs file and most of the functionality appears to have returned. Here's what's not working as I expected: I opened two files located in different directories, /home/briz/.j/prefs and /home/briz/web/test.html. Both files show up in my directory buffer list, along with a directory buffer item which is set to /home/briz/web. When I use the sidebar buffer list to click on "prefs" and then hit Control-D, the sidebar directory tree correctly hilites /home/briz/.j. However, when I select "test.html", the sidebar buffer list directory item correctly changes to /home/briz/web, but the sidebar directory tree doesn't select /home/briz/web; its tree is open only to /home/briz. After trying to duplicate this several times (I can't duplicate it every single time), I'm beginning to wonder if it has something to do with caching. Does j cache the results in the sidebar directory tree? On Fri, 2003-05-16 at 08:19, Brad Brizendine wrote: > I seem to remember that the sidebar directory tree would follow the > current directory. In other words, if I'm in my home directory, the > /home/<username> folder would be expanded in the sidebar directory > tree, and then if I use a directory buffer to navigate to a different > folder (or if I use the directory buffer list to select a new buffer), > the sidebar directory tree would refresh itself to the new location. > > That behavior seems to be missing for the last few releases. Or am I > just imagining things? > > Either way, I would find that behavior helpful. > > Thanks for your work on j. > > > > > -- > _____________________________ > Brad Brizendine, CTO, Glyphix -- _____________________________ Brad Brizendine, CTO, Glyphix |
From: Peter G. <pe...@ar...> - 2003-05-16 15:56:05
|
> > I seem to remember that the sidebar directory tree would follow the > > current directory. In other words, if I'm in my home directory, the > > /home/<username> folder would be expanded in the sidebar directory > > tree, and then if I use a directory buffer to navigate to a different > > folder (or if I use the directory buffer list to select a new buffer), > > the sidebar directory tree would refresh itself to the new location. > > > > That behavior seems to be missing for the last few releases. Or am I > > just imagining things? > > Hmmm... I'm a bit confused by all of this myself. If I hit Ctrl D right now, using 0.18.1.13+ to compose this message, I get (as expected) a directory buffer on my home directory, but the tree comes up looking at /, which seems wrong; I would have expected the tree to be open to /home/peter. The official 0.18.1 release seems to have the same problem. 0.15.3 (which I happen to have lying around for some reason) seems to work correctly: if I open a directory buffer on /home/peter, the tree opens to /home/peter too. So I'm thinking something broke, and then I get your second message... > OK, I have a little more detail. I just re-built my prefs file and most > of the functionality appears to have returned. I don't think the prefs file should have anything to do with this. What did you change? > Here's what's not working as I expected: I opened two files located in > different directories, /home/briz/.j/prefs and /home/briz/web/test.html. > Both files show up in my directory buffer list, along with a directory > buffer item which is set to /home/briz/web. When I use the sidebar > buffer list to click on "prefs" and then hit Control-D, the sidebar > directory tree correctly hilites /home/briz/.j. However, when I select > "test.html", the sidebar buffer list directory item correctly changes to > /home/briz/web, but the sidebar directory tree doesn't select > /home/briz/web; its tree is open only to /home/briz. I don't really follow the scenario here, exactly, but I still think something's broken. > After trying to duplicate this several times (I can't duplicate it every > single time), I'm beginning to wonder if it has something to do with > caching. Does j cache the results in the sidebar directory tree? Yes. You can force a complete refresh by doing Ctrl R in a directory buffer. But this should only make a difference (as far as the sidebar tree is concerned) if you create or remove a directory, which isn't part of your scenario as I understand it. (Note that just to muddy the waters a bit more, sidebar updates are generally done asynchronously by the idle thread, which makes the timing a bit unpredictable.) In any case, I still think something broke between 0.15.3 and 0.18.1. I'll see if I can track it down. Thanks for reporting the problem! -Peter |
From: Brad B. <br...@gl...> - 2003-05-16 16:23:54
Attachments:
prefs
prefs.bkup
|
Thanks for the unbelievably quick reply. I've tried to clarify things a little in answering your questions below. On Fri, 2003-05-16 at 08:56, Peter Graves wrote: > > > I seem to remember that the sidebar directory tree would follow the > > > current directory. In other words, if I'm in my home directory, the > > > /home/<username> folder would be expanded in the sidebar directory > > > tree, and then if I use a directory buffer to navigate to a different > > > folder (or if I use the directory buffer list to select a new buffer), > > > the sidebar directory tree would refresh itself to the new location. > > > > > > That behavior seems to be missing for the last few releases. Or am I > > > just imagining things? > > > > > Hmmm... > > I'm a bit confused by all of this myself. > > If I hit Ctrl D right now, using 0.18.1.13+ to compose this message, I > get (as expected) a directory buffer on my home directory, but the tree > comes up looking at /, which seems wrong; I would have expected the > tree to be open to /home/peter. > > The official 0.18.1 release seems to have the same problem. > > 0.15.3 (which I happen to have lying around for some reason) seems to > work correctly: if I open a directory buffer on /home/peter, the tree > opens to /home/peter too. > > So I'm thinking something broke, and then I get your second message... > > > OK, I have a little more detail. I just re-built my prefs file and most > > of the functionality appears to have returned. > > I don't think the prefs file should have anything to do with this. What > did you change? I didn't think so either. I don't know why I did it in the first place. I basically backed it up and then started from scratch. I've attached both to this email so you can see for yourself. > > > Here's what's not working as I expected: I opened two files located in > > different directories, /home/briz/.j/prefs and /home/briz/web/test.html.. > > Both files show up in my directory buffer list, along with a directory > > buffer item which is set to /home/briz/web. When I use the sidebar > > buffer list to click on "prefs" and then hit Control-D, the sidebar > > directory tree correctly hilites /home/briz/.j. However, when I select > > "test.html", the sidebar buffer list directory item correctly changes to > > /home/briz/web, but the sidebar directory tree doesn't select > > /home/briz/web; its tree is open only to /home/briz. > > I don't really follow the scenario here, exactly, but I still think > something's broken. > > > After trying to duplicate this several times (I can't duplicate it every > > single time), I'm beginning to wonder if it has something to do with > > caching. Does j cache the results in the sidebar directory tree? > > Yes. You can force a complete refresh by doing Ctrl R in a directory > buffer. But this should only make a difference (as far as the sidebar > tree is concerned) if you create or remove a directory, which isn't > part of your scenario as I understand it. > > (Note that just to muddy the waters a bit more, sidebar updates are > generally done asynchronously by the idle thread, which makes the > timing a bit unpredictable.) OK, I'll try to muddy the waters a little myself. Here's another thing I noticed. Using the above scenario, meaning that the sidebar directory tree was open to both /home/briz/.j and /home/briz/web, I then hit F1. While viewing the main help file, I hit Control-D. The sidebar buffer list created a directory buffer for the j install dir, but the sidebar directory tree was open only to the root level, and nothing was selected in it. Since I had never used the sidebar directory tree to traverse to j's install dir, it leads me to wonder if the sidebar directory tree can only refresh to a location for which it has already created a subtree. I hope this helps. > > In any case, I still think something broke between 0.15.3 and 0.18.1. > > I'll see if I can track it down. > > Thanks for reporting the problem! Thanks for your support. I did yet another "state of the editors" search yesterday and came right back to j again. > > -Peter -- _____________________________ Brad Brizendine, CTO, Glyphix |
From: Peter G. <pe...@ar...> - 2003-05-16 17:01:27
|
Hi Brad, The patch below should solve the problem. The fix will also be in the 0.18.1.14 development snapshot which I hope to get out later today. A wee bit of a brain cramp, there, while trying to apply a bit of bulletproofing to the code. Looks like 0.18.1 was the first official release to suffer from this problem. Thanks a lot for your help with this! -Peter diff -u -r1.4 DirectoryTree.java --- DirectoryTree.java 12 May 2003 03:25:18 -0000 1.4 +++ DirectoryTree.java 16 May 2003 16:52:52 -0000 @@ -150,7 +150,7 @@ private DefaultMutableTreeNode getNode(File file) { - if (treeModel == null || file != null) + if (treeModel == null || file == null) return null; return treeModel.getNode(file); } |
From: Olivier I. <Oli...@la...> - 2003-05-16 17:14:48
|
Hello the list I would like to congratulate Peter for this wonderful tool (j !). It is very efficient ... I would like to suggest just a feature missing about xml mode : to be able to validate xml again DTD or shema as jEdit xml mode does ... This is the only feature missing to switch definitively to j. Olivier. |
From: Peter G. <pe...@ar...> - 2003-05-19 18:34:28
|
> I would like to suggest just a feature missing about xml mode : to be > able to validate xml again DTD or shema as jEdit xml mode does ... > This is the only feature missing to switch definitively to j. This seems like a very reasonable suggestion. The version of Aelfred that is bundled with j is a non-validating, SAX1 parser. It has always been possible to use a different, possibly validating parser, as described in doc/xmlmode.html, but j currently provides no way to turn validation on or off, so you're stuck with the default setting of the parser in question, which is clearly suboptimal. What I'd really like to do is require Java 1.4, which comes with the Crimson parser, which supports optional validation. Then j could drop Aelfred (and the bundled version of SAX2), XmlParseImpl.java could be rewritten to fully utilize the SAX2 APIs, and some sort of UI (or Alt X tricks) could be provided to manage the features and properties of the underlying parser. So I'm thinking that 0.19.0, which should be out in the next week or so, will be the last version of j to support Java 1.3. (0.19.0 will introduce the Java debugger, plus improved diff support and various bugfixes and other oddments.) 0.20.0 will be the first release to require Java 1.4, and it will provide new and improved XML support as outlined above. How does this sound? -Peter |