Re: [Bug: 21.4.22] windows 7
15 years, 1 month
Vin Shelton
Vin Shelton
Howard -
I had written:
> Thanks for the bug report. Can you describe exactly what you did,
> and exactly what message you received?
>
> My guess would be that the name of the directory XEmacs should be
> looking in has spaces in it. Under native Windows this can present
> a problem.
Howard had written:
> I tried uninstalling and reinstalling in a directory with no spaces,
> but that did not help.
Most recently, he wrote again:
> Any other thoughts? This is that last piece I need to make my new
> machine fully functional for me, so I would love to get it done.
I was actually thinking along the same lines as Rodney Sparapani.
I was thinking about the value of your HOME directory, not the
installed directory. What does:
(find-user-init-file)^J
report in the *scratch* buffer?
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: [Bug: 21.4.22] windows 7
15 years, 1 month
Rodney Sparapani
Rodney Sparapani
On 07/23/10 07:25 AM, Georgi, Howard wrote:
> To: XEmacs Beta<xemacs-beta(a)xemacs.org>
> Subject: [Bug: 21.4.22] windows 7
> --text follows this line--
> ================================================================
> Dear Bug Team!
>
>
> I installed version 21.4.22 on my new windows 7 machine, and the
> installation appeared to go smoothly, but when I try to edit the
> init.el file, the system doesn't find the right directory.
>
> ================================================================
WAG. Do you have a HOME environment variable defined?
Rodney
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: slow startup for xemacs on Darwin
15 years, 1 month
Richard Cook
Richard Cook
HEre is a stack trace. I can give you args for whatever function, etc. Just ask.
I posted a hack to unix_canonicalize_host_name() that gets rid of the problem for me in another email.
Stack Trace
_kevent, FP=7fff5fbfbe60
__mdns_query_mDNSResponder, FP=7fff5fbfbe60
__mdns_search, FP=7fff5fbfbf20
__mdns_addrinfo, FP=7fff5fbfc080
_search_addrinfo, FP=7fff5fbfc110
_si_addrinfo, FP=7fff5fbfc1f0
_getaddrinfo, FP=7fff5fbfc270
C unix_canonicalize_host_name, FP=7fff5fbfc3e0
C canonicalize_host_name, FP=7fff5fbfc400
C x_canonicalize_console_connection, FP=7fff5fbfc4a0
C x_canonicalize_device_connection, FP=7fff5fbfc540
C canonicalize_device_connection, FP=7fff5fbfc580
C Ffind_device, FP=7fff5fbfc610
C Fmake_device, FP=7fff5fbfc700
C Ffuncall, FP=7fff5fbfc830
C execute_optimized_program, FP=7fff5fbfcb70
C funcall_compiled_function, FP=7fff5fbfcc70
C Feval, FP=7fff5fbfcf20
C condition_case_1, FP=7fff5fbfd0b0
C condition_case_3, FP=7fff5fbfd130
C execute_rare_opcode, FP=7fff5fbfd230
C execute_optimized_program, FP=7fff5fbfd580
C funcall_compiled_function, FP=7fff5fbfd680
C Feval, FP=7fff5fbfd930
C condition_case_1, FP=7fff5fbfdac0
C top_level_1, FP=7fff5fbfdae0
C internal_catch, FP=7fff5fbfdc10
C initial_command_loop, FP=7fff5fbfdc30
C ...21_5_b29_i386_apple_darwin10_4_0, FP=7fff5fbfdd00
On Jul 24, 2010, at 8:14 AM, Stephen J. Turnbull wrote:
> Hamish Macdonald writes:
>
>> However, I wonder why xemacs is trying to resolve this address.
>> Local X applications on my system don't appear to do a DNS lookup
>> when I use a display name like "/tmp/foo/bar/baz:0", so why does
>> xemacs?
>
> I dunno. If you've got the time, I would appreciate it if you'd set a
> breakpoint on getaddrinfo and tell me what's on the C stack and on the
> Lisp stack (use the lbt function defined in .gdbinit) when getaddrinfo
> gets called on such a thing. If not, I'll get to it (I have a Mac
> with reasonably fresh Apple libraries installed), but probably that
> will be Real Soon Now. :-(
>
>> Is it possible that either XEmacs is not using the locally
>> installed XLIB library?
>
> No. XEmacs always uses a toolkit; currently supported are Xt and GTK+
> v1 (oops, but there you go). I conjecture that XEmacs wants to know
> something about the display's network aspect, but I don't have a good
> guess as to what.
>
>> Is XEmacs performing its own interpretation of the DISPLAY
>> environment variable (that would be a bad idea).
>
> Well, for one thing, the DISPLAY environment variable is not the only
> way to specify a display to XEmacs. This can be done with the
> -display command line flag as well as `make-frame-on-display'.
>
> Unfortunately, it is REQUIRED for robust operation in the X
> environment that a program do its own parsing of such things. X does
> *no* sanity checking on arguments in most functions, and it often
> leaves the restrictions on arguments undocumented.[1]
>
> Footnotes:
> [1] That's why I'm an XEmacs developer, because it was easier to
> debug an X crash due to a plausible but illegal argument in XEmacs
> than it was to debug the same bug in Emacs.
>
--
✐Richard Cook
✇ Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue, Livermore, CA, 94550, USA
☎ (office) (925) 423-9605
☎ (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: [COMMIT] Apply Stephen's bugfix to my advice.el changes
15 years, 1 month
Stephen J. Turnbull
Stephen J. Turnbull
Mats Lidell writes:
> What bothers me is the time it takes to do a full build. You need a
> good machine and some spare CPU cycles in order to do it. Maybe a
> quick rebuild on each checkin and then a full rebuild, maybe once a
> week or so, is the way to go!?
I don't think that's a good idea, for two reasons. The first is that
I suspect it won't make an order of magnitude difference. If you
touch anything in xemacs-base, for example, then just about everything
depends on that and it will all get rebuilt, I believe.
The second is that I think the build from scratch is what we care
about most. A rebuild of only the changed package on checkin, well,
the developer should be doing that. If cycles are a problem, then a
weekly (daily if there are changes would be nice) full rebuild should
be enough.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: [COMMIT] Apply Stephen's bugfix to my advice.el changes
15 years, 1 month
Aidan Kehoe
Aidan Kehoe
Ar an séú lá is fiche de mí Iúil, scríobh Stephen J. Turnbull:
> Aidan Kehoe writes:
>
> > This syntax works, though, and also doesn’t provoke any complaints
> > on FreeBSD:
> >
> > (make-glyph `(((mswindows) . [xbm :data (6 20 ,(make-string 20 0))])
> > ((tty) . [string :data " "])))
>
> This syntax works because you have X support built in on FreeBSD,
> right?
XBM support, most relevantly, but yes.
> The whole point of my example is to use a valid instantiator
> format that is unknown to the XEmacs instance.
Ah. Well, then,
(make-glyph `(((mswindows) . [bmp :data ,(make-string 20 0)])
((tty) . [string :data " "])))
would have been better; that works on Cygwin for me, but fails on FreeBSD.
> > On FreeBSD, when I build without X11 support, I can provoke the error that
> > is blocking the build on evaluating the code in x-symbol-vars.el. Mats, I
> > suspect, but haven’t confirmed, that the following will allow the build to
> > continue, I can certainly evaluate it without problems:
> >
> > --- x-symbol-vars.el~ 2010-07-25 17:58:39.000000000 +0100
> > +++ x-symbol-vars.el 2010-07-25 17:53:53.000000000 +0100
> > ＠＠ -1099,7 +1099,8 ＠＠
> > :group 'x-symbol-input-init)
> >
> > (defvar x-symbol-heading-strut-glyph
> > - (make-glyph (eval-when-compile
> > + (make-glyph (remove-if-not
> > + #'(lambda (spec) (valid-instantiator-p (cdr spec) 'image))
> > `(((x) . [xbm :data (6 20 ,(make-string 20 0))])
> > ((mswindows) . [xbm :data (6 20 ,(make-string 20 0))])
> > ((tty) . [string :data " "]))))
>
> Not your fault, but if that is needed, something is seriously wrong
> with the implementation of make-glyph. The whole point of specifiers
> is to allow you to specify things that may or may not be reasonable
> for the current instance of XEmacs, and have XEmacs intelligently
> filter out nonsense. The device-type guards should serve that purpose.
Mmm, but they don’t and never have for the instantiators, as far as I can
see. We haven’t noticed because most of the time the same collection of
instantiators have been available, and Mats is, correctly, stretching things
a little with a smoketest without any X11 support.
> > We also really should apply something like the following in specifier.el,
> > which would have made the whole thing a lot easier to debug (misleading
> > error messages never make anything easy):
>
> Improving the error message seems reasonable to me. It doesn't need
> to be perfect if you can make it better. It does need some test
> cases, though.
No guarantees about when from me, but yes, I will make this change.
--
“Apart from the nine-banded armadillo, man is the only natural host of
Mycobacterium leprae, although it can be grown in the footpads of mice.”
-- Kumar & Clark, Clinical Medicine, summarising improbable leprosy research
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Can't compile org-mode in 21.5
15 years, 2 months
Didier Verna
Didier Verna
Hello,
I'm trying to compile org-mode with the latest 21.5 from the repo, and
I'm getting this:
Compiling /usr/local/src/emacs-lisp/org-mode/lisp/org.el...
Loading iso-with-esc...
While compiling toplevel forms in file /usr/local/src/emacs-lisp/org-mode/lisp/org.el:
!! Syntax error (("Non-ISO-8859-1 character specified with octal escape" 493))
>>Error occurred processing lisp/org.el: Syntax error: Non-ISO-8859-1 character specified with octal escape, 493
Any idea ?
Thanks.
--
Resistance is futile. You will be jazzimilated.
Scientific site: http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta
- 2 participants
- 2 comments
Re: slow startup for xemacs on Darwin
15 years, 2 months
Aidan Kehoe
Aidan Kehoe
Ar an ceathrú lá is fiche de mí Iúil, scríobh Hamish Macdonald:
> >
> > Ar an tríú lá is fiche de mí Iúil, scríobh Hamish Macdonald:
> > > [...] Is
> > > XEmacs performing its own interpretation of the DISPLAY environment
> > variable
> > > (that would be a bad idea).
> >
> > On Sat, Jul 24, 2010 at 6:06 AM, Aidan Kehoe <kehoea(a)parhasard.net> wrote:
> >
> >>
> >> Hmm? The format of DISPLAY has been stable for decades.
>
> This is so, but why would XEmacs need to interpret the value of the DISPLAY
> environment variable? That string is meant to be passed to the X libraries
> for communication with the server, not interpreted by application programs
> (regardless of the fact that historically programs have done that, it is a
> bad idea).
>
> What possible need could XEmacs have to do that?
Now I look into it, XEmacs does leave the parsing of the DISPLAY variable to
the X11 libraries. Still, a lot of the point of X11 is that programs written
with one version of the libraries can display on servers written with
another version of the libraries, even on another architecture; randomly
changing the format of the string makes that harder.
(In practice, people should be tunnelling the X11 connection over SSH, where
this won’t matter, as far as I can see; SSH passes the DISPLAY string to
xauth(1), it doesn’t do the parsing itself.)
--
“Apart from the nine-banded armadillo, man is the only natural host of
Mycobacterium leprae, although it can be grown in the footpads of mice.”
-- Kumar & Clark, Clinical Medicine, summarising improbable leprosy research
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
moving vcard to mail-lib
15 years, 2 months
Mike Kupfer
Mike Kupfer
Hi Simon, there are a couple different mail front-ends that use
vcard.el--most notably, Gnus and VM. Currently we distribute vcard.el
in the Gnus package, but it seems like it would make more sense to
distribute it in mail-lib. As you're the maintainer for the mail-lib
package, I wanted to check in with you to see how you'd like to handle
this.
There's a new version of vcard.el that comes with the latest version of
VM. It seems to work okay with Gnus, so that's the version I'd like to
get into mail-lib.
Please let me know how you'd like to proceed.
thanks,
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: [Bug: 21.4.22] windows 7
15 years, 2 months
Vin Shelton
Vin Shelton
Thanks for the bug report. Can you describe exactly what you did, and
exactly what message you received?
My guess would be that the name of the directory XEmacs should be looking in
has spaces in it. Under native Windows this can present a problem.
Thank you,
Vin Shelton
On Fri, Jul 23, 2010 at 8:25 AM, Georgi, Howard <hgeorgi(a)fas.harvard.edu>wrote:
> To: XEmacs Beta <xemacs-beta(a)xemacs.org>
> Subject: [Bug: 21.4.22] windows 7
> --text follows this line--
> ================================================================
> Dear Bug Team!
>
>
> I installed version 21.4.22 on my new windows 7 machine, and the
> installation appeared to go smoothly, but when I try to edit the
> init.el file, the system doesn't find the right directory.
>
> ================================================================
>
> System Info to help track down your bug:
> ---------------------------------------
>
> OS version:
>
>
> Microsoft Windows XP [Version 5.1.2600]
> OS: Windows_NT
>
>
> XEmacs 21.4.22 "Instant Classic" configured for `i586-pc-win32'.
>
>
> Building XEmacs in "c:\\XEmacsBuild\\xemacs-21.4.22\\nt".
> Using compiler "icl -nologo -W3 -O2 -G5 -MD".
> Installing XEmacs in "c:/XEmacsBuild/installed/XEmacs-21.4.22".
> Compiling in support for Microsoft Windows native GUI.
> Compiling in support for XPM images.
> Compiling in support for GIF images.
> Compiling in support for PNG images.
> Compiling in support for TIFF images.
> Compiling in support for JPEG images.
> Compiling in support for toolbars.
> Compiling in support for dialogs.
> Compiling in support for widgets.
> Compiling in support for native sounds.
> Compiling in fast dired implementation.
> Using portable dumper.
> Using system malloc.
> Using DLL version of C runtime library
>
>
> Load-Path Lisp Shadows:
> ----------------------
> (c:\Program Files
> (x86)\XEmacs\xemacs-packages\lisp\xemacs-base\easy-mmode c:\Program
> Files (x86)\XEmacs\XEmacs-21.4.22\lisp\easy-mmode)
>
> Internationalization Settings:
> -------------------------
>
>
> Installed XEmacs Packages:
> -------------------------
> (xemacs-devel ver: 1.79 upstream: No-Upstream-Ver)
> (xemacs-base ver: 2.18 upstream: No-Upstream-Ver)
> (x-symbol ver: 1.11 upstream: 4.5.1)
> (vc ver: 1.45 upstream: No-Upstream-Ver)
> (time ver: 1.14 upstream: 1.17)
> (text-modes ver: 1.95 upstream: No-Upstream-Ver)
> (texinfo ver: 1.3 upstream: No-Upstream-Ver)
> (speedbar ver: 1.29 upstream: 1.0pre4)
> (sounds-wav ver: 1.12 upstream: No-Upstream-Ver)
> (sh-script ver: 1.24 upstream: 2.0f)
> (semantic ver: 1.2 upstream: 1.4.4)
> (reftex ver: 1.34 upstream: 4.21)
> (prog-modes ver: 2.18 upstream: No-Upstream-Ver)
> (perl-modes ver: 1.14 upstream: No-Upstream-Ver)
> (pc ver: 1.28 upstream: No-Upstream-Ver)
> (os-utils ver: 1.41 upstream: No-Upstream-Ver)
> (net-utils ver: 1.56 upstream: N/A)
> (mail-lib ver: 1.8 upstream: No-Upstream-Ver)
> (ispell ver: 1.32 upstream: 3.6)
> (hm--html-menus ver: 1.24 upstream: 5.9)
> (fsf-compat ver: 1.17 upstream: No-Upstream-Ver)
> (eshell ver: 1.16 upstream: 0fc80a3f6bb3bb59f42e9ff83cc8b89bf90fe658)
> (elib ver: 1.13 upstream: 1.0)
> (eieio ver: 1.06 upstream: 1.0pre4)
> (efs ver: 1.34 upstream: 1.24)
> (edit-utils ver: 2.4 upstream: No-Upstream-Ver)
> (ediff ver: 1.77 upstream: 2.75)
> (edebug ver: 1.22 upstream: No-Upstream-Ver)
> (ecb ver: 1.22 upstream: 2.31)
> (dired ver: 1.19 upstream: 7.16)
> (debug ver: 1.18 upstream: No-Upstream-Ver)
> (cc-mode ver: 1.45 upstream: 5.30.10)
> (calc ver: 1.26 upstream: 2.02fX3)
> (c-support ver: 1.22 upstream: No-Upstream-Ver)
> (auctex ver: 1.51 upstream: 11.84)
>
>
>
> Features:
> --------
>
> (mail-abbrevs xemacsbug shadow sendmail rfc822 efs-cu
> xemacs-devel-autoloads xemacs-base-autoloads x-symbol-autoloads
> vc-autoloads time-autoloads text-modes-autoloads texinfo-autoloads
> speedbar-autoloads sounds-wav-autoloads sh-script-autoloads
> semantic-autoloads reftex-autoloads prog-modes-autoloads
> perl-modes-autoloads pc-autoloads os-utils-autoloads
> net-utils-autoloads mail-lib-autoloads ispell-autoloads
> hm--html-menus-autoloads fsf-compat-autoloads eshell-autoloads
> elib-autoloads eieio-autoloads efs-autoloads edit-utils-autoloads
> ediff-autoloads edebug-autoloads ecb-autoloads dired-autoloads
> debug-autoloads cc-mode-autoloads calc-autoloads c-support-autoloads
> tex-site auctex-autoloads lisp-autoloads loadhist auto-show
> fontl-hooks code-cmds gutter-items menubar-items x-menubar dragdrop
> mode-motion mouse itimer auto-save lisp-mode easymenu iso8859-1 page
> buff-menu lib-complete help-nomule cus-file derived frame text-props
> obsolete cus-start custom widget cl-extra mini-cl cl cl-19 packages
> backquote very-early-lisp file-coding mswindows-scrollbars mswindows
> toolbar native-sound scrollbar network-streams subprocesses
> menu-accelerator-support menubar md5 xemacs gutter tiff png gif jpeg
> xpm xbm lisp-float-type windows-nt dragdrop-api dialog devices
> window-system base64)
>
>
> Recent keystrokes:
> -----------------
>
> misc-user button1 button1up M-x r e p o r t - TAB button1
> button1up RET
>
>
> Recent messages (most recent first):
> -----------------------------------
>
> Loading xemacsbug...done
> Loading xemacsbug...
> Making completion list...
> (New file)
> Loading efs-cu...done
> Loading efs-cu...
>
>
> _______________________________________________
> XEmacs-Beta mailing list
> XEmacs-Beta(a)calypso.tux.org
> http://calypso.tux.org/mailman/listinfo/xemacs-beta
>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments