January 2006 - XEmacs-Beta - XEmacs Mailing List Archives

After update from 1.5.18 to 1.5.19, xemacs 21.4.13 can only run from bash 18 years, 10 months

Karr, David

I have a desktop icon for running Xemacs 21.4.13. This has been working fine. Just today, I upgraded Cygwin from 1.5.18 to 1.5.19. Now when I double-click the icon, it does nothing. I then tried pasting the path to it into a DOS cmd prompt, and it still does nothing. I then executed it directly from a bash prompt, and that worked. I have a similar icon for 21.4.18, and that doesn't demonstrate the same problem, although 21.4.18 always runs a cmd window in the background, which 21.4.13 does not.

4 participants
3 comments

Variable names of package hierarchies 18 years, 10 months

Ralf Angeli

In XEmacs 21.5 the variable names for package hierarchies were changed from {early,late,last}-packages to {early,late,last}-package-hierarchies. AUCTeX looks for the old variable names in its build procedure and fails when being configured with XEmacs 21.5 due to the change of names. (This was reported by Clemens Fruhwirth on the AUCTeX bug mailing list.) I am wondering if any other packages out there might get the same problem as soon as they will be used with XEmacs 21.5 and if it made sense to supply aliases for the old variable names. It's no problem if you don't want to do this. Then I'll simply adapt the relevant function call in AUCTeX's build procedure. -- Ralf

6 participants
11 comments

**Message you sent blocked by our bulk email filter** 18 years, 10 months

MAILER DAEMON

Your message to: bwascher(a)sugarloaf-usa.com was blocked by our Spam Firewall. The email you sent with the following subject has NOT BEEN DELIVERED: Subject: Message could not be delivered

1 participants
0 comments

configure vs debian 18 years, 10 months

Giacomo Boffi

yesterday i tried to build the latest & greatest xemacs straight from cvs, on my home system, i.e., debian unstable if i tried to configure --with-athena=3d, the configuration stopped, with the message (more or less) "i found no suitable athena library" i had to configure without specifying anything with regard to athena, i built xemacs, installed and, surprise, i had a working xemacs with xft and 3d widgets... it's me that i've done something bad, it's configure or it'debian? ciao gb

2 participants
4 comments

Re: possible bug in 21.4.18 windows version and installation 18 years, 10 months

Vin Shelton

