21.5.27 crash on startup.
16 years, 11 months
Stephen J. Turnbull
brister(a)pobox.com writes:
> raw-append-progress-feedback("Fontifying *scratch*..." 0 #<x-frame "XEmacs" 0x27e4e>)
Put `(setq progress-feedback-use-echo-area t)' in your init file.
This is a known bug in the progress gauge widget.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Followup: Re: Releasing the Emacs guided tour into the public domain; also, video
16 years, 11 months
Jason A. Spiro
2007/4/2, Jason Spiro <jasonspiro4(a)gmail.com> wrote:
> By the way, an idea: Perhaps it would be better if the material was
> hosted on a wiki ( perhaps at
> http://commons.wikimedia.org/wiki/Category:Software_documentation )
> and your page linked to the material on the wiki? Then it would be
> easier for people to contribute. What do all of you think? Phil,
> would you like me to upload the material to the site I mentioned?
>
Hi Phil,
Could you kindly mention a few times in the guided tour that C-h means
Control-h and M-x means Alt-x?
Or would you like me to make the changes? I can, though it'd be
easier for me to do so if the document was moved to a wiki as
mentioned above. :-)
--
Jason Spiro: computer consulting with a smile.
I provide software development and training services to clients worldwide.
Contact me for a FREE consultation. Satisfaction guaranteed.
+1 (416) 781-5938 / Email: info(a)jspiro.com / MSN: jasonspiro(a)hotmail.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Solaris binaries
16 years, 11 months
Mike Kupfer
A couple years ago (yikes!) Stephen and I traded some email off-list
about making pre-built Solaris binaries of XEmacs available. The
binaries on the Solaris Companion aren't suitable for a lot of folks,
because they're built on the under-development Solaris release and are
not guaranteed to work on older, shipping releases.
It just occurred to me to check Blastwave, which provides a lot of
prebuilt Solaris binaries. And yes, XEmacs is there (21.4.19).
Blastwave binaries should run on Solaris 8 and later releases.
http://www.blastwave.org/packages.php/xemacs
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
evangelizing xemacs with a graphical tutorial
16 years, 11 months
Jason Spiro
Hi,
Emacsen can be hard to learn sometimes. :-)
It would be great if you could ship an illustrated tutorial (the one
from http://stuff.mit.edu/iap/emacs/ is the best one I've found) in
xemacs's etc/ directory. It would be even better if you could mention
it on the splash screen and the Help menu. :-) Part 1 of the set is
an accelerated illustrated tutorial on Emacs for the impatient. The
rest of the set cover customization and elisp. They are excellent,
and it looks like GNU Emacs will probably plans include them too: see
the thread at http://thread.gmane.org/gmane.emacs.devel/65537/focus=65629
The files are GFDLed. I don't know if they are anti-xemacs-biased or not.
What do you think?
--Jason Spiro
--
Jason Spiro: computer consulting with a smile.
I also provide training and spyware removal services for homes and businesses.
Call or email for a FREE 5-minute consultation. Satisfaction guaranteed.
+1 (416) 781-5938 / Email: info(a)jspiro.com / MSN: jasonspiro(a)hotmail.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: 21.4.20 configure.in problems
16 years, 11 months
Vin Shelton
On 5/4/07, Stephen J. Turnbull <turnbull(a)sk.tsukuba.ac.jp> wrote:
> Vin Shelton writes:
>
> > On 5/3/07, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
>
> > > We should fix the quoting problem, though, since it's trivial to do
> > > so. At least the Bash man page specifies the argument to -c as "a
> > > string", so it needs quotes if it contains spaces.
> >
> > Here's why I asked exactly what went wrong:
> >
> > bash-3.2$ mkdir "foo bar"
>
> Spaces in the path returned is not my point. As you point out,
> dealing with them would take auditing the whole script, and possibly
> can't be done. The point is that
>
> sh -c cd $src && pwd
>
> means
>
> if sh -c cd $src; then
> pwd
> fi
>
> which clearly is not the same as
>
> sh -c "cd $src && pwd"
Yes. And my point was that, absent an actual bug (like "I was trying
to configure in a directory with spaces in the name and I couldn't"),
I'm not going to make that change. There's no real benefit to doing
so.
That's approximately where you're headed with your next point:
>
> (although a little thought suggests that in that context it's actually
> equivalent!)
Regards,
Vin
PS. I wasted about an hour of my life last night generating the
attached diff to configure. With this patch, configure will run to
completion in a directory with spaces in the name. The makefiles
still need tweaking:
srcdir=/opt/src/foo bar
needs to be turned into
srcdir=/opt/src/foo\ bar
but if you do that, you can actually build XEmacs.
--
The Journey by Mary Oliver
http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
21.4.20 configure.in problems
16 years, 11 months
Christophe Kalt
Couple issues i ran into:
dnl Calculate canonical name for blddir (i.e. current
directory).
dnl PWD may already be the preferable absolute name for ".",
dnl but we can't trust it - it is sometimes inaccurate.
absolute_pwd="`pwd`";
if test -n "$PWD" -a "`cd $PWD && pwd`" = "$absolute_pwd"
While this will behave okay, it still prints a spurious
"./configure: no home directory"
on stderr
dnl Check if the source directory already has a configured system in it.
if test `pwd` != `sh -c cd $srcdir && pwd` \
Please, use quotes:
if test `pwd` != `sh -c "cd $srcdir && pwd"` \
Christophe
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Hello,
16 years, 11 months
Molly Scannell
Hello,
I would like to make certain keywords (that I define) turn up highlighted Color1 when I write, and others turn up highlighted Color2. I understand how to turn on syntax highlighting, but could you possibly give me an example
about what should be in my init.el file to do this?
Thanks!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
minor configure/doc bug
16 years, 11 months
Rodney Sparapani
Hi Gang:
Most likely a minor configure/doc bug, but I have given up trying to
figure out how the autotools work. For 21.5-b27, configure --help lists
bufpos as a valid item for the --with-error-checking list, but
configure does not actually except that option. Also, configure --help
does not list extents, but that does appear to be a valid option.
Thanks,
Rodney
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
RE: [Bug: 21.4.20] Network Drives
16 years, 11 months
Steve Higham
Vin, Stephen,
I'm sorry if I've missed something here, but I cannot think of any benefit
from trying to identify whether a file is executable under windows. Surely
the sensible approach it to try and execute it if requested, and report any
resulting failures.
I appreciate that the Unix approach of having an "executable attribute" has
benefits. Furthermore programs like xemacs should obviously respect this
attribute. However windows does not have this attribute. The OS shell and
all other systems, assume that all files are executable.
I can see no end of problems with this proposed function. Where the function
successfully identifies an executable file there will be no benefit. Where
the function fails to recognise a file as executable, the user will
presumably be told that his / her file is not marked as executable. This
will presumably cause loads of grief and no benefit.
Cheers,
Steve
-----Original Message-----
From: ethersoft(a)gmail.com [mailto:ethersoft＠gmail.com] On Behalf Of Vin
Shelton
Sent: 29 April 2007 13:12
To: Stephen J. Turnbull
Cc: Steve Higham; Benson Margulies; xemacs-beta(a)xemacs.org
Subject: Re: [Bug: 21.4.20] Network Drives
On 4/29/07, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
> Steve Higham writes:
>
> > My machine contains several perl scripts (*.pl) which are certainly
> > executable. Can the "executable extension list" be modified as a
standard
> > lisp variable?
>
> No, that's precisely why I consider it bogus, even though I haven't
> used Windows in years. The list is implicit in a series of if ... else
> if ... clauses in the function.
>
> On the other hand, since I haven't been using Windows, I'm unsure
> whether there's a way to register an extension as executable, and how
> XEmacs could determine that at runtime. So I need somebody who knows
> about that kind of thing to look at it.
I looked at the function; you're right - it's totally bogus. There is
a registry key which defines file associations and we could
potentially use that. I'll investigate a bit further.
- Vin
--
The Journey by Mary Oliver
http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta