.
although i like the frame display too, i would probably go for using
non-local files without frames,
heinz-dieter conradi
since the subject of jde-help has just surfaced i remembered another old
problem of mine.
i got the problem some time ago when i shared my linux box with a
coworker. whoever was the second to call jde-help got an error. the
document had been fetched by wget into the global tmp directory by the
f
:
> Check out jde-eclipse.el:
this requires a running eclipse and i was trying to do without it.
however, for the time beeing, it might worth considering.
heinz-dieter conradi
do this?
tia, heinz-dieter conradi
/to/prj/directory"))
one could write something more generic and portable?
tia for any ideas, heinz-dieter conradi
eturn)] '(lambda ()
(interactive)
(c-indent-command)
(c-context-line-break)
))
heinz-dieter conradi
.
wouldn't it be better to show the compilation window (with just the
classpath ...) immediatly after the compilation started.
tia, heinz-dieter conradi
hi alain,
> > The project is becoming
> > more and more complex and I have not been able to implement the
> > dependencies into the Makefiles. So I decided to give this a try in the
> > JDE environment, but also in vain.
>
> Nope, JDE is not the answer. You need an external tool for that. You can
hi paul,
>
> Turns out there was an extraneous print statement in
> jde-compile-run-exec, perhaps left over from a debugging session, that
> was dumping the compiler arguments into the minibuffer. I've removed
> the print statement from the latest version of compile.el in the CVS
> repository.
>
r removing the other compiler
deprecation option).
and at work the entry above
'(jde-compile-option-debug (quote ("all" (t nil nil)
is working
!???
still puzzled, heinz-dieter conradi
kes" "1.14"
"/usr/local/bin/jikes" # # nil nil])
apply(jde-compile-compiler [object jde-compile-jikes "jikes" "jikes" "1.14"
"/usr/local/bin/jikes" # # nil nil])
eieio-generic-call(jde-compile-run-exec ([object jde-compile-jikes &qu
hi paul,
> Heinz-Dieter Conradi writes:
> > hi all,
> >
> > while tracking down some problems with regard to using the IBM VM i
> > noticed some oddities with regard to the jdk-registry.
> >
> > - specifying the Jde-Run-Executable
> >
hi paul,
> >
> > i have got some problems when trying to use the IBM VM with the new
> > jdk-registry.
> >
> > the main entry in this prj.el is:
> >
> > '(jde-jdk-registry (quote (
> > ("IBM" . "/opt/java/IBMJava2-13/")
> ^
>
> The purpose of the version field is to allo
> Also, I think there is a way to handle file names with spaces in them
> by using a print0 argument to find, but I have never been able to get
> that to work on my NT / cygwin box.
just use 'print0' in combination with 'xargs -0' as in
find . -name "*.java" -print0 | xargs -0 grep "something"
ng here?
Since nobody else seems to have this problem, I guess I have made some
stupid mistake ;-(
In the meantime I will happily continue to use beta1 with semantic 1.3.2.
TIA, Heinz-Dieter Conradi
15 matches
Mail list logo
