can't see screen using Jedit 4.3pre8
Submitted by
liran vigdor on
Wednesday, 15 November, 2006 - 07:05
I was using jedit 4.2 and now tried to transfer to 4.3pre8 , but when starting Jedit , I cant see anything, and only if I pass on the screen with the mouse it will show the screen - this is true only for the icons and other jedit stuff, the files themself can't be seen anyway !
thanks
What's best to use for XML formatting? Tried JTidy but it's causing line breaks
Submitted by
rickcr on
Wednesday, 15 November, 2006 - 19:26
What is the best plugin for formatting XML files? I tried using JTidy but I can't seem to figure out how to get it to not put in a line break in between every line. TIA for any help.
Console plugin significantly slows down build process
Submitted by
shlomy on
Sunday, 19 November, 2006 - 11:59
Hi,
I've started using the Console plugin (with the ErrorList plugin) to build our project. First, I must say that the Console plugin is really great - it is very easy to configure to support other tools (e.g. g++), and it simplies working with jEdit a lot.
The problem is that the output of my build process, which is quite large, is displayed in the Console plugin very slowly (much slower than the Linux shell), and this slows down the build significantly. Any idea why this happens or what I can do to fix this slowdown?
Also, from the documentation of the Console plugin, it seems like it tries to match all the Error Patterns until it finds a match. Is this the way it works? While it may be good enough for most purposes, there are several problems with this:
1. Lines which do not express errors in the output of one tool, may express errors in the output of another tool. So if I'm running the first tool, I may get false errors because its output is also matches with the other error patterns. (Probably rare, though)
2. The output is probably slowed down by several redundant pattern matches.
Since the Console plugin cannot really know which tool is generating the output, it can either try all of the Error Patterns or rely on the user to indicate which Error Patterns to include. When I run "make", I only have "g++" output, so I don't need to match all other patterns (I've added a 'g++' error pattern manually). When I run Perl, I only have Perl output. I can erase some error patterns to exclude them, but I think the Console plugin should enable the user to select the active error patterns to use (e.g. using check-boxes or using disable/enable buttons below the Error Patterns list), to avoid unwanted pattern matches.
Shlomy
In firefox, drop downs are not legible. They are close to zero width. Simple CSS fix.
Submitted by
Anup on
Sunday, 19 November, 2006 - 18:22
The community web site, for ages, has had drop downs that cannot be read, because their width is screwed up.
The problem is by the following CSS rule (around line 38 of style1.css)
.box * {
max-width: 100%; /* make sure textarea's and inputs do not overflow the containing box */
}
The * makes EVERYTHING have this max-width, and it is not needed.
Removing it sorts it out. If you really want this just for text areas and inputs, then use this:
.box textarea, .box input {
max-width: 100%; /* prevent overflow of the containing box */
}
This is critical, for it prevents using the web site effectively under Firefox (which I imagine is a LARGE audience for this site) because you can't read the drop downs. User participation will hopefully increase when this is done.
Please create a feature to allow community members to monitor forum blogs and delete fake/spam users
Submitted by
Anup on
Sunday, 19 November, 2006 - 18:27
The tons of chinese comment spam is wrecking the usefulness of JEdit's community site. Here are some ideas (not knowing anything about Drupal) how to sort this out:
1) Community self-policing: allow/invite some users somehow (loyal, longtime, frequent posters, ask who is interested?) to volunteer to police the community site. Limit capability only to delete posts, or report a user abusing the site (this will prevent misuse by volunteers!). Then, when users or posts are marked as requiring deletion or something, another group agrees, or the admin has final say or something like that.
Of course, this needs to be done in such a way that the same robots that create accounts and post content do not create volunteer accounts!
2) Put rel="nofollow" or whatever it is, in the anchor tag of html posts, so that spammers have no need to try and create fake accounts. They are just trying to increase their links so that search engines will follow them.
Drupal must have some comment spam plug-in surely?
Not addressing this for so long is creating a negative impression amongst users, and losing the value of this open-source project... JEdit itself is excellent, but its natural support has to be good too.
WTF MAKES A NEW LINE???
Submitted by
thinsoldier on
Sunday, 19 November, 2006 - 19:26
I need to fine all commas (,) and replace them with a new line/ carriage return.
for example: jim,jane,john,joe,kelly,kent,kimberley
becomes:
jim
jane
john
etc....
HOW?
in BBEdit I can
find: ,
replace: \r
done.
but jedit doesnt respond to \r, \n, \r\n it just literally replaces the , with \ r \ n !
ie: jim\rjane\rjohn\rjoe\rkelly\rkent\rkimberley !
And where is the best place to find active JEdit users? Is there an irc channel anywhere?
ABB RAPID edit mode (jEdit-ABB_RAPID.zip v0.0.1 by Andrew Thompson)
Submitted by
andrewt on
Thursday, 23 November, 2006 - 05:28
Edit mode for jEdit 4.2 for ABB RAPID robot programming language.
Note this is not 100% complete. It has been some time since I worked on this, but thought I should make this available "as-is" at least. Please feel free to develop it!
In particular, there is no auto un-indent - as far as I know this was not supported by jEdit 4.2
Includes code browser support via ctags.
Favorites / FTP-Plugin: label for connections?
Submitted by
pepl on
Thursday, 23 November, 2006 - 10:51
Hi!
I'm using jEdit to edit files (almost Perl) which resides on Unix servers who are placed in strong secured areas in our company.
The only way to access these files is to use a special server over which i have to establish SSL tunnels to the servers.
This means that i'm always connecting over one server on different ports.
I save these connections as favorites and unfortunately they all, for example, look like this:
'sftp://user@server:55010/usr/ldap'
'sftp://user@server:55020/usr/ldap'
'sftp://user@server:55030/usr/ldap'
'sftp://user@server:55040/usr/ldap'
'sftp://user@server:55020/prj/ldap/scripts'
'sftp://user@server:55040/prj/ldap/scripts'
This could be connections to four different servers - ports 55010,...,55040 (e.g. production, test, etc.).
Until now i have 12 connections defined who all look like the example above.
As you can see this ist very confusing, very unclear.
If there where the possibility to enter labels for favorites or for ftp-connections it would be much easier for me.
In Ultra-Edit there's a possibility to name (to label) connections (i used Ultra-Edit before).
Do you think it's possible to create a feature like labeling or naming favorites or ftp-connections?
Thanks
Pepl
Cheat RubyGem macros
Submitted by
charlesroper on
Friday, 24 November, 2006 - 18:17
I've created a couple of macros for the excellent Cheat RubyGem (check it out: http://cheat.errtheblog.com/). Download 'em from here:
http://homepages.nildram.co.uk/~charlesr/jedit/cheat_macros.zip
Charles
Rails macro for moving between related files
Submitted by
marioaquino on
Saturday, 25 November, 2006 - 20:31
I have created a macro for jumping between related files in a Rails project. The macro figures out what file you have in your buffer and offers a popup list of other related files that you can jump to. There is a brief screencast demonstrating the macro that you can view on my blog: http://marioaquino.blogspot.com/
You can download the macro from: http://mario.blogdns.net/rails_macro.zip
SVN update (svn_update.bsh v1.0 by Dale Anson)
Submitted by
daleanson on
Sunday, 26 November, 2006 - 16:49
Macro to run SVN update. The SVN command line client needs to be installed separately.
SVN Add (svn_add.bsh v1.0 by Dale Anson)
Submitted by
daleanson on
Sunday, 26 November, 2006 - 17:28
Console plugin is required. SVN command line client is required. Works on current buffer only. I add it to the text area context menu (right click on the text area, then "Customize this menu").
SVN Commit (svn_commit.bsh v1.0 by Dale Anson)
Submitted by
daleanson on
Sunday, 26 November, 2006 - 17:29
Console plugin is required. SVN command line client is required. Works on current buffer only. I add it to the text area context menu (right click on the text area, then "Customize this menu").
SVN Info (svn_info.bsh v1.0 by Dale Anson)
Submitted by
daleanson on
Sunday, 26 November, 2006 - 17:30
Console plugin is required. SVN command line client is required. Works on current buffer only. I add it to the text area context menu (right click on the text area, then "Customize this menu").
SVN Log (svn_log.bsh v1.0 by Dale Anson)
Submitted by
daleanson on
Sunday, 26 November, 2006 - 17:31
Console plugin is required. SVN command line client is required. Works on current buffer only. I add it to the text area context menu (right click on the text area, then "Customize this menu").
SVN Revert (svn_revert.bsh v1.0 by Dale Anson)
Submitted by
daleanson on
Sunday, 26 November, 2006 - 17:32
Console plugin is required. SVN command line client is required. Works on current buffer only. I add it to the text area context menu (right click on the text area, then "Customize this menu").
PV SVN Add (pv_svn_add.bsh v1.0 by Dale Anson)
Submitted by
daleanson on
Sunday, 26 November, 2006 - 17:41
These macros work on the currently selected node in the ProjectViewer tree. If the node is a directory, the commands are recursive, except for the info command. I added them to the ProjectViewer context menu (Plugins, Plugin Options, ProjectViewer, Context Menu). Both ProjectViewer and Console plugins are required, SVN command line client required.
PV SVN Commit (pv_svn_commit.bsh v1.0 by Dale Anson)
Submitted by
daleanson on
Sunday, 26 November, 2006 - 17:42
These macros work on the currently selected node in the ProjectViewer tree. If the node is a directory, the commands are recursive, except for the info command. I added them to the ProjectViewer context menu (Plugins, Plugin Options, ProjectViewer, Context Menu). Both ProjectViewer and Console plugins are required, SVN command line client required.
PV SVN Info (pv_svn_info.bsh v1.0 by Dale Anson)
Submitted by
daleanson on
Sunday, 26 November, 2006 - 17:43
These macros work on the currently selected node in the ProjectViewer tree. If the node is a directory, the commands are recursive, except for the info command. I added them to the ProjectViewer context menu (Plugins, Plugin Options, ProjectViewer, Context Menu). Both ProjectViewer and Console plugins are required, SVN command line client required.
PV SVN Log (pv_svn_log.bsh v1.0 by Dale Anson)
Submitted by
daleanson on
Sunday, 26 November, 2006 - 17:44
These macros work on the currently selected node in the ProjectViewer tree. If the node is a directory, the commands are recursive, except for the info command. I added them to the ProjectViewer context menu (Plugins, Plugin Options, ProjectViewer, Context Menu). Both ProjectViewer and Console plugins are required, SVN command line client required.