12:36 a.m.
Hi,
As I promised I tried the suggestion bellow and yes it (make check) works --
xemacs-21.4.1 and xemacs-21.5.0 on Solaris 8 on Sun w/s. Now I can check the
installation (and sleep better :-)
Thanks.
But I still have the problem with XEmacs not beeing able to customize (you caled
it broken button or something) I need to be able to use 'customize'.
Also both 21.5.0 and 21.4.1 treat fonts differently from 21.1.14 - I do not know
why. But I am missing a lot nice fonts that 21.1.14 uses and the others cannot.
Both 21.5.0 and 21.4.1 cannot (do not) open any images as images, i.e. open them
as (binary) files.
Because of that I have to keep 21.1.14.
I compiled all of them with the same configure parameters and use the same
(literally) configuration even the same packages except for
xemacs/libxemacs-21.x.x/lisp/.
Thanks
Latchezar
From: "Stephen J. Turnbull"
<turnbull(a)sk.tsukuba.ac.jp>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Date: Thu, 29 Mar 2001 13:20:57 +0900
To: "Latchezar M. Dimitrov" <lmdimi(a)mthcsc.wfu.edu>
Subject: Re: probs "Urania" on sparc-sun-solaris2.8
>>>>> "lmd" == Latchezar M Dimitrov
<lmdimi(a)mthcsc.wfu.edu> writes:
lmd> Would you or "the path guru" please tell how to do it now?
cd $path_to_XEmacs_sources
if [ -d xemacs-packages ] ; then rmdir -f xemacs-packages ; fi
if [ -L xemacs-packages ] ; then rm -f xemacs-packages ; fi
if [ -e xemacs-packages ] ; then exit(1) ; fi # should not happen!!
ln -s /usr/scratch/XEmacs/lib/xemacs/xemacs-packages xemacs-packages
if [ -d mule-packages ] ; then rmdir -f mule-packages ; fi
if [ -L mule-packages ] ; then rm -f mule-packages ; fi
if [ -e mule-packages ] ; then exit(1) ; fi # should not happen!!
ln -s /usr/scratch/Mule/lib/mule/mule-packages mule-packages
make check # should pass all tests now, unless the paths guru has
# changed the code that checks for "in-place" packages
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
Latchezar (Lucho) Dimitrov Wake Forest University, Winston-Salem, NC
home: (336) 794-2094 grad.lab: (336) 758-4954
mailto:dimil01g＠wfu.edu or http://www.wfu.edu/~dimil01g/
lmdimi(a)mthcsc.wfu.edu
lmdimi(a)pilot.mthcsc.wfu.edu
... Type fast, think slow. ...
"Hippocratic Oath For Software Engineers"
3:41 p.m.
New subject: (no subject)
|--==> "LMD" == Latchezar M Dimitrov <lmdimi(a)mthcsc.wfu.edu> writes:
LMD> Both 21.5.0 and 21.4.1 cannot (do not) open any images as images, i.e. open them
LMD> as (binary) files.
In ./lisp/format.el un-comment the image formats you want in
'format-alist'. Then re-compile XEmacs.
Steve T. You should probably do this for 21.4.2
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
2:03 a.m.
New subject: (no subject)
>>>> "SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> Steve T. You should probably do this for 21.4.2
No. IIRC that was because the image-mode code was broken. AFAIK that
hasn't changed. Autodetecting images has to be a user decision until
somebody audits image-mode.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
6:09 a.m.
New subject: (no subject)
|--==> "SJT" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes:
>>>>>"SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> Steve T. You should probably do this for
21.4.2
SJT> No. IIRC that was because the image-mode code was broken. AFAIK that
SJT> hasn't changed. Autodetecting images has to be a user decision until
SJT> somebody audits image-mode.
OK. Is that on anybody's todo list? I think this should be taken
care of _before_ this release goes public. IMO, this kind of
customization would be beyond the newbie user. Especially seeing as
though it doesn't seem to be documented anywhere.
In case anyone is interested, I've been 'autodetecting images' since
about 21.2.30-something with no image-mode problems.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
7:43 a.m.
New subject: (no subject)
>>>> "SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> OK. Is that on anybody's todo list? I think this should be
SY> taken care of _before_ this release goes public.
image-mode is in the packages, right? image-mode problems are
unrelated to the release. Show me that it's fixed, and I'll consider
a patch to format-alist.
In any case, we have _no_ labor committed to doing the things that
"should" be done, and we have a strong consensus for release. So I
did. The release _is_ "public"; I'm not going to take it back now.
The criterion for promotion from "gamma" to "stable" is exactly that:
don't crash, don't destroy data. "Working image-mode" is a feature,
and IMHO lack of it should not delay promotion to stable. (But that's
mostly Vin's decision.)
SY> IMO, this kind of customization would be beyond the newbie
SY> user. Especially seeing as though it doesn't seem to be
SY> documented anywhere.
Something should be done about that, but there are far more important
things on my personal todo list, like teaching custom about Mule fonts
or at least documenting how to break one leg of `custom-set-faces'.
In any case, AFAIK the image-mode functions autoload, so just do M-x
image-mode.
SY> In case anyone is interested, I've been 'autodetecting images'
SY> since about 21.2.30-something with no image-mode problems.
Sure. But that mode allows a lot more than just detect and display,
and it was silently trashing some files or something. It wasn't just
randomly removed from that alist. It assaulted somebody and was sent
to Coventry for its crime because nobody was willing to fix it
properly.
If you want to add it to 21.5 and see what happens, fine with me[1].
Eventually I'll look at the file(s) and look up the threads. But for
21.4, paranoia rules.
Footnotes:
[1] But some people object to adding stuff to format-alist on general
principles.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
1:44 p.m.
New subject: (no subject)
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
>>>>> "SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> OK. Is that on anybody's todo list? I think this should be
SY> taken care of _before_ this release goes public.
image-mode is in the packages, right? image-mode problems are
unrelated to the release. Show me that it's fixed, and I'll consider
a patch to format-alist.
Let's not go down that path, please.
`format-alist' is a very low-level feature. Adding image-mode to it
was a mistake in the first place: it broke simple editing features
such as editing XPM files. (I had to use VI for that for a time.)
Because of it being low-level, you couldn't circumvent it with using
`C-x i' or other tricks.
Pretty please: if we are to implement the imaging feature, let's do it
at a higher level, preferrably as a regular mode invoked off
`auto-mode-alist'.
Sure. But that mode allows a lot more than just detect and display,
and it was silently trashing some files or something. It wasn't just
randomly removed from that alist.
Right.
8614
days inactive
8616
days old
5 comments
4 participants
participants (4)
-
Hrvoje Niksic -
Latchezar M. Dimitrov -
Stephen J. Turnbull -
Steve Youngs