Running linux, jedit 4.3pre16.
I am seeing that jedit will only open the first eight files I supply to it on the
command line. If I supply any more than that, the files after the first eight, are
simply not opened.
I can open as many as I want, using the mouse (directory/file browser), once I am
in the editor. Unfortunately I often need to supply a large number of files on the
command line.
This behavior did not occur in 4.2. In 4.2 you can supply as many files as you want
on the command line, and they all get opened. So if I want to open more than 8 files
on the command line, I use 4.2.
Submitted | mtgavin - 2009-04-04 05:07:56 | Assigned | |
---|---|---|---|
Priority | 5 | Labels | editor core |
Status | open | Group | None |
Resolution | None |
2009-04-04 14:06:46 shlomy |
What is the command-line that you use to launch jEdit with a specified list of files? |
---|---|
2009-04-04 15:59:43 mtgavin |
Nothing out of the ordinary (I don't think, anyway.) |
2009-07-26 15:19:50 dennis_sheil |
I have been having trouble dupicating the problem. mtgavin, what operating system
are you running on? I am running Linux, more specifically the deltah version of Gnewsense,
which is heavily based on Ubuntu Hardy. My shell is bash 3.2.33. With both 4.3.pre13
and 4.3.pre18, I can load more than eight files from the command line, with either
method you mention, either wildcard or explicitly. If you're running on a UNIX, what
shell are you using? I assume you're not running this from a MacOS X command line
or an MS-DOS prompt or the like. Since you're running this as "jedit" and not "java
-jar jedit.jar", I assume you're using the jedit installed by the OS flavor's package.
When I do a "which jedit" it shows /usr/bin/jedit as my shell script, when I do a
"tail -1 /usr/bin/jedit" it says |
2009-07-26 15:32:19 delvinj |
Works fine for me, windows XP.
|
2009-07-26 18:36:25 shlomy |
If jEdit only opens 8 files from the command-line, it's probably due to the batch
file (or alias?) named 'jedit'. Please add the contents of this alias / batch file.
|
2009-08-02 04:29:13 mtgavin |
After reading Dennis post, dated 2009-07-26 15:19, and shlomy: you are right, the
problem was in my jedit script, very similar to what Dennis described.
|
2009-08-02 05:24:56 shlomy |
Can you attach your jEdit invocation script?
|
2009-08-02 18:20:25 mtgavin |
shlomy - my script is identical to yours. On my linux system (Red Hat Enterprise release 4, Nahant Update 4), after it executes the first iteration of the 'while' loop (brings up jedit, with 9 files) it does not do anything else. So, it blocks after the first instance of the 'while' loop, leaving me with only the first 9 files open. I am not sure why the script is trying to do things this way, it seems to be much simpler to use the $@ parameter. What are we intending to accomplish with this looping? How is this better than simply using the $@ parameter, as dennis_shell indicated? |
2009-08-02 19:22:53 ezust |
You're missing a & in your batch file:
|
2009-08-02 19:31:14 shlomy |
That's not a custom batch file - it's the one that the installer creates, I think in this case the copy in the repository shoult be changed. |
2009-08-02 20:08:37 ezust |
Yes, I guess it's a bug in the installer script generation code of jedit core.
|
2009-08-03 00:21:10 mtgavin |
If you plan on adding an ampersand (&) after the exec call to jedit, please make sure it works. I tried adding the ampersand to the end of the exec call. When you do this, if jedit isn't already open, it does not work as intended -it opens ('numfiles' mod 9) versions of jedit (not just one), each with nine open files. |
2009-08-03 00:22:30 mtgavin |
Opps, meant that it adds 'numfiles / 9' (not mod 9) versions of jedit. Sorry. |