Sponsored Content
Contact Us Post Here to Contact Site Administrators and Moderators Problem connecting to www.unix.com Post 302216119 by Neo on Friday 18th of July 2008 03:40:17 AM
Old 07-18-2008
Yes, we upgraded the forums recently and you need to clear your browser cache and cookies, close and restart your browser.
 

5 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

New www.unix.com search

PUZZLED: How can I search for posts on 'VI' if by the new rules (or maybe they are old) I get the messge: "The search term you specified (vi) is under the minimum word length (3) and therefore will not be found. Please make this term longer. If this term contains a wildcard, please make... (13 Replies)
Discussion started by: sierra_aar
13 Replies

2. Post Here to Contact Site Administrators and Moderators

www.unix.com

Of late, when i start www.unix.com my system is going to 100% CPU and takes lot of time to get the information. I think this is happening after adding the graphics on the page. Has anyone seen this problem..Sorry to post this here.. (6 Replies)
Discussion started by: sssow
6 Replies

3. Forum Support Area for Unregistered Users & Account Problems

Access to https://www.unix.com/source?

Folks, Hope this is not a newbie question, but it might end up being that. I wanted to retrieve the source code for unix_linux_bench as directed on https://www.unix.com/linux-benchmarks/11175-instructions-linux-benchmarks.html When one clicks on the links specified for download, the browser... (1 Reply)
Discussion started by: wagdalule
1 Replies

4. Shell Programming and Scripting

[Ubuntu / PERL ]Problem installing WWW::Mechanize mod

Hello everyone, I've got some problem intalling a perl module. The installation is well done as you can see below. gueg@ux31:~$ sudo apt-get install libwww-mechanize-perl Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état...... (4 Replies)
Discussion started by: tot94
4 Replies

5. Post Here to Contact Site Administrators and Moderators

Www.UNIX.com is slow today ???

Hi, Just wanting to know if there is any issues today with the site. Initially I thought it is my internet connection or computer but regardless which one I use, the site has been slow and it is also not showing with the right fonts etc. I've been trying for the last 12+ hours and it's always been... (21 Replies)
Discussion started by: newbie_01
21 Replies
JEDIT(1)						      General Commands Manual							  JEDIT(1)

NAME
jedit - Programmer's text editor written in Java SYNOPSIS
jedit [ options ] [ files ] DESCRIPTION
This manual page briefly documents jEdit's command-line parameters. Complete documentation can be found by invoking the Help->jEdit Help menu item within jEdit. jEdit is a cross-platform text editor written in Java. It has an extensive feature set that includes syntax highlighting, auto indent, folding, word wrap, abbreviation expansion, multiple clipboards, powerful search and replace, and much more. Furthermore, jEdit is extremely customizable, and extensible, using either macros written in the BeanShell scripting language, or plugins written in Java. jEdit requires Java 2 version 1.3. jEdit is released under the GNU General Public License, which can be found in the online help. GENERAL COMMAND LINE USAGE
When opening files from the command line, a line number or marker to position the caret on can be specified like so: $ jedit MyApplet.java +line:10 $ jedit thesis.tex +marker:c Command-line switches begin with a "-". Some take a parameter. A file whose name begins with "-" can be opened like so: $ jedit -- -myfile MISCELLANEOUS OPTIONS
-log=level Set the minimum log level to an integer between 1 and 9. Default is 7. Has no effect when connecting to another instance via the edit server. -usage Show a brief command line usage message without starting jEdit. This message is also shown if an invalid switch was specified. -version Show the version number without starting jEdit. -- Specifies the end of command-line processing. Further parameters are treated as file names, even if they begin with a dash. CONFIGURATION OPTIONS
-plugins Enable loading of plugins. This is the default. Has no effect when connecting to another instance via the edit server. -noplugins Disable loading of plugins. Has no effect when connecting to another instance via the edit server. -restore Restore previously open files on startup. This is the default. -norestore Do not restore previously open files on startup. -run=script Run the specified BeanShell script. There can only be one of these parameters on the command line. -settings=dir Store user-specific settings in the directory named "dir", instead of the default $HOME/.jedit. The directory will be created auto- matically if it does not exist. Has no effect when connecting to another instance via the edit server. -nosettings Start jEdit without loading user-specific settings. -startupscripts Run startup scripts. This is the default. Has no effect when connecting to another instance via the edit server. -nostartupscripts Disable startup scripts. Has no effect when connecting to another instance via the edit server. EDIT SERVER OPTIONS
For information about the edit server, see the section "Starting jEdit" in the jEdit online help. -background Run jEdit in background mode. In background mode, the edit server will continue listening for client connections even after all views are closed. Has no effect when connecting to another instance via the edit server. -nobackground Disable background mode. This is the default. Has no effect when connecting to another instance via the edit server. -gui Open an initial view. This is the default. Has no effect when connecting to another instance via the edit server. -nogui Do not open an initial view, and instead only open one when the first client connects. Can only be used in combination with the -background switch. You can use this switch to "pre-load" jEdit when you log in to your computer, for example. Has no effect when connecting to another instance via the edit server. -server Store the server port info in the file named "server" inside the settings directory. This is the default. -server=name Store the server port info in the file named "name". File names for this parameter are relative to the settings directory. -noserver Do not attempt to connect to a running edit server, and does not start one either. FILES
/usr/share/jedit jEdit program files. /usr/share/jedit/doc jEdit online help, which can be viewed from within jEdit using the Help->jEdit Help command. /usr/share/java/jedit.jar The jEdit program. /usr/bin/jedit Shell script for starting jEdit. /usr/share/man/man1/jedit.1 This manual page. $HOME/.jedit Each user who runs jEdit has a settings directory. Its content is documented in the "Customizing jEdit" section of the online help. SEE ALSO
java(1) VERSION
jEdit 4.2 BUGS
See http://www.jedit.org/index.php?page=feedback for bug reporting information. WEB
http://www.jedit.org/ AUTHOR
This page was written by Krzysztof Krzyzaniak (eloy) <eloy@debian.org> for Debian project, with further modifications and additions for jEdit 4.2 by Slava Pestov <slava@jedit.org>. April 23, 2003 JEDIT(1)
All times are GMT -4. The time now is 05:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy