Re: strange behaviour with SuSE8.0

[Klaus Schmid <klaus.schmid@xxxxxx>]

Am Montag, 20. Mai 2002 05:15 schrieb John E. Davis:
> Klaus Schmid <klaus.schmid@xxxxxx> wrote:
> >1. I can copy only a few characters from xjed to kmail.
> >If I select more, nothing happens  -- or the cursor jumps some lines
> >away -- while trying to paste with the mouse middle button.
>
>    Does this problem only arise with kmail?  What about pasting into
> some other program, e.g., jed running in an xterm?

Same with pasting into xterm jed and xterm command line.

> >2.  With xjed -- and jed -- my .jedrc gets evaluated
> >one time more then expected. (With SuSE8.0-jed 2 times more!)
> >That means '-n' does not work and otherwise it gets evaluated
> >twice.
>
> Is is possible that SuSE has installed something in, e.g.,
> /etc/jed.conf, causing your .jedrc to load twice?

Yes, there is something. I found
but yet not sure what happens/happened here:

ks@linux:~> ls /etc/jed* -l -A
-rw-r--r--    1 root     root          392 Mai 16 20:10 /etc/jed-defaults.sl
-rw-r--r--    1 root     root           39 Mär 25 20:35 /etc/jed.conf

/etc/jed-init.d:
insgesamt 16
-rw-r--r--    1 root     root          341 Mär 25 20:35 00site.sl
-rw-r--r--    1 root     root         1516 Mär 25 20:35 01lxkernel.sl
-rw-r--r--    1 root     root          310 Mär 25 20:35 02visbell.sl
-rw-r--r--    1 root     root          479 Mär 25 20:35 99default.sl
ks@linux:~>

> What does
>     jed -batch
>
> produce?

This:

ks@linux:~> jed -batch
loading /usr/local/jed/lib/site.sl
loading /usr/local/jed/lib/os.sl
loading /usr/local/jed/lib/menus.sl
loading /etc/jed.conf
loading /etc/jed-defaults.sl
loading /etc/jed-init.d/00site.sl
loading /usr/share/jed/lib/jed.rc
loading /etc/jed-init.d/01lxkernel.sl
loading /etc/jed-init.d/02visbell.sl
loading /etc/jed-init.d/99default.sl
loading /home/ks/jed/.jedrc            *** see note ***
loading /home/ks/jed/jed.rc
loading /usr/local/jed/lib/keydefs.sl
loading /usr/local/jed/lib/isearch.sl
loading /home/ks/jed/patchlib/bw.sl
loading /home/ks/jed/patchlib/nextbuf.sl
loading /home/ks/jed/patchlib/nextwin.sl
loading /home/ks/jed/patchlib/scroll.sl
loading /home/ks/jed/jd/jdini.sl
loading /home/ks/jed/patchlib/protpl.sl
loading /home/ks/jed/patchlib/emacs.sl
loading /usr/local/jed/lib/colors/black3.sl
ks@linux:~>

note: I have defined JED_HOME=/home/ks/jed at system login;
.jedrc evaluates jed.rc (win compatible); library path gets
extended to /home/ks/patchlib. It seems after doing this
the '-n' switch works and .jedrc gets evaluated just one time.
I think defining JED_HOME was the critical change for this.
(Maybe I will now tweak with JED_LIBRARY -- thanks for
providing this way -- to regain full control and consistency
for win-Jed and lin-Jed.)

For future release I feel initialization conventions should be a bit
more simpler and transparent, but not less powerful.
Wouldn't some changes be worth the effort in the long run?

Thanks
Klaus