Robert, (Pardon the top-posting, but since xemacs-beta didn't see your most recent reply, I thought I'd include it in its entirety below.) OK. Please remember to include xemacs-beta on *all* your replies. I'm running out of ideas, but I think it may have something to do with remnants of your previous installation getting in the way. By the way, I still don't know /exactly/ what steps you took. If you want to continue to pursue this, please send xemacs-beta a list of the steps you took (like the formula I published earlier: mkdir test cd test cp ~/cvsroot/xemacs-21.4/src/win* . etags *.c *.h xemacs-21.4 -vanilla C-x C-f window.c C-s XSETWINDOW M-. -> Find tag: (default XSETWINDOW) RET ) for either or both of your problems. If you're happy with 21.4.13, you don't have to continue your investigation. Cheers, Vin On 1/27/06, Robert Abad <Robert_Abad(a)trimble.com> wrote: > Hi Vin, > > Please see below. > > Regards, > Robert > > > -----Original Message----- > > From: ethersoft(a)gmail.com [mailto:ethersoft＠gmail.com] On > > Behalf Of Vin Shelton > > Sent: Tuesday, January 24, 2006 5:07 PM > > To: Robert Abad > > Cc: xemacs-beta > > Subject: Re: possible bug in 21.4.18 windows version and installation > > > > Hi Robert, > > > > Please don't drop xemacs-beta, many heads are better than one! > > > > On 1/23/06, Robert Abad <Robert_Abad(a)trimble.com> wrote: > > > Hi Vin, > > > > > > Thanks for responding. Please see below. > > > > > > Regards, > > > Robert > > > > > > > -----Original Message----- > > > > From: ethersoft(a)gmail.com [mailto:ethersoft＠gmail.com] On > > Behalf Of > > > > Vin Shelton > > > > Sent: Saturday, January 21, 2006 7:09 PM > > > > To: Robert Abad > > > > Cc: xemacs-beta(a)xemacs.org > > > > Subject: Re: possible bug in 21.4.18 windows version and > > > > installation > > > > > > > > Dear Robert, > > > > > > > > Thanks for writing. > > > > > > > > On 1/19/06, Robert Abad <Robert_Abad(a)trimble.com> wrote: > > > > > I recently installed XEmacs v21.4.18 on Windows XP machine > > > > using the > > > > > Inno-Setup exe program. I believe there are several issues > > > > with this > > > > > version and its installation: > > > > > > > > > > - Whenever I try to use a Tag Table, it always defaults to > > > > C:\TAGS (I > > > > > have C:\ set as my startup directory). It doesn't > > default to the > > > > > directory in which I used a shell to create a tags file or the > > > > > directory in which I have the currently opened file. This > > > > behavior is > > > > > very different from v21.4.13 (the previously released windows > > > > > version). > > > > > > > > I wouldn't expect this to be any different between the versions, > > > > actually. Where a particular TAGS table is found depends on the > > > > setting of the variable tag-table-alist. The info node on > > > > 'Selecting a Tags Table' tries to explain this. > > > > > > Let me elaborate a little more.... > > > > > > In v21.4.13, I would open a file, say, C:\projects\src\junk.c. I > > > would then want to search for a tag (M-x tags-search). > > XEmacs would > > > then ask me (in the command line): > > > > > > Build tag completion table for c:\projects\src\TAGS? (y or n) > > > > > > I would hit 'y' for yes and the search would begin. I > > wouldn't have > > > to do anything with the variable tag-table-alist (unless it was > > > automatically done for me). > > > > > > v21.4.18 does not do this. I'll open the file just like before. I > > > invoke a tags search and the command line says (I don't > > remember the > > > exact words): > > > > > > C:\TAGS does not exist > > > > > > The search is then aborted. It won't let me specify a tags table > > > either via the menu Tools->Tags->Select Tags Table File... > > (which I > > > believe is the same as M-x visit-tag-table). My > > expectation was that > > > this would've behaved the same way that 21.4.13 behaved. > > > > > > > I don't see the behavior you described. Here's what I did: > > > > mkdir test > > cd test > > cp ~/cvsroot/xemacs-21.4/src/win* . > > etags *.c *.h > > xemacs-21.4 -vanilla > > C-x C-f window.c > > C-s XSETWINDOW > > M-. -> Find tag: (default XSETWINDOW) RET This loads the TAGS > > file and jumps to the definition of XSETWINDOW in window.h. > > The TAGS file is small enough not to prompt for a completion table. > > > > This is running the latest windows native XEmacs from the > > 21.4.19-pre5 setup kit (available from > > ftp://ftp.xemacs.org/pub/xemacs/windows/testing). > > > > Do you see the problematic behavior in a xemacs started with > > the -vanilla option? > > Okay, I've tried the 21.4.19-pre6 version and it still exhibits the > behavior that I was reporting above in 21.4.18. And yes, it still does > this with the vanilla option. > > > > > If so, please file a bug report with the new XEmacs (the > > installation report you filed came from the 21.4.13 version). > > Below is an installation report for 21.4.19-pre6 > > > > What does your etags file look like? Did you generate a > > fresh one using the etags that came with XEmacs? > > > > I did recreate the etags file and its still doesn't work. I also tried > to explicitly specify the TAGS table using: > M-x visit-tags-table > > As much as I'd like to use 21.4.18 (or 21.4.19 beta), I'm going to have > to go back to 21.4.13 because it won't let me do a tags search. I > depend on that to do my work. > > In another email, you gave me some elisp code to put in .xemacs/init.el. > I created a init.el file and inserted that code. It did not solve my > path problem. > > Regards, > Robert > > ======================INSTALLATION REPORT FOR > 21.4.19-pre6================================ > > > To: XEmacs Beta <xemacs-beta(a)xemacs.org> > Subject: [Bug: 21.4.18] blah > --text follows this line-- > ================================================================ > Dear Bug Team! > > > > ================================================================ > > System Info to help track down your bug: > --------------------------------------- > > OS version: Microsoft Windows XP [Version 5.1.2600] OS: Windows_NT > XEmacs 21.4.18 "Social Property" configured for `i586-pc-win32'. > Building XEmacs in > "e:\\acs\\software\\XEmacsWindowsKit\\xemacs-21.4-2006-01-26\\nt". > Using compiler "cl -nologo -W3 -O2 -G5 -MD". Installing XEmacs in > "c:\\XEmacs-built\\XEmacs-21.4.18". Package path is > "~\\.xemacs;;c:\\XEmacs-built\\site-packages;c:\\XEmacs-built\\xemacs-pa > ckages". 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: > ---------------------- > nil > > > Installed XEmacs Packages: > ------------------------- > (xemacs-devel ver: 1.72 upstream: No-Upstream-Ver) > (xemacs-base ver: 2.01 upstream: No-Upstream-Ver) > (time ver: 1.14 upstream: 1.17) > (text-modes ver: 1.9 upstream: No-Upstream-Ver) > (texinfo ver: 1.3 upstream: No-Upstream-Ver) > (speedbar ver: 1.28 upstream: 0.14beta4) > (sounds-wav ver: 1.12 upstream: No-Upstream-Ver) > (sh-script ver: 1.21 upstream: 2.0f) > (semantic ver: 1.19 upstream: 1.4.2) > (prog-modes ver: 2.06 upstream: No-Upstream-Ver) > (perl-modes ver: 1.08 upstream: No-Upstream-Ver) > (pc ver: 1.28 upstream: No-Upstream-Ver) > (os-utils ver: 1.36 upstream: No-Upstream-Ver) > (net-utils ver: 1.48 upstream: N/A) > (mail-lib ver: 1.75 upstream: No-Upstream-Ver) > (fsf-compat ver: 1.15 upstream: No-Upstream-Ver) > (eieio ver: 1.05 upstream: 0.17) > (efs ver: 1.33 upstream: 1.23) > (edit-utils ver: 2.32 upstream: No-Upstream-Ver) > (ediff ver: 1.6 upstream: 2.75) > (edebug ver: 1.21 upstream: No-Upstream-Ver) > (ecb ver: 1.22 upstream: 2.31) > (dired ver: 1.17 upstream: 7.13) > (debug ver: 1.17 upstream: No-Upstream-Ver) > (cc-mode ver: 1.45 upstream: 5.30.10) > (c-support ver: 1.22 upstream: No-Upstream-Ver) > > > > Features: > -------- > > (mail-abbrevs xemacsbug shadow sendmail rfc822 tags etags cc-mode > cc-menus cc-cmds cc-styles cc-align cc-engine cc-vars cc-defs > regexp-opt efs-cu shell comint ring xemacs-devel-autoloads > xemacs-base-autoloads time-autoloads text-modes-autoloads > texinfo-autoloads speedbar-autoloads sounds-wav-autoloads > sh-script-autoloads semantic-autoloads prog-modes-autoloads > perl-modes-autoloads pc-autoloads os-utils-autoloads > net-utils-autoloads mail-lib-autoloads fsf-compat-autoloads > eieio-autoloads efs-autoloads edit-utils-autoloads ediff-autoloads > edebug-autoloads ecb-autoloads dired-autoloads debug-autoloads > cc-mode-autoloads c-support-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: > ----------------- > > t h % ; button1 button1up button1 button1up Sh-insert > ; RET p a t h RET e t a g s SPC * . h SPC * . c SPC > * . a s BS BS i n c SPC * . a s m RET C-x C-f 1 6 7 > i n . c RET next next next next next next next next > next next next next next next next next next next next > next next next next next next next next next next next > next next next next next button1 button1up ESC . ESC > . ESC . misc-user > > > Recent messages (most recent first): > ----------------------------------- > > Loading xemacsbug...done > File c:\TAGS not a valid tags file > Loading xemacsbug... > File c:\TAGS not a valid tags file > File c:\TAGS not a valid tags file > Loading etags...done > Loading etags... > Loading cc-mode...done > Loading cc-mode... > Loading efs-cu...done > Loading efs-cu... > Note: file is write protected > c:\projECTS\code\airborne\05xx\app565\ > Completed > Completing file name... > Completed > Completing file name... > Completed > Completing file name... > Completed > -- Whoever you are, no matter how lonely, the world offers itself to your imagination, calls to you like the wild geese, harsh and exciting-- over and over announcing your place in the family of things. Mary Oliver

1 participants
0 comments

XEmacs 21.5.24 compile in XP due to CR LF issue 18 years, 10 months

Tsunhin John Wong

Hi all, First, thanks Rick for the reply I sort out the problem to be the line-ends (CR/LF) problem of files in the source files which are all in UNIX formats: this has rendered these sources distribution virtually "not buildable" in the XP environment (in order to obtain the NT XEmas) --- because there are so many files for UNIX to WIN32 format conversion and anyone has to also figure out whether a file is a binary file or a text file before the conversion neither of any version of VS .NET nor the nmake in win32 can handle these unix file format automatically Does anybody has a suggestion for work around for the CR LF conversion in order to build in win32? Regards, Tsunhin On Fri, 27 Jan 2006, Rick Rankin wrote: > >> ----- Original Message ---- >> From: Tsunhin John Wong <tjw23(a)pitt.edu> >> To: xemacs-nt(a)xemacs.org; xemacs-beta(a)xemacs.org >> Sent: Friday, January 27, 2006 1:33:11 AM >> Subject: XEmacs 21.5.24 Cannot load project file to VS .NET >> >> Hi all, >> >> I tried to load the .dsp (VC6 project file) cannot be load onto my VS .NET >> Version 7.1.3088 with .NET Framework 1.1 Version 1.1.4322 SP1 >> >> I was told that the .dsp was corrupted, but I look through it and find the >> text file seems to be alright >> >> Any suggestion for me to solve this? > > I'm afraid I don't understand what this has to do with XEmacs. It seems to me that > you need to be asking this on some sort of Microsoft-specific list. > > --Rick > > > >

2 participants
1 comments

Re: Mule-on-Windows, full Unicode support XEmacs 18 years, 10 months

Stephen J. Turnbull

Reply-To set to xemacs-beta and ben. The other lists are basically dead. >>>>> "Tsunhin" == Tsunhin John Wong <JohnW+(a)pitt.edu> writes: Tsunhin> Hi all XEmacs users on NT/XP, I'm trying to find a way to Tsunhin> work on UNICODE text (inputing CJK characters) XEmacs 21.5 is moving toward full Unicode support. The next step is to use Unicode as the internal encoding. (Stalled as the lead developer is on vacation, maybe we'll see results in February.) We are currently restricted with respect to modern Chinese character sets such as GBK and GB18030; these cannot be supported with the legacy (Mule) internal encoding. Tsunhin> by XEmacs in an XP box Is there anyway to install the Tsunhin> MULE-UCS packages? and how is the status of MULE-UCS in Tsunhin> recent year? Mule-UCS has been orphaned, abandoned, unsupported, and unmaintained for about 5 years. Nor does XEmacs 21.4 support Mule well at all; third party patches are required. On the Windows platform you really should use XEmacs 21.5, which does pretty much everything that Mule-UCS does, although you may need to load some non-default character sets. Up to the current release (21.5.24) it is very stable, though there are many rough edges since it is the development line. There is likely to be substantial instability in the near future, however, as we replace the legacy internal encoding with Unicode. The emacs-unicode2 branch of GNU Emacs is well-recommended for stability and character set support if those are overriding concerns. But that branch is of course completely unsupported, currently not being developed AFAIK (they're devoting maximum effort to the current release) and is basically waiting on the release to be merged to mainline, at which point you can probably expect some months of instability. (And as far as I know all emacs-unicode developers are Unix-based; I've seen no reports about it on Windows. It's *probably* OK but I suggest asking before you invest effort.) -- Graduate School of Systems and Information Engineering University of Tsukuba http://turnbull.sk.tsukuba.ac.jp/ Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Economics of Information Communication and Computation Systems Experimental Economics, Microeconomic Theory, Game Theory

5 participants
7 comments

RE: Re: After update from 1.5.18 to 1.5.19, xemacs 21.4.13 can only run from bash 18 years, 10 months

Karr, David

> -----Original Message----- > From: cygwin-owner(a)cygwin.com > [mailto:cygwin-owner＠cygwin.com] On Behalf Of René Berber > > Karr, David wrote: > [snip] > >>And the command you are running is? > > > > > > C:\cygwin\usr\local\bin\i686-pc-cygwin\xemacs-21.4.13.exe > > This is not the xemacs distributed by Cygwin... or is it? This is the Xemacs built for Cygwin, but not distributed through cygwin. > Continuing with the guess work, did you move the old xemacs > to /usr/local? No, I didn't manually move anything. > Have you checked if the old xemacs depends on libraries you > don't currently have? (i.e. cygcheck > /usr/local/bin/i686-pc-cygwin/xemacs-21.4.13) I verified that all the dlls listed in this output exist (just piped it to "xargs ls"). Remember that the only change I made was upgrading Cygwin from 1.5.18 to 1.5.19. I didn't intentionally remove any libraries.

1 participants
0 comments

RE: Re: After update from 1.5.18 to 1.5.19, xemacs 21.4.13 can only run from bash 18 years, 10 months

Karr, David

> -----Original Message----- > From: cygwin-owner(a)cygwin.com > [mailto:cygwin-owner＠cygwin.com] On Behalf Of René Berber > > Karr, David wrote: > > > I have a desktop icon for running Xemacs 21.4.13. This has been > > working fine. Just today, I upgraded Cygwin from 1.5.18 to > 1.5.19. > > Now when I double-click the icon, it does nothing. I then tried > > pasting the path to it into a DOS cmd prompt, and it still does > > nothing. I then executed it directly from a bash prompt, and that > > worked. > > And the command you are running is? C:\cygwin\usr\local\bin\i686-pc-cygwin\xemacs-21.4.13.exe > > I have a similar icon for 21.4.18, and that doesn't demonstrate the > > same problem, although 21.4.18 always runs a cmd window in the > > background, which 21.4.13 does not. > > I think what affected your installation is a change of > version of Xemacs not the Cygwin dll. > > This works for me with no problem: > > C:\cygwin\bin\run.exe xemacs I did not upgrade Xemacs. Executing the icon (which uses the path given above), or pasting that path into a cmd window, does nothing. It just returns to the prompt and the window doesn't appear. The upgrade of Cygwin did not affect the execution of 21.4.18 at all, only 21.4.13. I'm not using 21.4.18 regularly yet for other reasons.

1 participants
0 comments

RE: After update from 1.5.18 to 1.5.19, xemacs 21.4.13 can only run from bash 18 years, 10 months

Karr, David

> -----Original Message----- > From: Glynn Clements [mailto:glynn＠gclements.plus.com] > > Karr, David wrote: > > > I have a desktop icon for running Xemacs 21.4.13. This has been > > working fine. Just today, I upgraded Cygwin from 1.5.18 to > 1.5.19. > > Now when I double-click the icon, it does nothing. I then tried > > pasting the path to it into a DOS cmd prompt, and it still does > > nothing. I then executed it directly from a bash prompt, and that > > worked. > > Did you reboot? If you upgrade cygwin1.dll, Cygwin programs > don't work correctly (or at all) until you have rebooted. No difference. > > I have a similar icon for 21.4.18, and that doesn't demonstrate the > > same problem, although 21.4.18 always runs a cmd window in the > > background, which 21.4.13 does not. > > You can use Cygwin's "run" program to hide the console window, e.g.: > > C:\Cygwin\bin\run.exe C:\Cygwin\xemacs.bat With this knowledge, just in case, I tried running "c:\cygwin\bin\run <pathtoxemacs21413>" from a cmd prompt, and it made no difference.

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta January 2006